CVE-2026-82760

validatedZero produced an exploit or a check.

GHSA-q876-xr24-2mcx ↗EUVD-2026-81478 ↗

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.8.0, <= 4.14.2; >= 5.0.0-rc.0, <= 5.0.0-rc.13
fixed in 4.15.0, 5.0.0-rc.14
CWE-407 Inefficient Algorithmic Complexity
ETK-2026-5008Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:hex/ash_authentication
+64dTTV
40mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+64dagent stopped
0
+20d
+40d
+60d

description

AshAuthentication API-key sign-in in affected releases processes attacker-controlled encoded key fields with disproportionate CPU cost before credentials are verified. An unauthenticated remote party that can reach this sign-in path can exhaust CPU resources, with greater exposure when the action accepts request-body input.

mitigation

Upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14, as appropriate for your release line. Until then, reject oversized API-key values at the edge and avoid exposing API-key sign-in through request bodies.

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.
–
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-17 13:08Z
Δ 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:08Z
  2. 2026-09-17 13:08Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-5008",
  "cve_id": "CVE-2026-82760",
  "display_id": "CVE-2026-82760",
  "ghsa_id": "GHSA-q876-xr24-2mcx",
  "euvd_id": "EUVD-2026-81478",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Algorithmic denial of service in ash_authentication API key sign-in",
  "summary": "AshAuthentication API-key sign-in in affected releases processes attacker-controlled encoded key fields with disproportionate CPU cost before credentials are verified. An unauthenticated remote party that can reach this sign-in path can exhaust CPU resources, with greater exposure when the action accepts request-body input.",
  "mitigation": "Upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14, as appropriate for your release line. Until then, reject oversized API-key values at the edge and avoid exposing API-key sign-in through request bodies.",
  "vendor": "erlang",
  "product": "ash_authentication",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.8.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.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": [
    407
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 40.27173991666667,
  "t0_at": "2026-09-17T13:08:46.382000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-20T06:22:51.674234+00:00",
      "days": 63.718116808263886,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:08:46.382000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-17T13:08:46.382000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T13:08:46.382000+00:00",
      "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-q876-xr24-2mcx"
    }
  }
}

published 2026-11-20 05:42Z
last change 2026-11-20 06:48Z

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.