2vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate2 (100.0%)
- Low0 (0.0%)
backstage-plugin-proxy-backend
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 2ModerateAffects 2 versions
- 0LowAffects 0 versions
Monthly breakdown
- 2 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 2
- Low: 0
Vulnerabilities (2)
Known vulnerabilities affecting backstage-plugin-proxy-backend, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| GHSA-472h-9c5j-prrr | Moderate | Backstage: Inconsistent credential enforcement for overlapping proxy routes### Impact An operator can configure overlapping proxy paths with different credential requirements. When a parent path permits unauthenticated access and a nested path requires credentials, the parent exemption can also cover requests handled by the nested proxy. An unauthenticated caller may therefore reach the nested upstream through Backstage, including with static upstream credentials configured for that proxy. Exploitation requires this specific overlapping route configuration. The resulting confidentiality and integrity impact depends on the capabilities exposed by the nested upstream |
| GitHub (opens in a new tab) | |
| GHSA-9ghw-48h5-v2w5 | Moderate | 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. ### 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. |
| GitHub (opens in a new tab) |
- GHSA-472h-9c5j-prrrModerateBackstage: Inconsistent credential enforcement for overlapping proxy routes
>= 0.5.0, < 0.6.18
### Impact An operator can configure overlapping proxy paths with different credential requirements. When a parent path permits unauthenticated access and a nested path requires credentials, the parent exemption can also cover requests handled by the nested proxy. An unauthenticated caller may therefore reach the nested upstream through Backstage, including with static upstream credentials configured for that proxy. Exploitation requires this specific overlapping route configuration. The resulting confidentiality and integrity impact depends on the capabilities exposed by the nested upstream
CVE: CVE-2026-106456
- GHSA-9ghw-48h5-v2w5ModerateBackstage: Improper input validation in proxy-backend
< 0.6.17
### 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.
CVE: CVE-2026-106491