# CVE-2026-106460: Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization > Attackers can bypass email verification checks to assume other catalog identities and gain unauthorized access in Backstage developer portals. - **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** GHSA-xm5q-p7w3-x6cp ## What is CVE-2026-106460? CVE-2026-106460 is a medium-severity authentication bypass vulnerability in Linuxfoundation Backstage, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Backstage is an open framework for building developer portals. From 0.3.0 until 0.6.15 and 0.7.5, the @backstage/plugin-auth-node package did not consistently honor explicit negative email verification during shared OAuth profile normalization. The affected paths include a selected profile email marked verified: false, a matching raw provider email marked email_verified: false, and an email obtained only from an ID token marked email_verified: false. Exploitation requires an admitted identity-provider user who can supply or change an unverified email and a deployment that uses the selected profile email to resolve catalog identities. The verification metadata must apply to the selected email; an absent email_verified claim alone is not affected. In an affected configuration, the user may assume another catalog identity and obtain its associated access and permissions. This issue is fixed in versions 0.6.15 and 0.7.5. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2026-106460? 4 open source packages ship an affected version, including @backstage/plugin-auth-node. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@backstage/plugin-auth-node` | npm | From 0.3.0 | 0.6.15 | | `@backstage/plugin-auth-node` | npm | From 0.3.0 | 0.6.15 | | `@backstage/plugin-auth-node` | npm | From 0.7.0 | 0.7.5 | | `@backstage/plugin-auth-node` | npm | From 0.7.0 | 0.7.5 | Products: Linuxfoundation Backstage, Linuxfoundation Backstage\/Plugin-Auth-Node. ## How do I fix CVE-2026-106460? Upgrade @backstage/plugin-auth-node to a fixed version for your release line: 0.6.15 or 0.7.5. ## Is CVE-2026-106460 being exploited? There is no known exploitation of CVE-2026-106460 in the wild and no public exploit code. ## Other vulnerabilities in Linuxfoundation Backstage - [CVE-2026-106501](https://insights.sbomify.com/CVE-2026-106501/): Backstage: Sensitive information exposure in Scaffolder (critical 9.6) - [CVE-2026-106558](https://insights.sbomify.com/CVE-2026-106558/): Backstage: Improper validation of TechDocs MkDocs configuration (high 8.8) - [CVE-2026-88064](https://insights.sbomify.com/CVE-2026-88064/): Backstage: Improper input validation in TechDocs MkDocs configuration (high 8.8) - [CVE-2026-106459](https://insights.sbomify.com/CVE-2026-106459/): Backstage: Improper input validation in Sentry scaffolder actions (high 8.5) - [CVE-2026-106486](https://insights.sbomify.com/CVE-2026-106486/): Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-106460 and fix it if it is affected. What it is: CVE-2026-106460 is a medium-severity authentication bypass vulnerability in Linuxfoundation Backstage, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-106460 in the wild and no public exploit code. Affected packages and fixed versions: - @backstage/plugin-auth-node (npm): affected from 0.3.0; fixed in 0.6.15 - @backstage/plugin-auth-node (npm): affected from 0.3.0; fixed in 0.6.15 - @backstage/plugin-auth-node (npm): affected from 0.7.0; fixed in 0.7.5 - @backstage/plugin-auth-node (npm): affected from 0.7.0; fixed in 0.7.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-106460/ (Markdown: https://insights.sbomify.com/CVE-2026-106460/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106460 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106460 - OSV: https://osv.dev/vulnerability/CVE-2026-106460 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-106460/ Summaries are generated and may contain mistakes; the official description above is the record.