CVSS 3.1
7.7 highCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:LHigh (7.7) in linuxfoundation. EPSS 0.5% 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:L/A:L@backstage/plugin-techdocs-node (npm): fixed in 1.15.4Explain CVE-2026-106510 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106510?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106510?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-106510 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-4488-j8vj-vqqv | npm | @backstage/plugin-techdocs-node | <1.15.4 | 1.15.4 |
Red Hat rates this Important.
This vulnerability is rated as Important because authenticated users permitted to register catalog entities can trigger arbitrary system commands on the backend build host. In Red Hat Developer Hub and Ansible Automation Platform environments utilizing in-tree TechDocs generation, an attacker can leverage malicious documentation configurations to compromise the host system. The impact is limited to deployments where untrusted catalog ingestion is permitted and documentation builds are not delegated to isolated external runners.
To mitigate this vulnerability, implement the following operational and configuration controls:
1. Isolate documentation builds:
Configure TechDocs to delegate builds to an external pipeline rather than executing them locally on the portal host. In `app-config.yaml`, set:
```yaml
techdocs:
builder: 'external'
```
Warning: Applying configuration changes to `app-config.yaml` requires restarting or redeploying the service to take effect. Delegating to external builders requires generating documentation through external CI/CD pipelines or dedicated build runners.
2. Restrict catalog registration:
Restrict catalog registration privileges to authorized administrators through role-based access control (RBAC) and permission policies, preventing untrusted users from registering components with custom documentation paths.
3. Audit catalog repositories:
Inspect existing entity repositories and their `mkdocs.yml` files for untrusted or unexpected `markdown_extensions` declarations before documentation builds are processed.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Developer Hub 1 | rhdh/rhdh-hub-rhel9 | Affected | |
| 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-106510.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.