Skip to content
Heist/ feed
Back to feed
MediumFix available

Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization

Type: advisorySources: OSV

### Impact Several Passport-based authentication providers use shared OAuth profile normalization from `@backstage/plugin-auth-node`. Affected versions may pass an email to email-based sign-in resolvers even when verification metadata supplied for that same address is explicitly negative. The ID-token-only fallback likewise did not consistently respect `email_verified: false`. Exploitation requires a deployment where an admitted identity-provider user can supply or change an email address without verification and Backstage uses that profile email to resolve catalog identities. In that configuration, the user may be able to assume another catalog identity and obtain its associated access and permissions. An absent `email_verified` claim is not by itself considered an affected condition. Some providers rely on authoritative organizational provisioning and intentionally omit the optional claim. Operators using email-based sign-in resolution must ensure that the configured provider restricts sign-in to the intended user population and supplies an authoritative email address, either through provider verification or trusted immutable provisioning. This advisory covers the shared Passport profile normalization path when the selected profile email itself carries `verified: false`, when a matching raw provider email carries `email_verified: false`, or when an email obtained only from an ID token carries `email_verified: false`. It does not apply verification metadata from a different

Products
@backstage/plugin-auth-node
Affected versions
Not specified
Fixed versions
0.6.15, 0.7.5
CVEs
CVE-2026-106460
Confirmed fixed CVEs
Not specified
Updated in this feed
28 Oct 2026, 08:47 UTC · Revision 1

Source evidence

Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization

core-osv · Original source

Published 7 Oct 2026, 20:23 UTC

### Impact Several Passport-based authentication providers use shared OAuth profile normalization from `@backstage/plugin-auth-node`. Affected versions may pass an email to email-based sign-in resolvers even when verification metadata supplied for that same address is explicitly negative. The ID-token-only fallback likewise did not consistently respect `email_verified: false`. Exploitation requires a deployment where an admitted identity-provider user can supply or change an email address without verification and Backstage uses that profile email to resolve catalog identities. In that configuration, the user may be able to assume another catalog identity and obtain its associated access and permissions. An absent `email_verified` claim is not by itself considered an affected condition. Some providers rely on authoritative organizational provisioning and intentionally omit the optional claim. Operators using email-based sign-in resolution must ensure that the configured provider restricts sign-in to the intended user population and supplies an authoritative email address, either through provider verification or trusted immutable provisioning. This advisory covers the shared Passport profile normalization path when the selected profile email itself carries `verified: false`, when a matching raw provider email carries `email_verified: false`, or when an email obtained only from an ID token carries `email_verified: false`. It does not apply verification metadata from a different

osv:GHSA-xm5q-p7w3-x6cp

@backstage/plugin-auth-node

Fixed versions: 0.6.15

@backstage/plugin-auth-node

Fixed versions: 0.7.5

Complete source record
{
  "id": "455098d9c57217164b9907a2ec84cf7db82fbb8aeb13a3ef7534eeebc3337d01",
  "url": "https://osv.dev/vulnerability/GHSA-xm5q-p7w3-x6cp",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization",
    "summary": "### Impact Several Passport-based authentication providers use shared OAuth profile normalization from `@backstage/plugin-auth-node`. Affected versions may pass an email to email-based sign-in resolvers even when verification metadata supplied for that same address is explicitly negative. The ID-token-only fallback likewise did not consistently respect `email_verified: false`. Exploitation requires a deployment where an admitted identity-provider user can supply or change an email address without verification and Backstage uses that profile email to resolve catalog identities. In that configuration, the user may be able to assume another catalog identity and obtain its associated access and permissions. An absent `email_verified` claim is not by itself considered an affected condition. Some providers rely on authoritative organizational provisioning and intentionally omit the optional claim. Operators using email-based sign-in resolution must ensure that the configured provider restricts sign-in to the intended user population and supplies an authoritative email address, either through provider verification or trusted immutable provisioning. This advisory covers the shared Passport profile normalization path when the selected profile email itself carries `verified: false`, when a matching raw provider email carries `email_verified: false`, or when an email obtained only from an ID token carries `email_verified: false`. It does not apply verification metadata from a different ",
    "evidence": "osv:GHSA-xm5q-p7w3-x6cp",
    "products": [
      {
        "name": {
          "value": "@backstage/plugin-auth-node",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "0.6.15",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      },
      {
        "name": {
          "value": "@backstage/plugin-auth-node",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "0.7.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-xm5q-p7w3-x6cp",
      "aliases": [
        "CVE-2026-106460",
        "GHSA-xm5q-p7w3-x6cp"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0.3.0"
                },
                {
                  "fixed": "0.6.15"
                }
              ]
            }
          ],
          "package": {
            "name": "@backstage/plugin-auth-node",
            "purl": "pkg:npm/%40backstage/plugin-auth-node",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-xm5q-p7w3-x6cp/GHSA-xm5q-p7w3-x6cp.json"
          }
        },
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0.7.0"
                },
                {
                  "fixed": "0.7.5"
                }
              ]
            }
          ],
          "package": {
            "name": "@backstage/plugin-auth-node",
            "purl": "pkg:npm/%40backstage/plugin-auth-node",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-xm5q-p7w3-x6cp/GHSA-xm5q-p7w3-x6cp.json"
          }
        }
      ],
      "modified": "2026-10-07T20:30:06.837006795Z",
      "provider": "osv",
      "references": [
        "https://github.com/backstage/backstage/security/advisories/GHSA-xm5q-p7w3-x6cp",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-106460",
        "https://github.com/backstage/backstage/commit/507e65ab9160aae6b602513dbfaebdd6be0ca8bb",
        "https://github.com/backstage/backstage/commit/f0a43dacd1b501064da042b43eab9c1e06371d38",
        "https://github.com/backstage/backstage/commit/fc5e30aba8ea7282ed3658c3b985cec71051cf9d",
        "https://github.com/backstage/backstage",
        "https://github.com/backstage/backstage/releases/tag/v1.49.7",
        "https://github.com/backstage/backstage/releases/tag/v1.54.7"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-287"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": "2026-10-06T21:17:16Z",
        "github_reviewed_at": "2026-10-07T20:23:52Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-106460",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 97237,
  "published_at": "2026-10-07T20:23:52+00:00"
}