CVE-2026-76949

validatedZero produced an exploit or a check.

GHSA-hh34-374j-pfr5 ↗EUVD-2026-82578 ↗

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.10.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-290 Authentication Bypass by Spoofing
ETK-2026-3855Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:hex/ash_authentication
+51dTTV
44mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+51dagent stopped
0
+10d
+20d
+30d
+40d

description

ash_authentication 4.10.0 through 4.14.2 and 5.0.0-rc.0 through 5.0.0-rc.13 can accept a forged remember-me state over an existing authenticated session. An attacker able to place a cookie in a victim's browser can switch the victim into the attacker's account when remember-me is enabled in the browser pipeline and token presence is not required.

mitigation

Upgrade 4.x deployments to 4.15.0 or 5.0 release-candidate deployments to 5.0.0-rc.14. Until upgrading, require token presence for authentication where supported, or remove the remember-me plug from the browser pipeline.

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
44m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-17 21:57Z
Δ 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 21:57Z
  2. 2026-09-17 21:57Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3855",
  "cve_id": "CVE-2026-76949",
  "display_id": "CVE-2026-76949",
  "ghsa_id": "GHSA-hh34-374j-pfr5",
  "euvd_id": "EUVD-2026-82578",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Remember-me authentication bypass in ash_authentication",
  "summary": "ash_authentication 4.10.0 through 4.14.2 and 5.0.0-rc.0 through 5.0.0-rc.13 can accept a forged remember-me state over an existing authenticated session. An attacker able to place a cookie in a victim's browser can switch the victim into the attacker's account when remember-me is enabled in the browser pipeline and token presence is not required.",
  "mitigation": "Upgrade 4.x deployments to 4.15.0 or 5.0 release-candidate deployments to 5.0.0-rc.14. Until upgrading, require token presence for authentication where supported, or remove the remember-me plug from the browser pipeline.",
  "vendor": "erlang",
  "product": "ash_authentication",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.10.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": [
    290
  ],
  "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": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 43.86381793333333,
  "t0_at": "2026-09-17T21:57:50.146000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-07T18:56:52.350378+00:00",
      "days": 50.874331069189815,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T21:57:50.146000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-17T21:57:50.146000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-17T21:57:50.146000+00:00",
      "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-hh34-374j-pfr5"
    }
  }
}

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.