Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Informational severity, published 5 November 2026.

Which products and versions are affected?

github.com/imgproxy/imgproxy (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v2 (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v3 (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v4 (Go) SEMVER:introduced=4.0.0,fixed=4.0.16; and 1 more.

Is there a fix for This vulnerability?

Yes. github.com/imgproxy/imgproxy/v4 (Go): upgrade to 4.0.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network.

Check whether you run github.com/imgproxy/imgproxy (Go), github.com/imgproxy/imgproxy/v2 (Go), github.com/imgproxy/imgproxy/v3 (Go) or one of the others listed 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.

imgproxy integer overflow in ICO loader

Severity: info · Published 2026-11-05

imgproxy is an image processing service that handles various image formats including ICO files. An integer overflow in the ICO loader allows an attacker to send a specially crafted image file that causes the service to crash or potentially execute arbitrary code due to heap memory corruption.

Technologies: github.com/imgproxy/imgproxy (Go), github.com/imgproxy/imgproxy/v2 (Go), github.com/imgproxy/imgproxy/v3 (Go), github.com/imgproxy/imgproxy/v4 (Go), Imgproxy. Vendors: Go, Imgproxy.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Informational severity, published 5 November 2026.
Which products and versions are affected?: github.com/imgproxy/imgproxy (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v2 (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v3 (Go) SEMVER:introduced=0; github.com/imgproxy/imgproxy/v4 (Go) SEMVER:introduced=4.0.0,fixed=4.0.16; and 1 more.
Is there a fix for This vulnerability?: Yes. github.com/imgproxy/imgproxy/v4 (Go): upgrade to 4.0.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network.
Am I affected?: Check whether you run github.com/imgproxy/imgproxy (Go), github.com/imgproxy/imgproxy/v2 (Go), github.com/imgproxy/imgproxy/v3 (Go) or one of the others listed 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/v4 (Go): upgrade to 4.0.16 or later
```
go get github.com/imgproxy/imgproxy/v4@v4.0.16
```

Technical details

An integer overflow in vips/icoload.c occurs when computing data_size + BMP_FILE_HEADER_LEN (14 bytes) for an attacker-controlled 32-bit data_size value. When data_size exceeds UINT32_MAX - 14, the addition wraps to a small value, causing VIPS_MALLOC to allocate insufficient heap memory. The subsequent write of ICO prefix and original-size data causes a heap buffer overflow. This is reachable over the network with no authentication or user interaction required.

Affected products

imgproxy imgproxy 4.0.0 to 4.0.15

Identifiers

GHSA-hff9-5pqw-6w9f
GO-2026-6897

Timeline

2026-10-06: disclosed
2026-11-05: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.