dbcve.org
Backstage\/plugin Scaffolder BackendPlugin / extension · Linuxfoundation

CVE-2026-29184

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-07
Fix available
A fix is available. Upgrade to 3.1.4 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Backstage is an open framework for building developer portals. Prior to version 3.1.4, a malicious scaffolder template can bypass the log redaction mechanism to exfiltrate secrets provided run through task event logs. This issue has been patched in version 3.1.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Backstage scaffolder templates have a log redaction mechanism intended to prevent secrets from appearing in task event logs. Prior to version 3.1.4, a malicious scaffolder template could bypass this redaction mechanism, allowing exfiltration of secrets that were passed through the task event logging system.

MitigationUpgrade Backstage to version 3.1.4 or later to apply the patch that fixes the log redaction bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Backstage\/plugin Scaffolder BackendPlugin / extension
Affected:< 3.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Scaffolder Backend version
    Run 'npm list @backstage/plugin-scaffolder-backend' or inspect your package.json dependencies to find the installed version of @backstage/plugin-scaffolder-backend
    Affected if The installed version is below 3.1.4 (e.g., 3.1.3, 3.1.0, etc.)
  2. Confirm Scaffolder plugin is enabled
    Verify that the @backstage/plugin-scaffolder-backend package is present in your Backstage installation and the scaffolder backend plugin is loaded in your app configuration
    Affected if The Scaffolder backend plugin is actively running in your Backstage instance
  3. Identify template creation access
    Review your Backstage permissions and catalog configuration to determine which users or entities can create or modify scaffolder templates
    Affected if Untrusted or non-admin users have permissions to create, modify, or submit scaffolder templates in your Backstage instance
  4. Check for secrets in template parameters
    Review your scaffolder template YAML files (typically in templates/ directories) to identify any templates that accept sensitive values as parameters that could be logged
    Affected if Any scaffolder templates accept parameters containing secrets, credentials, tokens, or other sensitive values that could be passed to the task event logging system

You are affected if your installed @backstage/plugin-scaffolder-backend version is below 3.1.4 AND untrusted users can create or modify scaffolder templates that handle secrets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.4 or later
Fixed in 3.1.4
Interim mitigation

Upgrade Backstage to version 3.1.4 or later to apply the patch that fixes the log redaction bypass vulnerability.

Recommended fix High confidence

@backstage/plugin-scaffolder-backend version 3.1.4

  1. 1. Identify the package.json file in your Backstage project that contains @backstage/plugin-scaffolder-backend
  2. 2. Locate the version of @backstage/plugin-scaffolder-backend currently installed (check package.json or run npm list @backstage/plugin-scaffolder-backend)
  3. 3. Update the version of @backstage/plugin-scaffolder-backend to version 3.1.4 or later in package.json
  4. 4. Run npm install to update the dependency
  5. 5. Rebuild and redeploy your Backstage instance to apply the patched version
Caveat Review the Backstage v3.1.4 changelog for any breaking changes specific to your implementation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Backstage\/plugin Scaffolder Backend Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29184 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data