CVE-2026-25152

Workarounds

• Switch to runIn: docker in your app-config.yaml:

  techdocs:
    generator:
      runIn: docker

• Restrict write access to TechDocs source repositories to trusted users only

References

• https://backstage.io/docs/features/techdocs/configuration

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-25152 has a CVSS score of 5.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.14.1, 1.13.11); upgrading removes the vulnerable code path.

Kodem intelligence

This vulnerability is fixed in @backstage/plugin-techdocs-node version X.X.X. Users should upgrade to this version or later.

1. What is CVE-2026-25152? CVE-2026-25152 is a medium-severity path traversal vulnerability in @backstage/plugin-techdocs-node (npm), affecting versions = 1.14.0. It is fixed in 1.14.1, 1.13.11. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-25152? CVE-2026-25152 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @backstage/plugin-techdocs-node are affected by CVE-2026-25152? @backstage/plugin-techdocs-node (npm) versions = 1.14.0 is affected.
4. Is there a fix for CVE-2026-25152? Yes. CVE-2026-25152 is fixed in 1.14.1, 1.13.11. Upgrade to this version or later.
5. Is CVE-2026-25152 exploitable, and should I be worried? Whether CVE-2026-25152 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-25152 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-25152?
   • Upgrade @backstage/plugin-techdocs-node to 1.14.1 or later
   • Upgrade @backstage/plugin-techdocs-node to 1.13.11 or later