AI Science Tracker

better-auth/electron sign-in response exposes server secrets and can bypass two-factor

@better-auth/electron · AI involvement attributed to Anthropic OSS Scanner

Finding and attribution

A normal desktop sign-in can return the server auth context rather than the normal response, disclosing the auth secret and configured social-provider client secrets to a user who can sign in. With the auth secret, the user can create trusted signed values and obtain another known-email user’s session. Separately, when the Electron plugin precedes twoFactor(), password sign-in is enabled, and the account has two-factor enabled, a desktop sign-in code can be exchanged for a full session before second-factor completion. The advisory documents these separate paths under one GHSA; no CVE is assigned.

Product: @better-auth/electron. AI system: Anthropic OSS Scanner. Team / organization: Anthropic.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): Discovered by Anthropic’s OSS Scanner, ANT-2026-R8Z0P3MG. The advisory also lists ANT-2026-DDHILQ2X as a related anonymous-sign-in path, but does not establish it as an independent vulnerability.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The vulnerability is documented as a public disclosure; the source does not establish prior defender knowledge or exploitation.

Remediation status: fix documented. Upgrade @better-auth/electron and better-auth to 1.7.16 or 1.8.0-beta.5. If previously deployed, rotate auth and social-provider secrets.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 3 Nov 2026. AI attribution dated 3 Nov 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: data disclosure, authentication bypass.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

Case-level evidence: data disclosure.
Prerequisites / affected scope: Affected Electron plugin; a user who can sign in can cause the wrong endpoint context to be returned..
Exploitation evidence: No observed exploitation is reported.. Impact source · checked 16 Nov 2026.

Case-level evidence: authentication bypass.
Prerequisites / affected scope: Password sign-in enabled; user has two-factor; electron() is registered before twoFactor(); attacker knows the user password..
Exploitation evidence: No observed exploitation is reported.. Impact source · checked 16 Nov 2026.

Documented fix: Upgrade @better-auth/electron and better-auth to 1.7.16 or 1.8.0-beta.5. If previously deployed, rotate auth and social-provider secrets.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases