Plugin Auth Backend
Approved changes feed: RSS · Atom
cpe:2.3:a:@backstage:plugin-auth-backend:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | @Backstage (5ceb9f58-6325-5869-8c10-7ca92d58d4c7) |
|---|---|
| Product | Plugin Auth Backend (9ddd6091-18d8-5034-b9e3-b50fcc8e544e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-32236 |
vulnerable | 2026-06-03 15:20:42.589959 |
@backstage/plugin-auth-backend: SSRF in experimental CIMD metadata fetch
Backstage is an open framework for building developer portals. Prior to 0.27.1, a Server-Side Request Forgery (SSRF) vulnerability exists in @backstage/plugin-auth-backend when auth.experimentalClientIdMetadataDocuments.enabled is set to true. The CIMD
metadata fetch validates the initial client_id hostname against private IP ranges but does not apply the same validation after HTTP redirects. The practical impact is limited. The attacker cannot read the response body from the internal request, cannot control request headers or method, and the feature must be explicitly enabled via an experimental flag that is off by default. Deployments that restrict allowedClientIdPatterns to specific trusted domains are not affected. Patched in @backstage/plugin-auth-backend version 0.27.1.
Published: 2026-03-12T18:37:11.330Z
Updated: 2026-04-15T20:46:50.517Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-32235 |
vulnerable | 2026-06-03 15:20:42.588491 |
@backstage/plugin-auth-backend: OAuth redirect URI allowlist bypass
MEDIUM (5.9)
Backstage is an open framework for building developer portals. Prior to 0.27.1, the experimental OIDC provider in @backstage/plugin-auth-backend is vulnerable to a redirect URI allowlist bypass. Instances that have enabled experimental Dynamic Client Registration or Client ID Metadata Documents and configured allowedRedirectUriPatterns are affected. A specially crafted redirect URI can pass the allowlist validation while resolving to an attacker-controlled host. If a victim approves the resulting OAuth consent request, their authorization code is sent to the attacker, who can exchange it for a valid access token. This requires victim interaction and that one of the experimental features is explicitly enabled, which is not the default. This vulnerability is fixed in 0.27.1.
Published: 2026-03-12T18:35:06.325Z
Updated: 2026-03-12T20:46:46.618Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.