# CVE-2025-24354: GO-2025-3422 - imgproxy is vulnerable to SSRF against 0.0.0.0 in github.com/imgproxy/imgproxy

Source: https://junglewise.ai/threats/cve-2025-24354-imgproxy-is-vulnerable-to-ssrf-against-0-0-0-0  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-01-28  
License: CC BY 4.0 with a link back

CVE-2025-24354 · Severity: low · CVSS 3.1 · Published 2025-01-28

imgproxy is vulnerable to SSRF against 0.0.0.0 in github.com/imgproxy/imgproxy

Technologies: [github.com/imgproxy/imgproxy (Go)](https://junglewise.ai/threats/technologies/github-com-imgproxy-imgproxy), [github.com/imgproxy/imgproxy/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-imgproxy-imgproxy-v2), [github.com/imgproxy/imgproxy/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-imgproxy-imgproxy-v3). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-24354 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-24354 being exploited in the wild.

**How severe is CVE-2025-24354?** Low severity, with a CVSS score of 3.1, published 28 January 2025.

**Which products and versions are affected?** github.com/imgproxy/imgproxy (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=3.27.2; github.com/imgproxy/imgproxy/v2 (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v3 (Go) SEMVER:introduced=0,fixed=3.27.2.

**Is there a fix for CVE-2025-24354?** Yes. github.com/imgproxy/imgproxy (Go): upgrade to 3.27.2 or later; github.com/imgproxy/imgproxy/v3 (Go): upgrade to 3.27.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-24354?** Check whether you run github.com/imgproxy/imgproxy (Go), github.com/imgproxy/imgproxy/v2 (Go) or github.com/imgproxy/imgproxy/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/imgproxy/imgproxy (Go): upgrade to 3.27.2 or later

  ```sh
  go get github.com/imgproxy/imgproxy@v3.27.2
  ```

- github.com/imgproxy/imgproxy/v3 (Go): upgrade to 3.27.2 or later

  ```sh
  go get github.com/imgproxy/imgproxy/v3@v3.27.2
  ```


## Affected products

- github.com/imgproxy/imgproxy (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=3.27.2
- github.com/imgproxy/imgproxy/v2 (Go) SEMVER:introduced=0
- github.com/imgproxy/imgproxy/v3 (Go) SEMVER:introduced=0,fixed=3.27.2

## Identifiers

- CVE-2025-24354
- GHSA-j2hp-6m75-v4j4
- GO-2025-3422

## Related threats

- [imgproxy unbounded memory allocation in ICO loader](https://junglewise.ai/threats/go-2026-6898-imgproxy-has-unbounded-memory-allocation-in-ico-loader-a99ea6ff)
- [imgproxy out-of-bounds heap read/write in ICO loader BMP header](https://junglewise.ai/threats/go-2026-6895-imgproxy-has-out-of-bounds-heap-read-write-in-ico-loader-d8e85817)
- [imgproxy integer overflow in ICO loader](https://junglewise.ai/threats/go-2026-6897-imgproxy-has-integer-overflow-in-imgproxy-ico-loader-that-dbf52154)
- [imgproxy integer overflow in ICO loader](https://junglewise.ai/threats/imgproxy-has-integer-overflow-in-imgproxy-ico-loader-that-causes-denial-19f131eb)
- [imgproxy out-of-bounds write in ICO loader BMP header](https://junglewise.ai/threats/imgproxy-has-out-of-bounds-heap-read-write-in-ico-loader-bmp-header-c4e077cd)