CVE-2026-86533

validatedZero produced an exploit or a check.

GHSA-w374-hvrx-66hg ↗EUVD-2026-81486 ↗

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.
erlang ash_authentication >= 4.9.1, <= 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-4481Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:hex/ash_authentication
+58dTTV
13mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+58dagent stopped
0
+20d
+40d

description

ash_authentication deployments using session_identifier :jti without require_token_presence_for_authentication? set to true may continue to accept sessions after they have been revoked. An attacker who already possesses a session value can retain the associated authenticated access until the token expires.

mitigation

Set require_token_presence_for_authentication? to true immediately, then upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14. Reduce session lifetimes while upgrading to limit exposure from previously captured session values.

fixed in 4.15.0, 5.0.0-rc.14

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.91%60th percentile
agent run time
13m
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 check: a technique exists and was validated, but no deterministic check could cover this one.

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-86533

{
  "etk_id": "ETK-2026-4481",
  "cve_id": "CVE-2026-86533",
  "display_id": "CVE-2026-86533",
  "ghsa_id": "GHSA-w374-hvrx-66hg",
  "euvd_id": "EUVD-2026-81486",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Revocation bypass in ash_authentication JTI sessions",
  "summary": "ash_authentication deployments using `session_identifier :jti` without `require_token_presence_for_authentication?` set to `true` may continue to accept sessions after they have been revoked. An attacker who already possesses a session value can retain the associated authenticated access until the token expires.",
  "mitigation": "Set `require_token_presence_for_authentication?` to `true` immediately, then upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14. Reduce session lifetimes while upgrading to limit exposure from previously captured session values.",
  "vendor": "erlang",
  "product": "ash_authentication",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.9.1, <= 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.0091,
  "epss_percentile": 0.6051,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 13.0510355,
  "t0_at": "2026-09-17T13:09:37.963000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-14T18:27:23.635193+00:00",
      "days": 58.220667502233795,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:09:37.963000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-17T13:09:37.963000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:09:37.963000+00:00",
      "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-w374-hvrx-66hg"
    }
  }
}

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.