CVE-2026-134320
Received Received - Intake

Authentication Bypass in Better Auth Passkey Plugin

Vulnerability report for CVE-2026-134320, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
better-auth passkey to 1.7.16 (exc)
better-auth passkey From 1.2.0-beta.18 (inc) to 1.4.0 (exc)
better-auth passkey to 1.8.0-beta.5 (exc)
better-auth passkey to 1.7.16|end_excluding=1.8.0-beta.5 (exc)
better-auth better-auth to 1.7.16|end_excluding=1.8.0-beta.5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-134320 affects the @better-auth/passkey package and better-auth passkey plugin versions before 1.7.16 and 1.8.0-beta.5. When userVerification is set to required, the server fails to confirm user verification like PIN or biometric checks. It also incorrectly uses the request's origin instead of the configured origin for validation, allowing passkey responses from untrusted origins under the same relying party ID to be accepted.

Detection Guidance

To detect this vulnerability, check the version of @better-auth/passkey or better-auth installed in your system. If you are using versions before 1.7.16 or 1.8.0-beta.5 for @better-auth/passkey, or before 1.4.0 for better-auth, your system is vulnerable. Run commands like 'npm list @better-auth/passkey' or 'npm list better-auth' to verify installed versions.

Impact Analysis

This vulnerability undermines security by allowing passkey authentication without required user verification. Attackers could misuse passkeys registered on untrusted origins if they share the same relying party ID. However, it does not permit unauthorized account registration or bypassing sign-in directly.

Compliance Impact

This vulnerability undermines compliance with standards requiring strong authentication like GDPR and HIPAA by failing to enforce user verification during passkey authentication. When userVerification is set to required, the system should confirm PIN or biometric checks, but this flaw allows bypassing that requirement. Additionally, accepting passkey responses from untrusted origins under the same relying party ID violates origin validation principles, potentially exposing sensitive data to unauthorized access.

Mitigation Strategies

Upgrade the @better-auth/passkey package to version 1.7.16 or later and the better-auth passkey plugin to version 1.4.0 or later. Verify that userVerification is properly enforced and configured origins are used for validation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134320. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...