CVSS 3.1
7.7 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NHigh (7.7) in linuxfoundation. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @backstage/plugin-techdocs-node 1.14.7, 1.15.5.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N@backstage/plugin-techdocs-node (npm): fixed in 1.14.7, 1.15.5Explain CVE-2026-106455 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106455?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106455?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-106455 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 | from 0.11.12 before 1.14.7 |
| linuxfoundation:backstage_plugin-techdocs-node | from 1.15.0 before 1.15.5 |
| linuxfoundation:backstage | from 0.71.1 before 1.50.6 |
| linuxfoundation:backstage | from 1.51.1 before 1.54.8 |
| 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-q38j-6vcm-2f5m | npm | @backstage/plugin-techdocs-node | >=0.11.12 <1.14.7 | 1.14.7 |
| GHSA-q38j-6vcm-2f5m | npm | @backstage/plugin-techdocs-node | >=1.15.0 <1.15.5 | 1.15.5 |
Red Hat rates this Moderate.
This vulnerability is rated as Moderate impact for Red Hat Developer Hub and Ansible Automation Platform because exploitation requires authenticated privileges to modify documentation source repositories. In typical deployments, generated documentation builds execute within isolated environments where sensitive metadata endpoints enforce token-based authentication, substantially limiting unauthorized data exposure. Furthermore, an attacker cannot achieve arbitrary code execution or compromise host integrity, as the impact is confined to retrieving and publishing information from internal network destinations reachable by the documentation build runner.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Developer Hub 1 | rhdh/rhdh-hub-rhel9 | Not 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-106455.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.