Is CVE-2026-64664 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-64664 being exploited in the wild.

How severe is CVE-2026-64664?

Medium severity, with a CVSS score of 4.3, published 6 August 2026.

Which products and versions are affected?

statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.74.1; Statamic = 6.0.0, < 6.24.0.

Is there a fix for CVE-2026-64664?

Yes. statamic/cms (Packagist): upgrade to 5.74.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-64664 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-64664?

Check whether you run statamic/cms (Packagist) or Statamic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64664: Statamic CMS missing authorization in Control Panel user wizard

Q: Is there a fix for CVE-2026-64664?

Yes. statamic/cms (Packagist): upgrade to 5.74.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-64664 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-64664?

Check whether you run statamic/cms (Packagist) or Statamic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64664 · Severity: medium · CVSS 4.3 · Published 2026-08-06

Statamic is a content management system used to build and manage websites. A security flaw in its administrative Control Panel allows a logged-in user to verify if specific email addresses are registered as users on the system, even if they do not have permission to view the user list. While this does not expose passwords or personal content, it could be used by an attacker to identify valid accounts for further targeted attacks.

Technologies: statamic/cms (Packagist), Statamic. Vendors: Packagist, Statamic.

Quick answers

Is CVE-2026-64664 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64664 being exploited in the wild.
How severe is CVE-2026-64664?: Medium severity, with a CVSS score of 4.3, published 6 August 2026.
Which products and versions are affected?: statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.74.1; Statamic < 5.74.1, >= 6.0.0, < 6.24.0.
Is there a fix for CVE-2026-64664?: Yes. statamic/cms (Packagist): upgrade to 5.74.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64664 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-64664?: Check whether you run statamic/cms (Packagist) or Statamic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

statamic/cms (Packagist): upgrade to 5.74.1 or later
```
composer require statamic/cms:^5.74.1
```

Technical details

A missing authorization check (CWE-862) exists in a Statamic Control Panel endpoint intended for the user creation wizard. An authenticated attacker with low privileges (access to the Control Panel but without 'view users' permissions) can query this endpoint to determine if a specific email address is associated with an existing account. This results in the exposure of sensitive information (CWE-200) regarding user existence. The vulnerability is reachable over the network and requires no user interaction. Patches are available in versions 5.74.1 and 6.24.0.

Affected products

Statamic Statamic CMS < 5.74.1, >= 6.0.0, < 6.24.0

Identifiers

CVE-2026-64664
GHSA-225x-3jhx-wh4q

Timeline

2026-07-02: disclosed: Initial disclosure to vendor
2026-08-06: advisory: GitHub Advisory published
2026-08-06: patched: Fixes released in versions 5.74.1 and 6.24.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.