CVE-2026-85500

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

GHSA-fc47-6pgw-wh22 ↗EUVD-2026-81487 ↗

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.3.8, <= 4.14.2; >= 5.0.0-rc.0, <= 5.0.0-rc.13
fixed in 4.15.0, 5.0.0-rc.14
CWE-287 Improper Authentication
ETK-2026-4480Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:hex/ash_authentication
4d 03h 23msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1397h33m
0
+2h
+4h
+6h
+8h
+10h

description

ash_authentication versions before 4.15.0 and 5.0.0-rc.14 can allow an unconfirmed account to obtain a session when confirmation is required. This can affect directly exposed token sign-in or password-registration actions, including API routes, and may also affect configurations where the confirmation field is not selected or is hidden by a field policy.

mitigation

Upgrade ash_authentication to 4.15.0 or later, or to 5.0.0-rc.14 or later on the 5.0 release-candidate line. Until upgraded, do not expose the affected actions without an application-level confirmation check; ensure the confirmation field is selected and not hidden by a field policy.

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.
0.77%56th percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-17 13:09Z
Δ 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 13:09Z
  2. 2026-09-17 13:09Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4480",
  "cve_id": "CVE-2026-85500",
  "display_id": "CVE-2026-85500",
  "ghsa_id": "GHSA-fc47-6pgw-wh22",
  "euvd_id": "EUVD-2026-81487",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Confirmation bypass in ash_authentication sign-in flows",
  "summary": "ash_authentication versions before 4.15.0 and 5.0.0-rc.14 can allow an unconfirmed account to obtain a session when confirmation is required. This can affect directly exposed token sign-in or password-registration actions, including API routes, and may also affect configurations where the confirmation field is not selected or is hidden by a field policy.",
  "mitigation": "Upgrade ash_authentication to 4.15.0 or later, or to 5.0.0-rc.14 or later on the 5.0 release-candidate line. Until upgraded, do not expose the affected actions without an application-level confirmation check; ensure the confirmation field is selected and not hidden by a field policy.",
  "vendor": "erlang",
  "product": "ash_authentication",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.3.8, <= 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.0, <= 5.0.0-rc.13"
      ],
      "ecosystem": "erlang",
      "fixed_versions": [
        "5.0.0-rc.14"
      ],
      "package_name": "ash_authentication",
      "purl": "pkg:hex/ash_authentication"
    }
  ],
  "cwes": [
    287
  ],
  "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": 0.0077,
  "epss_percentile": 0.5618,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.5424992,
  "t0_at": "2026-09-17T13:09:43+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-17T13:09:43+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:09:43+00:00",
      "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-fc47-6pgw-wh22"
    }
  }
}

published 2026-11-14 18:14Z
last change 2026-11-18 21:43Z

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.