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.
- Exploited
- No known exploitation
- Fix
- Fixed in @better-auth/passkey 1.7.16, 1.8.0-beta.5 · better-auth 1.4.0
- Who is exposed
- Specific setups only
Summary
Written by a model
@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.
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.
“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”
What to do
Check whether your setup matches what the bug needs.
Uses @better-auth/passkey 1.4.0-beta.16 or later, or the passkey plugin built into better-auth before 1.4.0 authenticatorSelection.userVerification is set to "required" Relying party ID also covers origins the app does not control, such as other subdomainsUpgrade to a fixed version: @better-auth/passkey 1.7.16, 1.8.0-beta.5 · better-auth 1.4.0.
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-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"}.Affected versions
- @better-auth/passkeyFrom 1.4.0-beta.16 · fixed in 1.7.16Fixed in 1.7.16 (released Nov 3, 2026, 18 days before disclosure).
- @better-auth/passkeyFrom 1.8.0-beta.0 · fixed in 1.8.0-beta.5Fixed in 1.8.0-beta.5 (released Nov 3, 2026, 18 days before disclosure).The latest release, 1.7.25, is not affected.
- better-authFrom 1.2.0-beta.18 · fixed in 1.4.0Fixed in 1.4.0 (released Nov 22, 2025, 364 days before disclosure).The latest release, 1.7.26, is not affected.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach20/20better-auth: 19.7M downloads a week
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
Impact
- Widely used@better-auth/passkey has 3.6m weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · better-auth/better-auth · Advisory GHSA-gv75-j3v8-3crm |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134320 |
| Record | NVD · CVE-2026-134320 |
| Other links 1 | |
| Link | vulncheck.com · advisories/better-auth-passkey-before-1.7.16-improper-origin-and-user-verification-enforcement |
Questions about CVE-2026-134320
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: cve.now feed data
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: github.com
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: cve.now feed data
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: github.com
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: github.com
Related
- CVE-2026-67336better-auth before 1.6.11 Insecure Cryptographic Defaults via oidcProvider
- CVE-2026-110862Better Auth 1.4.0-beta.18 before 1.7.7 Authentication Bypass via Magic Link
- CVE-2025-71401better-auth before 1.4.2 basePath Modification DoS
- CVE-2026-114607better-auth: OAuth state can be used as a Magic Link to sign in as another user
- CVE-2026-110864Better Auth 1.5.0-beta.12 before 1.7.7 Authentication Bypass via OAuth Proxy
- CVE-2025-71399Better Auth before 1.4.5 Path Normalization Bypass via rou3
No corrections so far. Something wrong on this page? Report an error.