CVSS 3.1
8.5 highCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HHigh (8.5) in linuxfoundation. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in @backstage/plugin-techdocs-node 1.15.4.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H@backstage/plugin-techdocs-node (npm): fixed in 1.15.4Explain CVE-2026-106505 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106505?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106505?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106505 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| linuxfoundation:backstage_plugin-techdocs-node | before 1.14.6 |
| linuxfoundation:backstage_plugin-techdocs-node | from 1.15.0 before 1.15.4 |
| linuxfoundation:backstage | before 1.50.5 |
| linuxfoundation:backstage | from 1.51.1 before 1.54.6 |
| linuxfoundation:backstage | 1.51.0 |
| linuxfoundation:backstage | 1.51.0:next0 |
| linuxfoundation:backstage | 1.51.0:next1 |
| linuxfoundation:backstage | 1.51.0:next2 |
| linuxfoundation:backstage | 1.51.0:next3 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-p75x-jh7p-ppcx | npm | @backstage/plugin-techdocs-node | <1.15.4 | 1.15.4 |
Red Hat rates this Moderate.
This vulnerability is rated as Moderate because successful exploitation requires authenticated access and commit permissions to integrated documentation repositories, limiting the threat scope to authorized users. In affected Red Hat Developer Hub and Ansible Automation Platform environments where documentation generation is handled directly by the portal backend, an untrusted configuration file can evade filtering controls. Although command execution occurs on the underlying service host, the prerequisite of write privileges on documentation branches mitigates widespread, unauthenticated exposure.
To reduce the risk of unauthorized code execution, implement the following operational and configuration controls:
1. Restrict repository permissions: Limit write and commit access for repositories configured with TechDocs to trusted contributors only.
2. Code review enforcement: Mandate pull request reviews for all modifications to MkDocs configuration files (such as mkdocs.yml or mkdocs.yaml) prior to merging.
3. Container isolation: In the Backstage configuration (app-config.yaml), configure TechDocs to execute documentation generation inside an isolated container by setting `runIn: docker` instead of `runIn: local`, or offload documentation builds to an external CI/CD pipeline.
Caveat: Container isolation reduces direct host system exposure but does not fully eliminate the vulnerability within the container environment. Modifying application configuration files requires restarting the service for changes to take effect.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Developer Hub 1 | rhdh/rhdh-hub-rhel9 | Fix deferred | |
| Self-service automation portal 2 | ansible-automation-platform/automation-portal | Affected | |
| Self-service automation portal 2 | ansible-automation-platform/bootc-automation-portal-rhel9 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106505.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.