What is CVE-2026-106488?

CVE-2026-106488 is a high-severity improper authentication vulnerability in @backstage/plugin-auth-backend-module-oidc-provider (npm), affecting versions < 0.4.20. It is fixed in 0.4.20. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2026-106488?

CVE-2026-106488 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @backstage/plugin-auth-backend-module-oidc-provider are affected by CVE-2026-106488?

@backstage/plugin-auth-backend-module-oidc-provider (npm) versions < 0.4.20 is affected.

Is there a fix for CVE-2026-106488?

Yes. CVE-2026-106488 is fixed in 0.4.20. Upgrade to this version or later.

Is CVE-2026-106488 exploitable, and should I be worried?

Whether CVE-2026-106488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-106488 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-106488?

Upgrade @backstage/plugin-auth-backend-module-oidc-provider to 0.4.20 or later.

CVE-2026-106488

Q: How severe is CVE-2026-106488?

CVE-2026-106488 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @backstage/plugin-auth-backend-module-oidc-provider are affected by CVE-2026-106488?

@backstage/plugin-auth-backend-module-oidc-provider (npm) versions < 0.4.20 is affected.

Q: Is there a fix for CVE-2026-106488?

Yes. CVE-2026-106488 is fixed in 0.4.20. Upgrade to this version or later.

Q: Is CVE-2026-106488 exploitable, and should I be worried?

Whether CVE-2026-106488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-106488 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-106488?

Upgrade @backstage/plugin-auth-backend-module-oidc-provider to 0.4.20 or later.

Summary

Backstage: Improper authentication in the OIDC provider

Workarounds

Disable email-based sign-in resolution for the OIDC provider, or require the identity provider to verify email addresses before allowing sign-in.

Impact

Deployments using OIDC email-based identity resolution with a provider that permits unverified email addresses may allow an authenticated provider user to assume another catalog identity. This may grant access and permissions associated with that user. No direct availability impact is demonstrated.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-106488 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.20); upgrading removes the vulnerable code path.

Affected versions

@backstage/plugin-auth-backend-module-oidc-provider (< 0.4.20)

Security releases

@backstage/plugin-auth-backend-module-oidc-provider → 0.4.20 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Patched in @backstage/plugin-auth-backend-module-oidc-provider version 0.4.20.

Frequently Asked Questions

What is CVE-2026-106488? CVE-2026-106488 is a high-severity improper authentication vulnerability in @backstage/plugin-auth-backend-module-oidc-provider (npm), affecting versions < 0.4.20. It is fixed in 0.4.20. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2026-106488? CVE-2026-106488 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @backstage/plugin-auth-backend-module-oidc-provider are affected by CVE-2026-106488? @backstage/plugin-auth-backend-module-oidc-provider (npm) versions < 0.4.20 is affected.
Is there a fix for CVE-2026-106488? Yes. CVE-2026-106488 is fixed in 0.4.20. Upgrade to this version or later.
Is CVE-2026-106488 exploitable, and should I be worried? Whether CVE-2026-106488 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-106488 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-106488? Upgrade @backstage/plugin-auth-backend-module-oidc-provider to 0.4.20 or later.