CVE-2026-73563: @backstage/plugin-auth-backend Unauthenticated OAuth Account Takeover Vulnerability

MODERATE
Advisory Identifier: GHSA-38hq-7x33-php4
CVSS 4.7
CWE-601
Published
Advisory Summary

CVE-2026-73563 is a MODERATE (CVSS 4.7) unauthenticated oauth account takeover vulnerability (CWE-601: URL Redirection to Untrusted Site ('Open Redirect')) affecting @backstage/plugin-auth-backend libraries in the npm ecosystem. The issue involves unauthenticated oauth account takeover via `redirect_uri` allowlist bypass. Remediation is available by upgrading affected packages to version 0.29.2.

CVE-2026-73563 at a Glance

CVE Identifier CVE-2026-73563
GHSA Identifier GHSA-38hq-7x33-php4
Severity MODERATE
CVSS v3.1 Base Score 4.7
CWE Classification CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Affected Product @backstage/plugin-auth-backend
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 4.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-73563

To remediate this vulnerability, upgrade all affected @backstage/plugin-auth-backend dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@backstage/plugin-auth-backend fixed: 0.29.2
npm install @backstage/plugin-auth-backend@0.29.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @backstage/plugin-auth-backend

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-73563, inspect your project dependencies using npm:

npm ls @backstage/plugin-auth-backend

Analyze the terminal output to locate any version of @backstage/plugin-auth-backend in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.29.2), your application is affected.

Note: The npm ls @backstage/plugin-auth-backend command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect'), where the web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. In @backstage/plugin-auth-backend, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact The allowlist matching used by the experimental dynamic client registration and client ID metadata document (CIMD) features in `@backstage/plugin-auth-backend` matched glob patterns against the full URL string. A * wildcard could therefore match across URL component boundaries: a pattern such as `https://*.example.com/callback`, intended to allow subdomains of a trusted host, would also match an attacker-controlled URL such as `https://attacker.example/x.example.com/callback`. This applies to `auth.experimentalDynamicClientRegistration.allowedRedirectUriPatterns` as well as the `allowedClientIdPatterns` and `allowedRedirectUriPatterns` options of `auth.experimentalClientIdMetadataDocuments`. An attacker could use this to register an OAuth client whose redirect URI points to a host they control while still passing the allowlist, causing authorization codes to be delivered to the attacker when a victim completes an authorization flow. In addition, allowlist patterns without an explicit protocol could match URLs with any protocol, and redirect URIs containing embedded credentials (user:pass@host) were accepted after the credentials were stripped for matching. The practical impact is limited. Both features are experimental and disabled by default, and the default allowlist patterns only reference fixed or loopback hosts and are not affected. Deployments are only impacted if they enable one of these features and configure custom allowlist patterns that contain a wildcard in the hostname, or patterns without an explicit protocol. ### Patches Patched in `@backstage/plugin-auth-backend` version `0.29.2`. Patterns are now matched against each URL component separately so that wildcards no longer match across the host and path boundary, patterns without an explicit protocol are rejected as invalid configuration, and redirect URIs with embedded credentials are always rejected. Note that as part of this fix, a wildcard port no longer implicitly matches every path: a pattern such as `http://localhost:*` now only matches the root path. Use `http://localhost:*/*` to allow any port and any path. ### Workarounds Disable the experimental features by removing `auth.experimentalDynamicClientRegistration` and `auth.experimentalClientIdMetadataDocuments` from your `app-config`, which is the default configuration. Alternatively, restrict the configured allowlist patterns to fully specified URLs with an explicit protocol and no wildcard in the hostname, which are not affected by this vulnerability.

CVE-2026-73563 Affected @backstage/plugin-auth-backend Versions

1 component(s)
Fixed Versions:
0.29.2
Product / Package Ecosystem Affected Versions Fixed Version
@backstage/plugin-auth-backend
npm
< 0.29.2
0.29.2

References

Frequently Asked Questions

What is CVE-2026-73563?
CVE-2026-73563 is a security vulnerability in @backstage/plugin-auth-backend involving Unauthenticated OAuth account takeover via `redirect_uri` allowlist bypass under CWE-601: URL Redirection to Untrusted Site ('Open Redirect').
Which @backstage/plugin-auth-backend versions are affected?
Affected versions include releases prior to 0.29.2 across affected packages: @backstage/plugin-auth-backend.
What version fixes CVE-2026-73563?
Upgrading to 0.29.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @backstage/plugin-auth-backend affected?
Yes, @backstage/plugin-auth-backend is affected in releases prior to 0.29.2. Upgrade your dependency to 0.29.2 or later.
What is the CVSS score of CVE-2026-73563?
CVE-2026-73563 has a CVSS v3.1 base score of 4.7 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2026-73563?
CVE-2026-73563 is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect') (The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.).
How can I check npm dependencies for CVE-2026-73563?
Run the dependency tree command: 'npm ls @backstage/plugin-auth-backend'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-38hq-7x33-php4",
  "modified" : "2026-08-13T17:32:47Z",
  "published" : "2026-07-24T16:20:59Z",
  "aliases" : [ "CVE-2026-73563" ],
  "summary" : "@backstage/plugin-auth-backend: Unauthenticated OAuth account takeover via `redirect_uri` allowlist bypass",
  "details" : "### Impact\nThe allowlist matching used by the experimental dynamic client registration and client ID metadata document (CIMD) features in `@backstage/plugin-auth-backend` matched glob patterns against the full URL string. A * wildcard could therefore match across URL component boundaries: a pattern such as `https://*.example.com/callback`, intended to allow subdomains of a trusted host, would also match an attacker-controlled URL such as `https://attacker.example/x.example.com/callback`. This applies to `auth.experimentalDynamicClientRegistration.allowedRedirectUriPatterns` as well as the `allowedClientIdPatterns` and `allowedRedirectUriPatterns` options of `auth.experimentalClientIdMetadataDocuments`.\n\nAn attacker could use this to register an OAuth client whose redirect URI points to a host they control while still passing the allowlist, causing authorization codes to be delivered to the attacker when a victim completes an authorization flow. In addition, allowlist patterns without an explicit protocol could match URLs with any protocol, and redirect URIs containing embedded credentials (user:pass@host) were accepted after the credentials were stripped for matching.\n\nThe practical impact is limited. Both features are experimental and disabled by default, and the default allowlist patterns only reference fixed or loopback hosts and are not affected. Deployments are only impacted if they enable one of these features and configure custom allowlist patterns that contain a wildcard in the hostname, or patterns without an explicit protocol.\n\n### Patches\nPatched in `@backstage/plugin-auth-backend` version `0.29.2`. Patterns are now matched against each URL component separately so that wildcards no longer match across the host and path boundary, patterns without an explicit protocol are rejected as invalid configuration, and redirect URIs with embedded credentials are always rejected.\n\nNote that as part of this fix, a wildcard port no longer implicitly matches every path: a pattern such as `http://localhost:*` now only matches the root path. Use `http://localhost:*/*` to allow any port and any path.\n\n### Workarounds\nDisable the experimental features by removing `auth.experimentalDynamicClientRegistration` and `auth.experimentalClientIdMetadataDocuments` from your `app-config`, which is the default configuration. Alternatively, restrict the configured allowlist patterns to fully specified URLs with an explicit protocol and no wildcard in the hostname, which are not affected by this vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@backstage/plugin-auth-backend"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.29.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.29.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/backstage/backstage/security/advisories/GHSA-38hq-7x33-php4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/backstage/backstage/commit/274acc51d22a7dd919cdda49d9086cf12c0b8711"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/backstage/backstage/commit/6370e53bce8b227c63092300594ffde29c006886"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/backstage/backstage/commit/ef606a85545cb6d765e20afd1ff43ae5407a3660"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/backstage/backstage/commit/fdc0d2dcd9a571e3839d7f5de4133c4e242a3a41"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/backstage/backstage"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/backstage/backstage/releases/tag/v1.53.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-601" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T16:20:59Z",
    "nvd_published_at" : null
  }
}