Quick answers
- Is CVE-2026-24048 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24048 being exploited in the wild.
- How severe is CVE-2026-24048?
- Low severity, with a CVSS score of 3.1, published 21 January 2026.
- Which products and versions are affected?
- Backstage Backend-Defaults < 0.12.2, >= 0.13.0 and < 0.13.2, >= 0.14.0 and < 0.14.1.
- Is there a fix for CVE-2026-24048?
- A patch was published on 2026-01-21: Patches released for versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24048 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-24048?
- Check whether you run Backstage Backend-Defaults at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The FetchUrlReader component in Backstage automatically follows HTTP 3xx redirects when fetching remote content for the catalog and other plugins. A server-side request forgery (SSRF) vulnerability exists because redirect destinations are not validated against the `backend.reading.allow` allowlist. An attacker who controls a host listed in the allowlist can issue a redirect to an internal or sensitive URL not on the allowlist, bypassing the security control. The attack requires the attacker to control an allowed host and knowledge of the network topology; attackers cannot inject additional HTTP headers. Patches are available in @backstage/backend-defaults 0.12.2, 0.13.2, 0.14.1, and 0.15.0.
Affected products
- Backstage backend-defaults < 0.12.2, >= 0.13.0 and < 0.13.2, >= 0.14.0 and < 0.14.1
Identifiers
- CVE-2026-24048
- GHSA-q2x5-4xjx-c6p9
Timeline
- 2026-01-21: disclosed
- 2026-01-21: patched: Patches released for versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0