# CVE-2026-120436: Netpbm before 10.86.51, 11.02.30, and 11.15.08 Heap Overflow via jbigtopnm


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120436, GHSA-wj4q-h4hq-8gh7, UBUNTU-CVE-2026-120436

## What is CVE-2026-120436?

CVE-2026-120436 is a high-severity vulnerability in Netpbm, published on 2 Nov 2026. 

### Official description

Netpbm before 10.86.51, 11.x before 11.02.30, and 11.03 before 11.15.08 contains an integer overflow in jbigtopnm that causes heap buffer overflow when computing output buffer size. Attackers can supply a crafted multi-plane JBIG file with large header dimensions so jbg_dec_merge_planes() overflows the undersized buffer, causing crashes or potentially code execution.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120436 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120436 is a high-severity vulnerability in Netpbm, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120436 in the wild and no public exploit code.

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

## Sources

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

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