Skip to main content
Menu
CVEs

@better-auth/electron before 1.7.16 Auth Secret Disclosure and Two-Factor Bypass

Affects @better-auth/electron from 1.5.0-beta.12 up to 1.7.16 and from 1.8.0-beta.0 up to 1.8.0-beta.5 when the server registers the electron() plugin. Fixed in 1.7.16 and 1.8.0-beta.5.

CVE-2026-134316Published November 21, 2026, updated

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.7.16, 1.8.0-beta.5
Who is exposed
Specific setups only

Summary

Written by a model

@better-auth/electron 1.5.0-beta.12 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 accepts any validly signed value as its transfer cookie and returns the full endpoint context, including the auth secret and social provider client secrets, in sign-in responses. Authenticated users can obtain these secrets to forge sessions as other users. Attackers knowing a password can exchange desktop authorization codes issued before two-factor verification to bypass the second factor.

Who should check

Teams whose server registers the electron() plugin from @better-auth/electron 1.5.0-beta.12 or later, before 1.7.16 or 1.8.0-beta.5, including those using twoFactor() with password sign-in.

Not fixed by: Placing twoFactor() before electron() does not fix the server secret problem.

“You are affected if your server registers the electron() plugin from @better-auth/electron 1.5.0-beta.12 or later.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Server registers the electron() plugin from @better-auth/electron 1.5.0-beta.12 or later. Server registers twoFactor() (for the two-factor bypass). electron() appears before twoFactor() in the plugins array (for the two-factor bypass). Users with two-factor turned on can sign in with a password (for the two-factor bypass).
  2. Upgrade to a fixed version: 1.7.16, 1.8.0-beta.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134316 (@better-auth/electron before 1.7.16 Auth Secret Disclosure and Two-Factor Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134316 (entry last updated 2026-11-21):
Affected:
- npm package @better-auth/electron: from 1.5.0-beta.12, fixed in 1.7.16
- npm package @better-auth/electron: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
Fixed versions: 1.7.16, 1.8.0-beta.5.
Conditions (all must be true for the bug to be hit):
- Server registers the electron() plugin from @better-auth/electron 1.5.0-beta.12 or later. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc)
- Server registers twoFactor() (for the two-factor bypass). (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc)
- electron() appears before twoFactor() in the plugins array (for the two-factor bypass). (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc)
- Users with two-factor turned on can sign in with a password (for the two-factor bypass). (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134316 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134316 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc
- https://www.vulncheck.com/advisories/better-auth-electron-before-1.7.16-auth-secret-disclosure-and-two-factor-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134316
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134316"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects npm packages
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · better-auth/better-auth · Advisory GHSA-9p5w-h4pr-fcrc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134316
RecordNVD · CVE-2026-134316
Other links 1
Linkvulncheck.com · advisories/better-auth-electron-before-1.7.16-auth-secret-disclosure-and-two-factor-bypass

Questions about CVE-2026-134316

Is CVE-2026-134316 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Any signed-in user can read the auth secret and the social provider client secrets, then use them to forge sessions as other users. A user with a password can also get a session for an account without the second factor.

Source: github.com

Which versions are affected by CVE-2026-134316?

@better-auth/electron (npm): from 1.5.0-beta.12 before 1.7.16. @better-auth/electron (npm): from 1.8.0-beta.0 before 1.8.0-beta.5.

Source: cve.now feed data

Am I affected, and how do I check?

Servers that register the electron() plugin from @better-auth/electron 1.5.0-beta.12 through versions before 1.7.16, or 1.8.0-beta.0 through versions before 1.8.0-beta.5. The two-factor bypass also needs twoFactor() registered, with electron() placed before twoFactor() in the plugins array. Check the installed @better-auth/electron version in the package manifest or lockfile, and check the order of the plugins array in the server config.

Source: github.com

How do I fix CVE-2026-134316?

Upgrade @better-auth/electron to 1.7.16 or 1.8.0-beta.5, or a later version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.