Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.3
imgproxy can crash or be hijacked by malicious ICO image
published 14 days ago
Summary
Versions of imgproxy from 4.0.0 up to 4.0.15 can be tricked by a specially crafted ICO picture. The picture tricks the program into allocating the wrong amount of memory, which can cause the service to stop working or let an attacker run their own code. Update imgproxy to version 4.0.16 or later to fix the problem.
What to do
- Update imgproxy github.com/imgproxy/imgproxy/v3 to version 4.0.16.
- Update imgproxy github.com/imgproxy/imgproxy/v2 to version 4.0.16.
- Update imgproxy github.com/imgproxy/imgproxy to version 4.0.16.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Go | imgproxy | github.com/imgproxy/imgproxy/v3 |
>= 4.0.0, < 4.0.16 Fix: upgrade to 4.0.16
|
| Go | imgproxy | github.com/imgproxy/imgproxy/v2 |
>= 4.0.0, < 4.0.16 Fix: upgrade to 4.0.16
|
| Go | imgproxy | github.com/imgproxy/imgproxy |
>= 4.0.0, < 4.0.16 Fix: upgrade to 4.0.16
|
Original advisory text
imgproxy 4.0.0 before 4.0.16 Heap Buffer Overflow via ICO Loader Integer Overflow
imgproxy from 4.0.0 before 4.0.16 contains an integer overflow in the ICO loader that allows remote attackers to trigger a heap buffer overflow via a crafted data_size value. Attackers can submit a crafted ICO image whose data_size wraps the allocation in vips/icoload.c, corrupting heap memory to crash the process or achieve code execution.
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker full control (estimated)
Severity
9.3
Critical
Type
CWE-122Heap-based Buffer Overflow
CWE-190Integer Overflow
Timeline
Published8 Nov 2026
Updated8 Nov 2026
First seen30 Oct 2026
Sources
GHSA-hff9-5pqw-6w9f · OSV
Track software like this
Free during beta