@backstage/plugin-techdocs-node vulnerable to possible Path Traversal in TechDocs Local Generator

published 2026-01-30 9 mo ago modified 2026-06-17 4 mo ago also GHSA-w669-jj7h-88m9 , EUVD-2026-5002

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 links 1

npm @backstage/plugin-techdocs-node 1.13.11, 1.14.1
linuxfoundation backstage 1.13.11, 1.14.1

github.com/backstage/backstage@08f388e commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-25152 updated 2026-10-27 cvss 5.3

@backstage/plugin-techdocs-node: @backstage/plugin-techdocs-node Path Traversal in TechDocs Local Generator

Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9 Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal
affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 9 mo ago (2026-02-02)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	@backstage/plugin-techdocs-node	>=1.14.0, <1.14.1 <1.13.11	1.14.1 1.13.11

Affected products

backstage backstage

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

github.com /backstage/backstage/commit/08f388e3394b133171fe13b62a78caf14407b9c3
web
github.com /backstage/backstage/security/advisories/GHSA-w669-jj7h-88m9
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-25152
advisory
github.com /backstage/backstage
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary