Security readout for executives and security teams
Plain-English summary
This is a low-severity SSRF issue in Backstage’s auth backend. It only applies when an experimental client metadata feature is explicitly enabled. A redirect could cause the server to contact an internal address, but sources say the attacker cannot read the response body or control headers or method.
Executive priority
Treat as routine remediation unless your Backstage portal enables the experimental CIMD metadata feature. Prioritize verification, then upgrade affected instances during the next normal patch cycle or sooner if exposed.
Technical view
@backstage/plugin-auth-backend before 0.27.1 validates the initial client_id hostname against private IP ranges when experimental CIMD metadata fetching is enabled. Redirect targets were not given the same validation, creating SSRF risk. Deployments using allowedClientIdPatterns limited to trusted domains are not affected. Fixed in 0.27.1.
Likely exposure
Exposure is limited to Backstage deployments using @backstage/plugin-auth-backend before 0.27.1 with auth.experimentalClientIdMetadataDocuments.enabled set to true. The feature is off by default. Deployments restricting allowedClientIdPatterns to trusted domains are reported unaffected.
Exploitation context
The CVE record reports no KEV listing and the advisory characterizes practical impact as limited. The attacker cannot read internal response bodies and cannot control request headers or method. Exploitation still requires the experimental feature to be enabled.
Researcher notes
The issue is CWE-918 SSRF through redirect handling after initial hostname validation. The advisory states limited impact and no response-body disclosure. Avoid assuming broader internal network read access without additional evidence. Review the patch for redirect validation behavior.
Mitigation direction
- Upgrade @backstage/plugin-auth-backend to version 0.27.1 or later.
- If not needed, keep auth.experimentalClientIdMetadataDocuments.enabled disabled.
- Restrict allowedClientIdPatterns to specific trusted domains where appropriate.
- Review the GitHub advisory and vendor commit for implementation details.
Validation and detection
- Inventory Backstage deployments using @backstage/plugin-auth-backend.
- Check package versions for instances below 0.27.1.
- Review configuration for auth.experimentalClientIdMetadataDocuments.enabled set to true.
- Confirm allowedClientIdPatterns is limited to trusted domains if the feature is enabled.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-32236 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 1.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
1.7LowVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/backstage/backstage/security/advisories/GHSA-qp4c-xg64-7c6xCVE reference · x_refsource_CONFIRM
- https://github.com/backstage/backstage/commit/17038abf2dfdb4abc08a59b1c95af39851de0e07CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.