CVE-2025-24354 is a medium-severity (CVSS 5.3) Server-Side Request Forgery (SSRF) vulnerability in github.com/imgproxy/imgproxy. A fix is available for github.com/imgproxy/imgproxy — see the affected versions and patch details below.
imgproxy is vulnerable to SSRF against 0.0.0.0
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-24354.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/imgproxy/imgproxyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Imgproxy does not block the 0.0.0.0 address, even with IMGPROXY_ALLOW_LOOPBACK_SOURCE_ADDRESSES set to false. This can expose services on the local host.
Details
imgproxy protects against SSRF against a loopback address with the following check (source):
if !config.AllowLoopbackSourceAddresses && ip.IsLoopback() {
return ErrSourceAddressNotAllowed
}
This check is insufficient to prevent accessing services on the local host, as services may receive traffic on 0.0.0.0. Go's IsLoopback (source) strictly follows the definition of loopback IPs beginning with 127. 0.0.0.0 is not blocked.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/imgproxy/imgproxy | all versions | 3.27.2go get github.com/imgproxy/imgproxy@v3.27.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/imgproxy/imgproxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/imgproxy/imgproxy to 3.27.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24354 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
How to detect CVE-2025-24354
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-24354 -u https://target- Template
- Imgproxy < 3.27.2 - Server-Side Request Forgery (SSRF)
- Severity
- medium
- Impact
- Local services may be exposed to unauthorized access, risking information disclosure or local system compromise.
- Remediation
- The vulnerability has been fixed in imgproxy version 3.27.2. The fix involves updating the source address verification to also check for unspecified IP addresses (0.0.0.0) using the ip.IsUnspecified() function in addition to the existing ip.IsLoopback() check.
Template by ProjectDiscovery nuclei-templates (oksuzkayra), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-24354 in your dependencies?
Find it across Go, including transitive dependencies.