dbcve.org
BackstageApplication · Linuxfoundation

CVE-2026-25152

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-30
Fix available
A fix is available. Upgrade to 1.13.11 / 1.14.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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, and @backstage/plugin-techdocs-node provides common node.js functionalities for TechDocs. In versions of @backstage/plugin-techdocs-node prior to 1.13.11 and 1.14.1, a path traversal vulnerability in the TechDocs local generator allows attackers to read arbitrary files from the host filesystem when Backstage is configured with `techdocs.generator.runIn: local`. When processing documentation from untrusted sources, symlinks within the docs directory are followed by MkDocs during the build process. File contents are embedded into generated HTML and exposed to users who can view the documentation. This vulnerability is fixed in` @backstage/plugin-techdocs-node` versions 1.13.11 and 1.14.1. Some workarounds are available. Switch to `runIn: docker` in `app-config.yaml` and/or restrict write access to TechDocs source repositories to trusted users only.

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

A path traversal vulnerability in @backstage/plugin-techdocs-node allows arbitrary file read from the host filesystem when TechDocs is configured with `runIn: local`. Attackers can place symlinks in documentation directories that MkDocs follows during build, embedding sensitive file contents into generated HTML accessible to users.

MitigationSwitch techdocs.generator.runIn from 'local' to 'docker' in app-config.yaml and/or restrict write access to TechDocs source repositories. Alternatively, upgrade @backstage/plugin-techdocs-node to version 1.13.11 or 1.14.1.

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
BackstageApplication
Affected:< 1.13.11>= 1.14.0, < 1.14.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 @backstage/plugin-techdocs-node version
    Run `npm list @backstage/plugin-techdocs-node` or check your package.json dependencies to see the installed version
    Affected if Version is less than 1.13.11 or between 1.14.0 and 1.14.0.x (inclusive)
  2. Verify TechDocs generator configuration
    Open your app-config.yaml or app-config.local.yaml and search for the `techdocs.generator` section. Look for the `runIn` setting
    Affected if The setting `runIn: local` is present (vulnerable configuration)
  3. Confirm the config is actually loaded
    Check that the techdocs configuration block exists in the active configuration file being used by your Backstage instance
    Affected if The techdocs.generator.runIn setting is explicitly set to 'local' in the deployed config

You are affected if your installed @backstage/plugin-techdocs-node version is in the vulnerable range (below 1.13.11 or 1.14.0.x) AND your TechDocs generator is configured with runIn set to 'local'.

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 1.13.11 / 1.14.1 or later
Fixed in 1.13.111.14.1
Interim mitigation

Switch techdocs.generator.runIn from 'local' to 'docker' in app-config.yaml and/or restrict write access to TechDocs source repositories. Alternatively, upgrade @backstage/plugin-techdocs-node to version 1.13.11 or 1.14.1.

Recommended fix High confidence

@backstage/plugin-techdocs-node version 1.13.11 or 1.14.1

  1. Upgrade @backstage/plugin-techdocs-node to version 1.13.11 or higher (for Backstage 1.13.x line)
  2. Alternatively, upgrade to version 1.14.1 or higher (for Backstage 1.14.x line)
  3. After upgrade, verify TechDocs functionality works as expected

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

Fix this in Backstage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25152 — 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-25152 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