Statamic Vulnerable to Server-Side Request Forgery via Glide (DNS rebinding)
Published 26 Jun 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- <5.73.24
- Fixed in
- 5.73.24
composer require statamic/cms:^5.73.24- Affected
- >=6.0.0 <6.20.1
- Fixed in
- 6.20.1
composer require statamic/cms:^6.20.1Details
Impact
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.
Patches
This has been fixed in 5.73.24 and 6.20.1.
Is GHSA-v5c4-wcpj-x73m in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected statamic/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.