CVE-2026-24048

Backstage has a Possible SSRF when reading from allowed URL's in `backend.reading.allow`

LOW
3.7
CVSS Score
Published: January 21, 2026 at 10:51 PM UTC
Updated: June 17, 2026 at 10:22 AM UTC
2 products affected across 2 vendorsBackstage /backend DefaultsBackstage

Using backstage by backstage?

Get instant alerts when new vulnerabilities affect backstage - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.12.20.13.0 ≤ v ≤ 0.13.20.14.0 ≤ v ≤ 0.14.1
v < 0.12.2v < 0.13.2v < 0.14.1
Affected range stops below 0.12.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.13.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.14.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-918

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card