CVE-2026-67327
Auth library flaw enables account takeover via magic-link/email-OTP flows.
Is CVE-2026-67327 being exploited?
Not confirmed. CVE-2026-67327 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-67327?
CVE-2026-67327 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67327?
Yes. A fix has been recorded for CVE-2026-67327. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67327 affect?
CVE-2026-67327 affects better-auth >=1.1.3 and <1.6.22, better-auth >=1.7.0-beta.0 and <1.7.0-beta.10, Apps using better-auth with open email/password registration and magic-link/email-OTP. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67327?
Upgrade to better-auth 1.6.22 or >=1.7.0-beta.10; or disable open email/password registration until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Account takeover: attacker registers victim email with a password; victim's magic-link/OTP sign-in verifies account but attacker password and sessions remain, giving persistent access.
Immediate action required
- affected>= 1.1.3 and < 1.6.22
- affected>= 1.7.0-beta.0 and < 1.7.0-beta.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.