GHSA-4xvq-3m68-h444 CVE-2026-106504
Backstage has sensitive information exposure in scaffolder task logs
- Severity
- 6.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.26%
- Chance of exploitation in the next 30 days. Higher than 17.43% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-532 Insertion of Sensitive Information into Log File
- Fix
4.1.0- Upgrade @backstage/plugin-scaffolder-backend to this version or later
Description
Impact
An authenticated user who can create and read scaffolder tasks may be able to observe sensitive values in task logs in deployments with restrictive action permissions and affected templates. Exploitation requires a denied action whose input contains such a value.
Patches
Patched in @backstage/plugin-scaffolder-backend version 4.1.0
Workarounds
- Restrict scaffolder task creation and task-log reading to trusted users.
- Avoid placing centrally managed sensitive values in inputs to actions that may be denied until upgrading.
References
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| @backstage/plugin-scaffolder-backend | < 4.1.0 |
4.1.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
@backstage/plugin-scaffolder-backend npm → 4.1.0
- npm
npm install @backstage/plugin-scaffolder-backend@4.1.0- yarn
yarn add @backstage/plugin-scaffolder-backend@4.1.0- pnpm
pnpm add @backstage/plugin-scaffolder-backend@4.1.0
Severity breakdown
CVSS 3.1 6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-532: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How to prevent it
- Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Distribution: Remove debug log files before deploying the application into production.
- Operation: Protect log files against unauthorized read/write.
- Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-vwp5-f99x-x3rq Backstage has improper input validation in scaffolder task list ordering | Medium | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-hmp2-4m7g-22cv Backstage: Scaffolder action input authorization bypass | High | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-95p4-vv4g-jxxm Backstage may expose sensitive information in Scaffolder task failure events | Medium | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-g2v8-7jhw-pp8p Backstage: Sensitive information exposure in Scaffolder | Critical | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-xvgh-hmx8-9xxf Backstage: Improper task state validation in Scaffolder backend | High | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-mfvq-x7vr-rgqg Backstage: Secret-derived values may be exposed in scaffolder task logs | Medium | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-29gx-h2m3-xw44 Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback | Medium | Also affects @backstage/plugin-scaffolder-backend |
| GHSA-7hfw-grcm-cqm6 Backstage: Incorrect authorization in scaffolder task listing | Medium | Also affects @backstage/plugin-scaffolder-backend |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor