CVE-2026-106491: Backstage · Improper input validation in proxy-backend
Affects @backstage/plugin-proxy-backendSource GCVE Database
Not known to be exploited · CVSS 6.4 Medium : upgrade to 0.6.17 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade @backstage/plugin-proxy-backend to 0.6.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@backstage/plugin-proxy-backend | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @backstage/plugin-proxy-backend to version 0.6.17 or later to apply the official fix. Alternatively, deploy a reverse proxy or web application firewall (WAF) in front of Backstage to normalize request paths before they reach the backend, mitigating the risk of path traversal via crafted URLs.
Description
An authenticated user of Backstage can exploit improper input validation in the proxy-backend plugin to cause the proxy to forward requests to paths outside the intended base path on configured target servers. This vulnerability requires authentication and affects versions of @backstage/plugin-proxy-backend prior to 0.6.17. A patch is available in version 0.6.17. As a workaround, deploying a reverse proxy or WAF to normalize request paths can mitigate the issue.
References
- github.com/backstage/backstage/security/advisories/GHSA-9ghw-48h5-v2w5 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-106491 (opens in a new tab)
- github.com/backstage/backstage/commit/233287d0ce3133e41549bf92a7470c940a41753c (opens in a new tab)
- github.com/backstage/backstage (opens in a new tab)
- github.com/backstage/backstage/releases/tag/v1.54.6 (opens in a new tab)