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

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

GHSA-9p5w-h4pr-fcrc ↗

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/electron >= 1.5.0-beta.12, < 1.7.16; >= 1.8.0-beta.0, < 1.8.0-beta.5
fixed in 1.7.16, 1.8.0-beta.5
CWE-201 Insertion of Sensitive Information Into Sent Data
ETK-2026-3451Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:npm/@better-auth/electron
4h 12msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+4h02m
0
+2h
+6h
+8h

description

Servers using @better-auth/electron from 1.5.0-beta.12 onward may disclose authentication and social-provider client secrets during sign-in, allowing a user who can authenticate to impersonate other known-email users. A separate second-factor bypass affects deployments that enable twoFactor(), register electron() first, and permit password sign-in for users enrolled in two-factor authentication.

mitigation

Upgrade both @better-auth/electron and better-auth to 1.7.16, or to 1.8.0-beta.5 on the beta release line. Rotate the authentication secret and all configured social-provider client secrets; remove the electron() plugin until upgrade if necessary.

fixed in 1.7.16, 1.8.0-beta.5

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
12m
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, 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-11-03 21:38Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3451",
  "cve_id": null,
  "display_id": "ETK-2026-3451",
  "ghsa_id": "GHSA-9p5w-h4pr-fcrc",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Secret disclosure and two-factor bypass in @better-auth/electron",
  "summary": "Servers using @better-auth/electron from 1.5.0-beta.12 onward may disclose authentication and social-provider client secrets during sign-in, allowing a user who can authenticate to impersonate other known-email users. A separate second-factor bypass affects deployments that enable twoFactor(), register electron() first, and permit password sign-in for users enrolled in two-factor authentication.",
  "mitigation": "Upgrade both @better-auth/electron and better-auth to 1.7.16, or to 1.8.0-beta.5 on the beta release line. Rotate the authentication secret and all configured social-provider client secrets; remove the electron() plugin until upgrade if necessary.",
  "vendor": "npm",
  "product": "npm:@better-auth/electron",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.5.0-beta.12, < 1.7.16"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.7.16"
      ],
      "package_name": "@better-auth/electron",
      "purl": "pkg:npm/@better-auth/electron"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.8.0-beta.0, < 1.8.0-beta.5"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.8.0-beta.5"
      ],
      "package_name": "@better-auth/electron",
      "purl": "pkg:npm/@better-auth/electron"
    }
  ],
  "cwes": [
    201
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/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": 11.643129583333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T21:38:09+00:00",
      "days": -0.34320686113425924,
      "is_lower_bound": true,
      "measured_at": "2026-11-04T05:52:22.190481+00:00",
      "url": "https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc"
    }
  }
}

published 2026-11-04 04:50Z
last change 2026-11-04 05:49Z

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.