# CVE-2026-106455: Backstage: Improper validation of MkDocs plugin configuration in TechDocs > An authenticated attacker can exploit improper validation in Backstage TechDocs to perform Server-Side Request Forgery and read data from internal network locations. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** GHSA-q38j-6vcm-2f5m ## What is CVE-2026-106455? CVE-2026-106455 is a high-severity server-side request forgery vulnerability in Linuxfoundation Backstage, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Backstage is an open framework for building developer portals. From 0.11.12 until 1.14.7 and 1.15.5, the @backstage/plugin-techdocs-node package is affected by improper validation of mkdocs plugin configuration in techdocs. 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. This issue is fixed in @backstage/plugin-techdocs-node versions 1.14.7 and 1.15.5. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-106455? 4 open source packages ship an affected version, including @backstage/plugin-techdocs-node. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@backstage/plugin-techdocs-node` | npm | From 0.11.12 | 1.14.7 | | `@backstage/plugin-techdocs-node` | npm | From 0.11.12 | 1.14.7 | | `@backstage/plugin-techdocs-node` | npm | From 1.15.0 | 1.15.5 | | `@backstage/plugin-techdocs-node` | npm | From 1.15.0 | 1.15.5 | Products: Linuxfoundation Backstage, Linuxfoundation Backstage Plugin-Techdocs-Node. ## How do I fix CVE-2026-106455? Upgrade @backstage/plugin-techdocs-node to a fixed version for your release line: 1.14.7 or 1.15.5. ## Is CVE-2026-106455 being exploited? There is no known exploitation of CVE-2026-106455 in the wild and no public exploit code. ## Other vulnerabilities in Linuxfoundation Backstage - [CVE-2026-106501](https://insights.sbomify.com/CVE-2026-106501/): Backstage: Sensitive information exposure in Scaffolder (critical 9.6) - [CVE-2026-106558](https://insights.sbomify.com/CVE-2026-106558/): Backstage: Improper validation of TechDocs MkDocs configuration (high 8.8) - [CVE-2026-88064](https://insights.sbomify.com/CVE-2026-88064/): Backstage: Improper input validation in TechDocs MkDocs configuration (high 8.8) - [CVE-2026-106459](https://insights.sbomify.com/CVE-2026-106459/): Backstage: Improper input validation in Sentry scaffolder actions (high 8.5) - [CVE-2026-106486](https://insights.sbomify.com/CVE-2026-106486/): Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-106455 and fix it if it is affected. What it is: CVE-2026-106455 is a high-severity server-side request forgery vulnerability in Linuxfoundation Backstage, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-106455 in the wild and no public exploit code. Affected packages and fixed versions: - @backstage/plugin-techdocs-node (npm): affected from 0.11.12; fixed in 1.14.7 - @backstage/plugin-techdocs-node (npm): affected from 0.11.12; fixed in 1.14.7 - @backstage/plugin-techdocs-node (npm): affected from 1.15.0; fixed in 1.15.5 - @backstage/plugin-techdocs-node (npm): affected from 1.15.0; fixed in 1.15.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-106455/ (Markdown: https://insights.sbomify.com/CVE-2026-106455/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106455 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106455 - OSV: https://osv.dev/vulnerability/CVE-2026-106455 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-106455/ Summaries are generated and may contain mistakes; the official description above is the record.