Skip to content
Fencer Intel
medium 5.3

CVE-2025-24354 json

imgproxy is vulnerable to SSRF against 0.0.0.0

published last yr. modified 4mo ago also EUVD-2025-0172 , GHSA-j2hp-6m75-v4j4 , GO-2025-3422

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known, plus a Nuclei check

Summary

imgproxy is server for resizing, processing, and converting images. 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. This vulnerability is fixed in 3.27.2.

Patch / fix

  • go github.com/imgproxy/imgproxy 3.27.2
  • go github.com/imgproxy/imgproxy/v3 3.27.2
  • evilmartians imgproxy 3.27.2
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250128T150132-150000.1.29.1

suse advisories SUSE-SU-2025:0297-1

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250128T150132-1.1

opensuse advisories openSUSE-SU-2025:14710-1

Is CVE-2025-24354 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Imgproxy < 3.27.2 - Server-Side Request Forgery (SSRF) nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/imgproxy/imgproxy
<3.27.2
all versions
3.27.2
go github.com/imgproxy/imgproxy/v2
all versions
 no fix listed
go github.com/imgproxy/imgproxy/v3
<3.27.2
3.27.2

Affected products

  • imgproxy imgproxy

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.