Skip to main content
CVE-2026-134320VulnerabilityPublished

@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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134320· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 1.7.16 when convenient.

Data as of 21 Nov 2026, 19:58 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.02.3
CNA (VulnCheck)CVSS 3.13.1
Patch
Available – fixed in 1.7.16, 1.8.0-beta.5, 1.4.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
better-authpasskeyAffected
  • >=1.4.0-beta.16 <1.7.16
Fixed in
  • 1.7.16
better-authpasskeyAffected
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.8.0-beta.5
better-authpasskeyAffected
  • >=1.2.0-beta.18 <1.4.0
Fixed in
  • 1.4.0
npmpasskeypkg:npm/passkeyOther threatsAffected
  • >=1.4.0-beta.16 <1.7.16
  • >=1.8.0-beta.0 <1.8.0-beta.5
  • >=1.2.0-beta.18 <1.4.0
Fixed in
  • 1.7.16
  • 1.8.0-beta.5
  • 1.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should be cautious when deploying affected versions and consider additional authentication controls or monitoring to mitigate risk.

Description

@better-auth/passkey versions 1.4.0-beta.16 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, along with the passkey plugin in better-auth versions 1.2.0-beta.18 before 1.4.0, do not properly enforce WebAuthn user verification when it is set to "required". They also incorrectly take the expected origin from the request rather than from a secure configuration. This flaw allows users to register or authenticate using passkeys without the necessary PIN or biometric verification, and passkey responses from another origin under the same relying party ID may be accepted.

References

Community reviews

Loading reviews…