Quick answers
- Is CVE-2026-45660 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45660 being exploited in the wild.
- How severe is CVE-2026-45660?
- Medium severity, with a CVSS score of 5.4, published 29 May 2026.
- Which products and versions are affected?
- statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.73.22; Statamic < 5.73.22, < 6.18.1, < 5.73.22, >= 6.0.0-alpha.1, < 6.18.1.
- Is there a fix for CVE-2026-45660?
- Yes. statamic/cms (Packagist): upgrade to 5.73.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45660 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45660?
- 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.73.22 or later
composer require statamic/cms:^5.73.22
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Statamic's Glide image proxy due to insufficient normalization of IP addresses before performing public-IP validation. An unauthenticated attacker can bypass these checks by using alternative IP representations to force the server to make HTTP requests to internal addresses, including loopback (127.0.0.1), private network ranges, and cloud metadata endpoints. The vulnerability specifically affects sites that pass user-supplied URLs to Glide and are running on PHP versions older than 8.3. The issue is resolved in Statamic versions 5.73.22 and 6.18.1.
Affected products
- Statamic Statamic CMS < 5.73.22, < 6.18.1
Identifiers
- CVE-2026-45660
- GHSA-pf9c-ch8r-2958
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD