@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
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
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 2.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.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:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| better-authpasskey | Affected
| Fixed in
|
| better-authpasskey | Affected
| Fixed in
|
| better-authpasskey | Affected
| Fixed in
|
npmpasskeypkg:npm/passkeyOther threats | Affected
| Fixed in
|
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.