Is CVE-2026-64663 exploited in the wild?

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

How severe is CVE-2026-64663?

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

Which products and versions are affected?

statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.74.1.

Is there a fix for CVE-2026-64663?

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-64663 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-64663?

Check whether you run statamic/cms (Packagist) 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-64663: Statamic CMS unsafe reflection in Antlers template resolution

CVE-2026-64663 · Severity: medium · CVSS 6.5 · Published 2026-08-06

Statamic, a content management system, is vulnerable to a flaw that could allow an attacker to delete website content and assets. This occurs when user-provided data is improperly handled by the system's template engine. If a site uses templates that process untrusted input in specific ways, an unauthenticated attacker could trigger the destruction of data, potentially leading to service disruption and loss of digital assets.

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

Quick answers

Is CVE-2026-64663 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64663 being exploited in the wild.
How severe is CVE-2026-64663?: Medium severity, with a CVSS score of 6.5, published 6 August 2026.
Which products and versions are affected?: statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.74.1.
Is there a fix for CVE-2026-64663?: 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-64663 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-64663?: Check whether you run statamic/cms (Packagist) 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

Statamic CMS is vulnerable to unsafe reflection (CWE-470) within its Antlers template engine. The vulnerability arises when user-supplied input is incorporated into Antlers templates and subsequently used to select or invoke classes or code without sufficient validation. An unauthenticated remote attacker can exploit this by providing malicious input to templates that pass untrusted data into affected areas, leading to unauthorized method invocation and data destruction. The attack complexity is rated as high, likely due to the requirement for specific template configurations to be present. The issue has been patched 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-64663
GHSA-j2vp-f2pv-5rj4

Timeline

2026-07-02: disclosed: Advisory published by researcher
2026-08-06: advisory: GitHub Advisory published/reviewed
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.