Summary
Statamic: Account takeover via OAuth email matching without email-verification check
Workarounds
Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login.
Impact
When OAuth login is enabled with a provider that does not guarantee verified email addresses, an unauthenticated attacker could sign in as an existing user, potentially including a super admin, without their password. Exploitation requires OAuth to be explicitly enabled with such a provider.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2026-64665 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.74.1, 6.24.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed in 5.74.1 and 6.24.0.
Frequently Asked Questions
- What is CVE-2026-64665? CVE-2026-64665 is a high-severity improper authentication vulnerability in statamic/cms (composer), affecting versions < 5.74.1. It is fixed in 5.74.1, 6.24.0. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2026-64665? CVE-2026-64665 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of statamic/cms are affected by CVE-2026-64665? statamic/cms (composer) versions < 5.74.1 is affected.
- Is there a fix for CVE-2026-64665? Yes. CVE-2026-64665 is fixed in 5.74.1, 6.24.0. Upgrade to this version or later.
- Is CVE-2026-64665 exploitable, and should I be worried? Whether CVE-2026-64665 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-64665 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-64665?
- Upgrade
statamic/cmsto 5.74.1 or later - Upgrade
statamic/cmsto 6.24.0 or later
- Upgrade