CVE-2026-106488

validatedZero produced an exploit or a check.

GHSA-826h-28h9-65hg ↗EUVD-2026-94007 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
backstage < 0.4.20
fixed in 0.4.20
CWE-287 Improper Authentication
ETK-2026-826, permanent identifier
pkg:npm/@backstage/plugin-auth-backend-module-oidc-provider
+4h34mTTV
20mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+4h34magent stopped
0
+1h
+2h
+3h
+4h
+5h

description

Backstage deployments using the OIDC provider module's email-based identity resolution are affected when their identity provider allows unverified email addresses. An authenticated identity-provider user could be associated with another catalog identity and gain that identity's access permissions.

mitigation

Upgrade the backstage package to 1.54.6 and plugin-auth-backend-module-oidc-provider to 0.4.20. Until upgrades are complete, require verified email addresses from the identity provider or disable email-based identity resolution.

fixed in 0.4.20

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.28%19th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 20:38Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-06 20:38Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-106488

{
  "etk_id": "ETK-2026-826",
  "cve_id": "CVE-2026-106488",
  "display_id": "CVE-2026-106488",
  "ghsa_id": "GHSA-826h-28h9-65hg",
  "euvd_id": "EUVD-2026-94007",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authentication in Backstage OIDC identity resolution",
  "summary": "Backstage deployments using the OIDC provider module's email-based identity resolution are affected when their identity provider allows unverified email addresses. An authenticated identity-provider user could be associated with another catalog identity and gain that identity's access permissions.",
  "mitigation": "Upgrade the backstage package to 1.54.6 and plugin-auth-backend-module-oidc-provider to 0.4.20. Until upgrades are complete, require verified email addresses from the identity provider or disable email-based identity resolution.",
  "vendor": "backstage",
  "product": "backstage",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.4.20"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "0.4.20"
      ],
      "package_name": "@backstage/plugin-auth-backend-module-oidc-provider",
      "purl": "pkg:npm/@backstage/plugin-auth-backend-module-oidc-provider"
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0028,
  "epss_percentile": 0.1927,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 19.783849266666667,
  "t0_at": "2026-10-06T20:38:18.045000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-07T01:12:02.751750+00:00",
      "days": 0.19010077256944444,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T20:38:18.045000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-06T20:38:18.045000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T20:38:18.045000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106488"
    }
  }
}

published 2026-10-07 00:52Z
last change 2026-10-21 16:09Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.