# CVE-2026-123616: imgproxy 3.3.0 before 4.0.16 Memory Exhaustion DoS via ICO Loader


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-97wv-7mx5-f6w4, GHSA-mmq5-xm89-9pfg, GO-2026-6898

## What is CVE-2026-123616?

CVE-2026-123616 is a high-severity vulnerability in imgproxy, published on 8 Nov 2026. 

### Official description

imgproxy from 3.3.0 before 4.0.16 contains an unbounded memory allocation vulnerability in the ICO loader that fails to validate the data_size field. Attackers can supply a crafted 23-byte ICO file declaring a ~4GB data_size to trigger memory exhaustion and worker crashes without authentication.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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

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


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

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

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

## Is CVE-2026-123616 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123616 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123616 is a high-severity vulnerability in imgproxy, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123616 exists.

Affected packages and fixed versions:
- github.com/imgproxy/imgproxy/v3 (Go): affected from 3.3.0; no fix listed
- github.com/imgproxy/imgproxy/v3 (Go): affected from 3.3.0; fixed in 4.0.16
- github.com/imgproxy/imgproxy (Go): affected all versions; no fix listed
- github.com/imgproxy/imgproxy/v2 (Go): affected all versions; no fix listed
- github.com/imgproxy/imgproxy/v4 (Go): affected all versions; 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-123616/ (Markdown: https://insights.sbomify.com/CVE-2026-123616/index.md)
```

## Sources

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

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