# CVE-2026-54242: Statamic: Server-Side Request Forgery via Glide (DNS rebinding)

> Attackers can bypass URL validation via DNS rebinding to force the server to make requests to internal network addresses, potentially exposing sensitive data.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-v5c4-wcpj-x73m

## What is CVE-2026-54242?

CVE-2026-54242 is a medium-severity server-side request forgery vulnerability in statamic cms, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.24 and 6.20.1, the Glide image proxy's URL validation in src/Imaging/RemoteUrlValidator.php and src/Imaging/GuzzleAdapter.php 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 and 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. This issue is fixed in versions 5.73.24 and 6.20.1.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-54242?

4 open source packages ship an affected version, including statamic/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 5.73.24 |
| `statamic/cms` | Packagist | All versions | 5.73.24 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.20.1 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.20.1 |

## How do I fix CVE-2026-54242?

Upgrade statamic/cms to a fixed version for your release line: 5.73.24 or 6.20.1.

## Is CVE-2026-54242 being exploited?

There is no known exploitation of CVE-2026-54242 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54242 and fix it if it is affected.

What it is: CVE-2026-54242 is a medium-severity server-side request forgery vulnerability in statamic cms, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54242 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 5.73.24
- statamic/cms (Packagist): affected all versions; fixed in 5.73.24
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.20.1
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.20.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54242/ (Markdown: https://insights.sbomify.com/CVE-2026-54242/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54242
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54242
- OSV: https://osv.dev/vulnerability/CVE-2026-54242

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54242/
Summaries are generated and may contain mistakes; the official description above is the record.