CVE-2026-123616: imgproxy · Excessive Memory Allocation
Affects imgproxySource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 4.0.16 soon.
Data as of 8 Nov 2026, 01:50 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
- Patch
- Available – fixed in 4.0.16
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade imgproxy to 4.0.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| imgproxyimgproxy | Affected
| Fixed in
|
AI-suggested
Upgrade imgproxy to version 4.0.16 or later, where this vulnerability is fixed. No additional mitigation is required as the fix is officially released.
Description
CVE-2026-123616 is a high-severity vulnerability in imgproxy versions 3.3.0 up to but not including 4.0.16. It involves an unbounded memory allocation flaw in the ICO image loader, where the data_size field is not validated. An attacker can supply a crafted ICO file with a large declared data_size (~4GB) to cause memory exhaustion and crash worker processes without requiring authentication. The issue is fixed in imgproxy version 4.0.16.