CVE-2026-123615 · Package
NO FIX YET · SEE WHAT TO DO
imgproxy 3.3.0 before 4.0.17 reads and writes past a heap buffer when its ICO loader rebuilds a BMP header from an entry with a tiny declared data size. An unauthenticated remote attacker can send a crafted ICO image to corrupt heap metadata and crash the worker process.
first public Oct 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running imgproxy 3.3.0 through 4.0.16 that process images from untrusted sources, such as public URLs or user uploads, are exposed because the crafted ICO image reaches the vulnerable loader unauthenticated. Deployments that only resize trusted internal images or do not accept ICO input are at lower risk. Whether ICO support can be turned off is unknown from the sources.
Not affected if ico-disabled, trusted-sources-only
Who cares docker, imgproxy, self-hosted
imgproxy version or the Docker image tagIMGPROXY_ALLOW_... and source URL settings) so untrusted ICO files reach the loader4.0.17 or later (the fix is in 4.0.17 per the description; 3.3.0 and earlier 3.x affected)imgproxy 3.3.0 before 4.0.17 contains an out-of-bounds heap read and write in the ICO loader's BMP header reconstruction (vips_foreign_load_ico_header in vips/icoload.c) when an ICO entry declares a tiny data size, causing unvalidated header fields to be read and written past the allocated buffer. Unauthenticated remote attackers can supply a crafted ICO image to corrupt adjacent heap chunk metadata, triggering a glibc abort that crashes the worker.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.