better-auth before 1.4.9 Two-Factor Authentication Bypass via session.cookieCache
cve-program · CVE-2026-67337
Publishedbetter-auth versions before 1.4.9 contain a two-factor authentication bypass vulnerability when session.cookieCache is enabled. Attackers with valid primary credentials can access authenticated routes without completing second-factor verification by exploiting premature session caching.
Read the publisher's advisoryeuvd · EUVD-2026-51837
Publishedbetter-auth versions before 1.4.9 contain a two-factor authentication bypass vulnerability when session.cookieCache is enabled. Attackers with valid primary credentials can access authenticated routes without completing second-factor verification by exploiting premature session caching.
Read the publisher's advisorynvd · CVE-2026-67337
Publishedbetter-auth versions before 1.4.9 contain a two-factor authentication bypass vulnerability when session.cookieCache is enabled. Attackers with valid primary credentials can access authenticated routes without completing second-factor verification by exploiting premature session caching.
Read the publisher's advisoryosv · GHSA-xg6x-h9c9-2m83
Published### Summary Under certain configurations, sessions may be considered valid before two-factor authentication (2FA) is fully completed. This can allow access to authenticated routes without verifying the second factor. --- ### Description When two-factor authentication is enabled, the authentication flow correctly identifies users who require additional verification and defers full authentication until the second factor is completed. However, when `session.cookieCache` is enabled, the session generated during the initial sign-in step may be cached as valid **prior to 2FA verification**. Subsequent session lookups may then return this cached session without re-evaluating the 2FA requirement. This results in a situation where session validity can be established before all authentication constraints are satisfied. --- ### Impact An attacker (or user) with valid primary credentials may gain access to protected application routes without completing the required second authentication factor. Any application using `better-auth` with both two-factor authentication and session cookie caching enabled may be affected. --- ### Mitigation * Upgrade to a version of `better-auth` that includes the fix for this issue. * Ensure that session caching does not treat sessions as fully authenticated until all required authentication steps, including 2FA, are completed. * As a temporary workaround, disable `session.cookieCache` when using two-factor authentication.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-67337 · CVE overview and exploitation status
cve-program · CVE-2026-67337
- https://github.com/better-auth/better-auth/security/advisories/GHSA-xg6x-h9c9-2m83
- https://www.vulncheck.com/advisories/better-auth-before-two-factor-authentication-bypass-via-session-cookiecache
euvd · EUVD-2026-51837
- https://github.com/better-auth/better-auth/security/advisories/GHSA-xg6x-h9c9-2m83
- https://www.vulncheck.com/advisories/better-auth-before-two-factor-authentication-bypass-via-session-cookiecache
nvd · CVE-2026-67337
- https://github.com/better-auth/better-auth/security/advisories/GHSA-xg6x-h9c9-2m83
- https://www.vulncheck.com/advisories/better-auth-before-two-factor-authentication-bypass-via-session-cookiecache
osv · GHSA-xg6x-h9c9-2m83
Related changes
Linked by CVE identifierNo related changes are available here.