Answer in brief
CVE-2026-134320 records a Low severity (CVSS 2.3) vulnerability in @better-auth/passkey before 1.7.16 Improper Origin and User Verification Enforcement. The current sources do not mark it as known exploited. The current feed maps better-auth/passkey (generic), better-auth/passkey (generic), better-auth/passkey (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps better-auth/passkey (generic), better-auth/passkey (generic), better-auth/passkey (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| better-auth/passkeygeneric | >=1.4.0-beta.16 <1.7.16 | 1.7.16 |
| better-auth/passkeygeneric | >=1.8.0-beta.0 <1.8.0-beta.5 | 1.8.0-beta.5 |
| better-auth/passkeygeneric | >=1.2.0-beta.18 <1.4.0 | 1.4.0 |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
@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.
Quoted source text, attributed separately from HOL analysis.