ICO loader · V3: imgproxy has unbounded memory allocation
Affects github.com/imgproxy/imgproxy/v3Source GCVE Database
CVSS 7.5 High : upgrade to 4.0.16 soon.
Data as of 31 Oct 2026, 02:07 UTC
- Patch
- Available – fixed in 4.0.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWhat to do
Upgrade github.com/imgproxy/imgproxy/v3 to 4.0.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/imgproxy/imgproxy/v3 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch fixing this vulnerability is available in imgproxy version 4.0.16. Users should upgrade to version 4.0.16 or later to remediate this issue. Until upgraded, restricting or validating ICO image inputs may reduce exposure. No other vendor mitigation or workaround is documented.
Description
A vulnerability in imgproxy's ICO image loader allows unauthenticated attackers to trigger unbounded memory allocation by crafting a specially formed ICO file. The flaw exists because the ICO loader reads a data size field from the file without validation and uses it directly to allocate memory, potentially causing a ~4GB allocation from a small 23-byte file. This can lead to denial of service via memory exhaustion on affected imgproxy versions prior to 4.0.16.
References
- github.com/imgproxy/imgproxy/security/advisories/GHSA-mmq5-xm89-9pfg (opens in a new tab)
- github.com/imgproxy/imgproxy/commit/a821b6a4cb07a1bf2bb9077431d1c1e734d79917 (opens in a new tab)
- github.com/imgproxy/imgproxy (opens in a new tab)
- github.com/imgproxy/imgproxy/releases/tag/v4.0.16 (opens in a new tab)