# CVE-2026-120251: imagecodecs 2026.3.6 through 2026.10.10 Infinite Loop via ccittfax4_decode()


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-j736-6c4x-7rx7, openSUSE-SU-2026:12406-1

## What is CVE-2026-120251?

CVE-2026-120251 is a medium-severity vulnerability in cgohlke imagecodecs, published on 1 Nov 2026. 

### Official description

imagecodecs 2026.3.6 through 2026.10.10 contains an infinite loop vulnerability in ccitt_fax4_decode_size() that allows attackers to hang the calling process by supplying a crafted CCITT Group 4 stream. Attackers can provide an 8-byte G4 stream lacking EOFB to ccittfax4_decode() or the numcodecs Ccittfax4 codec, consuming full CPU until the process is killed.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-imagecodecs` | openSUSE:Tumbleweed | All versions | 2026.10.10-2.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-120251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120251 is a medium-severity vulnerability in cgohlke imagecodecs, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120251 exists.

Affected product: cgohlke imagecodecs. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-120251/ (Markdown: https://insights.sbomify.com/CVE-2026-120251/index.md)
```

## Sources

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

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