CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVE-2026-123615 imgproxy before 4.0.17 Out-of-Bounds Write in ICO Loader
High (8.7) in imgproxy imgproxy. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/imgproxy/imgproxy/v3 4.0.17.
On this page
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.
Severity
CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-13. 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-787 Out-of-bounds Write
- Published
- Modified
- Assigned by
- VulnCheck (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123615 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123615?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123615?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-123615 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-123615)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123615"><img src="https://cve.bz/cve/badge/CVE-2026-123615.svg" alt="CVE-2026-123615"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| imgproxy | from 3.3.0 before 4.0.17 |
Fix and patched versions
github.com/imgproxy/imgproxy/v3(Go): fixed in 4.0.17github.com/imgproxy/imgproxy/v4(Go): fixed in 4.0.17
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-494m-4556-wf5p | Go | github.com/imgproxy/imgproxy/v3 | >=3.3.0 <4.0.17 | 4.0.17 |
| GO-2026-6895 | Go | github.com/imgproxy/imgproxy | all versions | no fix published |
| GO-2026-6895 | Go | github.com/imgproxy/imgproxy/v2 | all versions | no fix published |
| GO-2026-6895 | Go | github.com/imgproxy/imgproxy/v3 | >=3.3.0 | no fix published |
| GO-2026-6895 | Go | github.com/imgproxy/imgproxy/v4 | <4.0.17 | 4.0.17 |