CVE-2026-54242

Statamic Vulnerable to Server-Side Request Forgery via Glide (DNS rebinding)

The Glide image proxy's URL validation could be bypassed using DNS rebinding. The remote hostname was validated as publicly routable, but resolved again when the image was actually fetched, so an attacker controlling the hostname's DNS could rebind it to an internal address after validation. This could cause the server to make HTTP requests to internal addresses, including loopback, private network, and cloud metadata endpoints.

This affects sites that pass user-supplied URLs to Glide.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-54242 has a CVSS score of 4.9 (Medium). The vector is network-reachable, low 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.73.24, 6.20.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This has been fixed in 5.73.24 and 6.20.1.

1. What is CVE-2026-54242? CVE-2026-54242 is a medium-severity server-side request forgery (SSRF) vulnerability in statamic/cms (composer), affecting versions < 5.73.24. It is fixed in 5.73.24, 6.20.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2026-54242? CVE-2026-54242 has a CVSS score of 4.9 (Medium). 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.
3. Which versions of statamic/cms are affected by CVE-2026-54242? statamic/cms (composer) versions < 5.73.24 is affected.
4. Is there a fix for CVE-2026-54242? Yes. CVE-2026-54242 is fixed in 5.73.24, 6.20.1. Upgrade to this version or later.
5. Is CVE-2026-54242 exploitable, and should I be worried? Whether CVE-2026-54242 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
6. What actually determines whether CVE-2026-54242 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.
7. How do I fix CVE-2026-54242?
   • Upgrade statamic/cms to 5.73.24 or later
   • Upgrade statamic/cms to 6.20.1 or later

Other vulnerabilities in statamic/cms