CVE-2026-106455: Backstage: Improper validation of MkDocs plugin configuration in TechDocs
Impact An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior.
Published Oct 7, 2026
Affected packages
@backstage/plugin-techdocs-node
- Ecosystem
- npm
- Affected
- >= 0.11.12, < 1.14.7
- Fixed in
- 1.14.7
- Check
npm ls @backstage/plugin-techdocs-node
@backstage/plugin-techdocs-node
- Ecosystem
- npm
- Affected
- >= 1.15.0, < 1.15.5
- Fixed in
- 1.15.5
- Check
npm ls @backstage/plugin-techdocs-node
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior.
Patches
Upgrade @backstage/plugin-techdocs-node to a patched version for the applicable release line:
1.14.x: upgrade to1.14.7or later in that line, available in Backstage v1.50.6.1.15.x: upgrade to1.15.5or later, available in Backstage v1.54.8.- Current mainline: upgrade to
2.0.0or later, available in Backstage v1.55.0.
The update removes MkDocs plugins outside the built-in allowlist. To retain additional plugins, review them and configure techdocs.generator.mkdocs.dangerouslyAllowAdditionalPlugins, or supply dangerouslyAllowAdditionalPlugins when creating the generator directly. Plugins supplied through defaultPlugins remain permitted.
Workarounds
- Restrict control of TechDocs source repositories and catalog registration to trusted maintainers.
- Run documentation builders with outbound access to private and link-local networks denied.
- Require token- or header-protected cloud instance metadata services.
References
- https://github.com/backstage/backstage/security/advisories/GHSA-q38j-6vcm-2f5m
- https://nvd.nist.gov/vuln/detail/CVE-2026-106455
- https://github.com/backstage/backstage/commit/28aa82ae2815988721dd7bbf43cd69c431dcd71b
- https://github.com/backstage/backstage/commit/9f76ea445088961f68c364764cc4b7734f368fc0
- https://github.com/backstage/backstage/releases/tag/v1.50.6
- https://github.com/backstage/backstage/releases/tag/v1.54.8
- https://github.com/backstage/backstage/releases/tag/v1.55.0
- https://github.com/advisories/GHSA-q38j-6vcm-2f5m
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-106505
Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend
high7.7Oct 7, 2026CVE-2026-106508
Backstage has potential file exposure through local TechDocs publisher
medium5.3Oct 7, 2026CVE-2026-106509
Backstage: Improper validation of MkDocs theme configuration in TechDocs
high7.7Oct 7, 2026CVE-2026-106510
Backstage: Remote code execution via crafted markdown_extensions in TechDocs mkdocs.yml
high7.7Oct 7, 2026CVE-2026-106557
Backstage has improper input validation in TechDocs Markdown extension configuration
high7.7Oct 7, 2026CVE-2026-106558
Backstage: Improper validation of TechDocs MkDocs configuration
high8.8Oct 7, 2026
