CVSS 4.0
9.3 criticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVE-2026-123614 imgproxy imgproxy: Heap-based Buffer Overflow
Critical (9.3) in imgproxy imgproxy. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/imgproxy/imgproxy/v3 4.0.16.
On this page
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.
Severity
CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- EPSS
- 0.7% estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-122 Heap-based Buffer Overflow
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123614 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123614?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123614?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123614 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123614)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123614"><img src="https://cve.bz/cve/badge/CVE-2026-123614.svg" alt="CVE-2026-123614"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| imgproxy | from 4.0.0 before 4.0.16 |
Fix and patched versions
github.com/imgproxy/imgproxy/v3(Go): fixed in 4.0.16github.com/imgproxy/imgproxy/v2(Go): fixed in 4.0.16github.com/imgproxy/imgproxy(Go): fixed in 4.0.16github.com/imgproxy/imgproxy/v4(Go): fixed in 4.0.16
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-hff9-5pqw-6w9f | Go | github.com/imgproxy/imgproxy/v3 | >=4.0.0 <4.0.16 | 4.0.16 |
| GHSA-hff9-5pqw-6w9f | Go | github.com/imgproxy/imgproxy/v2 | >=4.0.0 <4.0.16 | 4.0.16 |
| GHSA-hff9-5pqw-6w9f | Go | github.com/imgproxy/imgproxy | >=4.0.0 <4.0.16 | 4.0.16 |
| GO-2026-6897 | Go | github.com/imgproxy/imgproxy | all versions | no fix published |
| GO-2026-6897 | Go | github.com/imgproxy/imgproxy/v2 | all versions | no fix published |
| GO-2026-6897 | Go | github.com/imgproxy/imgproxy/v3 | all versions | no fix published |
| GO-2026-6897 | Go | github.com/imgproxy/imgproxy/v4 | >=4.0.0 <4.0.16 | 4.0.16 |
Attack patterns (CAPEC)
- CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.