CVE-2026-67328
SSO library auth bypass allowing account takeover via SAML, domain parsing, or logout XSS.
Is CVE-2026-67328 being exploited?
Not confirmed. CVE-2026-67328 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.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-67328?
CVE-2026-67328 is rated High with a CVSS score of 8.6. 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-67328?
Yes. A fix has been recorded for CVE-2026-67328. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67328 affect?
CVE-2026-67328 affects @better-auth/sso < 1.6.21, Web applications using @better-auth/sso, SSO integrations (SAML/OAuth providers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67328?
Upgrade to @better-auth/sso v1.6.21+, invalidate sessions and review SSO configs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can sign in as arbitrary users and take over accounts via SSO provider parsing mismatches, unbound SAML assertions, orphaned provider accounts, or reflected XSS.
Immediate action required
- affected< 1.6.21
- 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.