Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4xvq-3m68-h444

Backstage has sensitive information exposure in scaffolder task logs

CVSS 6.5 MediumEPSS 0.0026 · 17th percentile

Published by the GitHub Advisory Database at 7 Oct 2026, 16:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
@backstage/plugin-scaffolder-backendnpm<4.1.04.1.0
Identifiers
GHSA-4xvq-3m68-h444 · CVE-2026-106504
Weakness (CWE)
CWE-532
Tags
Published
7 Oct 2026
Updated
7 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

An authenticated user who can create and read scaffolder tasks may be able to see sensitive values in task logs of @backstage/plugin-scaffolder-backend versions before 4.1.0. Exploitation requires a denied action whose input contains such a value, and deployments with restrictive action permissions and affected templates are the ones at risk. Upgrade to @backstage/plugin-scaffolder-backend 4.1.0 or later; until then, restrict scaffolder task creation and log reading to trusted users and avoid putting centrally managed sensitive values in inputs to actions that may be denied.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 17th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.