# CVE-2026-133167: OFFIS DCMTK 3.5.4 through 3.7.1 Heap Out-of-Bounds Read via encodeTrueLossless


- **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:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-4p5h-7qh4-cpm9

## What is CVE-2026-133167?

CVE-2026-133167 is a medium-severity vulnerability in OFFIS DCMTK, published on 19 Nov 2026. 

### Official description

OFFIS DCMTK 3.5.4 through 3.7.1 contains an integer overflow in DJCodecEncoder::encodeTrueLossless size checks that allows attackers to trigger a heap out-of-bounds read. Attackers can supply a crafted DICOM file with large Columns, Rows and SamplesPerPixel values that, when compressed with true-lossless JPEG, crashes the application.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

1 open source package ship an affected version, including dcmtk/dcmtk.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dcmtk/dcmtk` | GitHub | `pkg:github/dcmtk/dcmtk` | From 3.5.4 to 3.7.1 | None |

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

No fix has been published for CVE-2026-133167 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-133167 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133167 is a medium-severity vulnerability in OFFIS DCMTK, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133167 in the wild and no public exploit code.

Affected packages and fixed versions:
- dcmtk/dcmtk (GitHub): affected from 3.5.4 up to 3.7.1; no fix listed

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

## Sources

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

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