CVE-2026-24048: Backstage has a Possible SSRF when reading from allowed URL's in `backend.reading.allow`
Impact
The FetchUrlReader component, used by the catalog and other plugins to fetch content from URLs, followed HTTP redirects automatically. This allowed an attacker who controls a host listed in backend.reading.allow to redirect requests to internal or sensitive URLs that are not on the allowlist, bypassing the URL allowlist security control.
This is a Server-Side Request Forgery (SSRF) vulnerability that could allow access to internal resources, but it does not allow attackers to include additional request headers.
Patches
This vulnerability is fixed in @backstage/backend-defaults version 0.12.2, 0.13.2, 0.14.1, and 0.15.0. Users should upgrade to this version or later.
Workarounds
- Restrict backend.reading.allow to only trusted hosts that you control and that do not issue redirects - Ensure allowed hosts do not have open redirect vulnerabilities - Use network-level controls to block access from Backstage to sensitive internal endpoints
References
- OWASP SSRF Prevention Cheat Sheet
Other sources
Backstage is an open framework for building developer portals, and @backstage/backend-defaults provides the default implementations and setup for a standard Backstage backend app. Prior to versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0, the FetchUrlReader component, used by the catalog and other plugins to fetch content from URLs, followed HTTP redirects automatically. This allowed an attacker who controls a host listed in backend.reading.allow to redirect requests to internal or sensitive URLs that are not on the allowlist, bypassing the URL allowlist security control. This is a Server-Side Request Forgery (SSRF) vulnerability that could allow access to internal resources, but it does not allow attackers to include additional request headers. This vulnerability is fixed in @backstage/backend-defaults version 0.12.2, 0.13.2, 0.14.1, and 0.15.0. Users should upgrade to this version or later. Some workarounds are available. Restrict backend.reading.allow to only trusted hosts that you control and that do not issue redirects, ensure allowed hosts do not have open redirect vulnerabilities, and/or use network-level controls to block access from Backstage to sensitive internal endpoints.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-24048?
CVE-2026-24048 is classified as a medium severity vulnerability due to its potential for SSRF attacks.
How do I fix CVE-2026-24048?
To fix CVE-2026-24048, upgrade the @backstage/backend-defaults package to version 0.14.1, 0.13.2, or 0.12.2.
What systems are affected by CVE-2026-24048?
CVE-2026-24048 affects versions of the @backstage/backend-defaults package up to 0.14.1, 0.13.2, and below 0.12.2.
What is SSRF in the context of CVE-2026-24048?
SSRF stands for Server-Side Request Forgery, which allows attackers to manipulate a server into fetching resources from internal or external servers.
What component is responsible for the vulnerability in CVE-2026-24048?
The FetchUrlReader component is responsible for the vulnerability in CVE-2026-24048 as it automatically follows HTTP redirects.