withdrawn 2026-10-14 23:24Z

This entry duplicated another and was withdrawn in its favour.

Superseded by ETK-2026-1613.

ETK-2026-364Zero's internal tracking ID, independent of the CVE number.

withdrawn
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:better-auth >= 1.5.0-beta.12, < 1.7.7
fixed in 1.7.7
CWE-287 Improper Authentication
ETK-2026-364, no cve assigned
pkg:npm/better-auth
6d 21h 19msince last run
–AI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
0
+2h
+4h
+6h
+8h
+10h
+12h

description

better-auth versions 1.5.0-beta.12 through 1.7.6 are affected when the OAuth Proxy plugin uses cookie-backed sign-in state and lacks a distinct proxy secret for each participating environment. An unauthenticated attacker who knows a user's verified email address may gain access as that user if implicit account linking is enabled.

mitigation

Upgrade better-auth to 1.7.7 and update all packages and nodes participating in the same OAuth or SAML state flow together. Until upgraded, use a dedicated OAuth Proxy secret that differs from each environment's global secret, move state storage to the database, or disable the OAuth Proxy plugin.

fixed in 1.7.7

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
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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: an exploit technique exists, 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.

No signals recorded for this entry yet.

this entry in the feed

GET /api/v1/feed/ETK-2026-364

{
  "etk_id": "ETK-2026-364",
  "cve_id": null,
  "display_id": "ETK-2026-364",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "retired",
  "anchor_state": "awaiting_cve",
  "title": "OAuth proxy authentication bypass in better-auth",
  "summary": "better-auth versions 1.5.0-beta.12 through 1.7.6 are affected when the OAuth Proxy plugin uses cookie-backed sign-in state and lacks a distinct proxy secret for each participating environment. An unauthenticated attacker who knows a user's verified email address may gain access as that user if implicit account linking is enabled.",
  "mitigation": "Upgrade better-auth to 1.7.7 and update all packages and nodes participating in the same OAuth or SAML state flow together. Until upgraded, use a dedicated OAuth Proxy secret that differs from each environment's global secret, move state storage to the database, or disable the OAuth Proxy plugin.",
  "vendor": "npm",
  "product": "npm:better-auth",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.5.0-beta.12, < 1.7.7"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.7.7"
      ],
      "package_name": "better-auth",
      "purl": "pkg:npm/better-auth"
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {}
}

published 2026-10-02 18:04Z
last change 2026-10-14 23:24Z

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.