CVE-2026-32235: @backstage/plugin-auth-backend: OAuth redirect URI allowlist bypass

Published Mar 12, 2026
·
Updated

Impact

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.

Patches

Upgrade to @backstage/plugin-auth-backend version 0.27.1 or later.

Workarounds

Disable experimental Dynamic Client Registration and Client ID Metadata Documents features if they are not required.

References

- RFC 6749 Section 3.1.2 - Redirection Endpoint

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
npm/@backstage/plugin-auth-backend<0.27.1
0.27.1
linuxfoundation Backstage<=0.27.0

Event History

Mar 12, 2026
Advisory Published
via GitHub·02:50 PM
Data Sourced
via GitHub·02:50 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·06:35 PM
Data Sourced
via MITRE·06:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
Affected Software
Apr 18, 58186
Event
via FIRST·10:11 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-32235?

CVE-2026-32235 is considered a critical vulnerability due to its potential for redirect URI allowlist bypass.

2

How do I fix CVE-2026-32235?

To fix CVE-2026-32235, upgrade to a version of @backstage/plugin-auth-backend that is above 0.27.1.

3

Which versions of @backstage/plugin-auth-backend are affected by CVE-2026-32235?

CVE-2026-32235 affects versions of @backstage/plugin-auth-backend up to and including 0.27.1.

4

What features make systems vulnerable to CVE-2026-32235?

Enabling experimental Dynamic Client Registration or Client ID Metadata Documents with misconfigured allowedRedirectUriPatterns can expose systems to CVE-2026-32235.

5

Can the vulnerability CVE-2026-32235 be exploited remotely?

Yes, CVE-2026-32235 can be exploited remotely if affected configurations are in place.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203