CVE-2026-106507 json
Backstage: TechDocs arbitrary file read via mkdocs snippets
published last mo. modified last mo. also EUVD-2026-94072
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
Backstage is an open framework for building developer portals. Prior to 1.15.4, the @backstage/plugin-techdocs-node package is affected by techdocs arbitrary file read via mkdocs snippets. Unsafe path resolution in TechDocs source tree handling allows an authenticated user who can register documentation sources to include content from outside the intended documentation boundary. Depending on deployment, this may expose files readable by the build process. This issue is fixed in version 1.15.4.
Patch / fix
- linuxfoundation backstage_plugin-techdocs-node 1.15.4
- linuxfoundation backstage 1.54.6
Is CVE-2026-106507 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- backstage backstage
- @backstage/plugin-techdocs-node plugin-techdocs-node
Classification
References
-
github.com
/backstage/backstage/commit/911ca36f10e654c5517da029129230fc05a4f580
patch
-
github.com
/backstage/backstage/releases/tag/v1.54.6
patch, release-notes
-
github.com
/backstage/backstage/security/advisories/GHSA-vmqh-7cj9-mvcj
mitigation, vendor-advisory
Sources
- CVE List CVE-2026-106507
- NVD CVE-2026-106507
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.