CVE-2026-106556 json
Backstage: Configuration bypass in TechDocs mkdocs.yml sanitization
published last mo. modified 27d ago also EUVD-2026-94370
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
Backstage is an open framework for building developer portals. Prior to 1.14.6, the @backstage/plugin-techdocs-node package is affected by configuration bypass in techdocs mkdocs.yml sanitization. Insufficient validation of MkDocs configuration during TechDocs generation could allow an authenticated user who can register or modify documentation sources to execute arbitrary commands in the build environment. Impact is limited to resources accessible to the TechDocs backend or build container. This issue is fixed in versions 1.14.6 and 1.15.4.
Patch / fix
- linuxfoundation @backstage/plugin-techdocs-node 1.14.6, 1.15.4
- linuxfoundation backstage_plugin-techdocs-node 1.14.6, 1.15.4
Is CVE-2026-106556 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-106556 updated cvss 7.7
plugin-techdocs-node: plugin-techdocs-node: arbitrary command execution via configuration sanitization bypass
-
Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9 Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal, ansible-automation-platform/bootc-automation-portal-rhel9affected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L |
Affected products
- backstage backstage
- @backstage plugin-techdocs-node
Classification
References
-
github.com
/backstage/backstage/commit/25125ee727a3de3418a8fa6a9e458cd5b73ecf26
patch
-
github.com
/backstage/backstage/commit/b6d1aea0bef99b8dfec3c8746032474867ba677a
patch
-
github.com
/backstage/backstage/releases/tag/v1.50.5
patch, release-notes
-
github.com
/backstage/backstage/releases/tag/v1.54.6
patch, release-notes
-
github.com
/backstage/backstage/security/advisories/GHSA-g2hj-v2j6-vfvg
mitigation, vendor-advisory
Sources
- CVE List CVE-2026-106556
- NVD CVE-2026-106556
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.