CVE-2026-106491: Backstage: Improper input validation in proxy-backend
Impact An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default.
Published Oct 7, 2026
Affected packages
@backstage/plugin-proxy-backend
- Ecosystem
- npm
- Affected
- < 0.6.17
- Fixed in
- 0.6.17
- Check
npm ls @backstage/plugin-proxy-backend
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default.
Patches
Patched in @backstage/plugin-proxy-backend version 0.6.17
Workarounds
- Deploy a reverse proxy or WAF in front of Backstage that normalizes request paths before they reach the backend.
References
- https://github.com/backstage/backstage/security/advisories/GHSA-9ghw-48h5-v2w5
- https://nvd.nist.gov/vuln/detail/CVE-2026-106491
- https://github.com/backstage/backstage/commit/233287d0ce3133e41549bf92a7470c940a41753c
- https://github.com/backstage/backstage/releases/tag/v1.54.6
- https://github.com/advisories/GHSA-9ghw-48h5-v2w5
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
