CVE-2026-88952

waiting for further signalsZero needs more public information before it can validate it.

GHSA-wc6x-276q-jrf9 ↗EUVD-2026-81619 ↗

no check availablenot proven exploitable
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.
erlang ash_authentication >= 4.14.0, <= 4.14.2; >= 5.0.0-rc.10, <= 5.0.0-rc.13
fixed in 4.15.0, 5.0.0-rc.14
ETK-2026-3856Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:hex/ash_authentication
6h 27msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1228h12m
0
+2h
+4h
+6h
+8h
+10h

description

ash_authentication can incorrectly link an OAuth2 identity to another user's account, allowing an attacker to sign in as that account and potentially alter its email address. This affects deployments using trusted provider email verification with a non-email registration identity or non-email sign-in filter; affected versions are 4.14.0 through 4.14.2 and 5.0.0-rc.10 through 5.0.0-rc.13.

mitigation

Upgrade to ash_authentication 4.15.0 or 5.0.0-rc.14, and configure email_field when the account email is not stored in :email. Until upgraded, disable trusted email verification or ensure registration and sign-in matching use the email attribute; review existing OAuth identity links and unexpected email changes.

fixed in 4.15.0, 5.0.0-rc.14

check
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-17 14:15Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-09-17 14:15Z
  2. 2026-09-17 14:15Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3856",
  "cve_id": "CVE-2026-88952",
  "display_id": "CVE-2026-88952",
  "ghsa_id": "GHSA-wc6x-276q-jrf9",
  "euvd_id": "EUVD-2026-81619",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OAuth2 account-linking authentication bypass in ash_authentication",
  "summary": "ash_authentication can incorrectly link an OAuth2 identity to another user's account, allowing an attacker to sign in as that account and potentially alter its email address. This affects deployments using trusted provider email verification with a non-email registration identity or non-email sign-in filter; affected versions are 4.14.0 through 4.14.2 and 5.0.0-rc.10 through 5.0.0-rc.13.",
  "mitigation": "Upgrade to ash_authentication 4.15.0 or 5.0.0-rc.14, and configure `email_field` when the account email is not stored in `:email`. Until upgraded, disable trusted email verification or ensure registration and sign-in matching use the email attribute; review existing OAuth identity links and unexpected email changes.",
  "vendor": "erlang",
  "product": "ash_authentication",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.14.0, <= 4.14.2"
      ],
      "ecosystem": "erlang",
      "fixed_versions": [
        "4.15.0"
      ],
      "package_name": "ash_authentication",
      "purl": "pkg:hex/ash_authentication"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0-rc.10, <= 5.0.0-rc.13"
      ],
      "ecosystem": "erlang",
      "fixed_versions": [
        "5.0.0-rc.14"
      ],
      "package_name": "ash_authentication",
      "purl": "pkg:hex/ash_authentication"
    }
  ],
  "cwes": null,
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.0938473,
  "t0_at": "2026-09-17T14:15:19.506000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-17T14:15:19.506000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T14:15:19.506000+00:00",
      "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-wc6x-276q-jrf9"
    }
  }
}

published 2026-11-07 18:12Z
last change 2026-11-08 00:08Z

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.