# CVE-2026-123614: imgproxy 4.0.0 before 4.0.16 Heap Buffer Overflow via ICO Loader Integer Overflow


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-hff9-5pqw-6w9f, GHSA-p65x-p3jr-w89f, GO-2026-6897

## What is CVE-2026-123614?

CVE-2026-123614 is a critical vulnerability in imgproxy, published on 8 Nov 2026. 

### Official description

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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-123614?

7 open source packages ship an affected version, including github.com/imgproxy/imgproxy, github.com/imgproxy/imgproxy/v2 and github.com/imgproxy/imgproxy/v3.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/imgproxy/imgproxy` | Go | All versions | None |
| `github.com/imgproxy/imgproxy` | Go | From 4.0.0 | 4.0.16 |
| `github.com/imgproxy/imgproxy/v2` | Go | All versions | None |
| `github.com/imgproxy/imgproxy/v2` | Go | From 4.0.0 | 4.0.16 |
| `github.com/imgproxy/imgproxy/v3` | Go | All versions | None |
| `github.com/imgproxy/imgproxy/v3` | Go | From 4.0.0 | 4.0.16 |
| `github.com/imgproxy/imgproxy/v4` | Go | From 4.0.0 | 4.0.16 |

## How do I fix CVE-2026-123614?

Upgrade github.com/imgproxy/imgproxy to 4.0.16 or later.

## Is CVE-2026-123614 being exploited?

There is no known exploitation of CVE-2026-123614 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123614 and fix it if it is affected.

What it is: CVE-2026-123614 is a critical vulnerability in imgproxy, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123614 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/imgproxy/imgproxy (Go): affected all versions; no fix listed
- github.com/imgproxy/imgproxy (Go): affected from 4.0.0; fixed in 4.0.16
- github.com/imgproxy/imgproxy/v2 (Go): affected all versions; no fix listed
- github.com/imgproxy/imgproxy/v2 (Go): affected from 4.0.0; fixed in 4.0.16
- github.com/imgproxy/imgproxy/v3 (Go): affected all versions; no fix listed
- github.com/imgproxy/imgproxy/v3 (Go): affected from 4.0.0; fixed in 4.0.16
- github.com/imgproxy/imgproxy/v4 (Go): affected from 4.0.0; fixed in 4.0.16

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123614/ (Markdown: https://insights.sbomify.com/CVE-2026-123614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123614
- OSV: https://osv.dev/vulnerability/CVE-2026-123614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123614/
Summaries are generated and may contain mistakes; the official description above is the record.