statamic/cms

CVE-2026-45660

CVE-2026-45660 is a medium-severity server-side request forgery (SSRF) vulnerability in statamic/cms (composer), affecting versions < 5.73.22. It is fixed in 5.73.22, 6.18.1.

Key facts
CVSS score
5.4
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
statamic/cms
Fixed in
5.73.22, 6.18.1
Disclosed
2026

Summary

Impact The Glide image proxy's URL validation could be bypassed using an IP representation that wasn't normalized before the public-IP check. An unauthenticated user 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. Sites running PHP 8.3 or newer are not affected. Patches This has been fixed in 5.73.22 and 6.18.1

Impact

What is server-side request forgery (SSRF)?

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.

Severity and exposure

CVE-2026-45660 has a CVSS score of 5.4 (Medium). 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.73.22, 6.18.1). Upgrading removes the vulnerable code path.

Affected versions

composer

  • statamic/cms (< 5.73.22)
  • statamic/cms (>= 6.0.0-alpha.1, < 6.18.1)

Security releases

  • statamic/cms → 5.73.22 (composer)
  • statamic/cms → 6.18.1 (composer)
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 instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-45660 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-45660 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-45660 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade statamic/cms to 5.73.22 or later
  • Upgrade statamic/cms to 6.18.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-45660

What is CVE-2026-45660?

CVE-2026-45660 is a medium-severity server-side request forgery (SSRF) vulnerability in statamic/cms (composer), affecting versions < 5.73.22. It is fixed in 5.73.22, 6.18.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2026-45660?

CVE-2026-45660 has a CVSS score of 5.4 (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.

Which versions of statamic/cms are affected by CVE-2026-45660?

statamic/cms (composer) versions < 5.73.22 is affected.

Is there a fix for CVE-2026-45660?

Yes. CVE-2026-45660 is fixed in 5.73.22, 6.18.1. Upgrade to this version or later.

Is CVE-2026-45660 exploitable, and should I be worried?

Whether CVE-2026-45660 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-45660 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-45660?
  • Upgrade statamic/cms to 5.73.22 or later
  • Upgrade statamic/cms to 6.18.1 or later

Stop the waste.
Protect your environment with Kodem.