ApplicationsHigh 8.5Patch available
CVE-2026-133168
Heap overflow in DCMTK 3.7.1 allows RCE via crafted color-by-plane DICOM JPEG images
How scary is it?
updated 21 Nov 2026- Yes
Works without logging in1
No account needed, but a person has to act, such as opening a link or a file (CVSS PR:N, UI:P).
- No
Reachable over the network1
Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).
- Yes
Proof-of-concept code is public2
1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild
None reported that we know of.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run OFFIS DCMTK in an affected version3.7.1
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
The attacker already has local access to the machine
CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.
Source 1
A person takes an action, such as opening a link or a file
CVSS user interaction: required (UI:P). A victim must click, open or otherwise cooperate.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade DCMTK to the patched version; block/validate untrusted DICOM inputs.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
- CVSS
- 8.5Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 0.22%chance of exploitation in the next 30 daystop 87% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 19 Nov 2026analysed here 21 Nov 2026
Summary
Impact
Processing a crafted color-by-plane DICOM (true-lossless JPEG) can trigger a heap overflow, causing crashes and potential remote code execution.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| OFFIS DCMTK | 3.7.1Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- OFFIS DCMTK 3.7.1
- PACS servers, DICOM viewers, and imaging apps using DCMTK 3.7.1
- Any image-processing pipeline that decodes DICOM JPEG images via DCMTK
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
GitHub proofs of concept
- LLCForge/CVE-2026-1331680 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 19 Nov 2026First proof-of-concept repository on GitHub (unvetted)
- 19 Nov 2026Published1 day later
- 19 Nov 2026CVE record last updatedsame day later
- 21 Nov 2026Analysed by vulneraibility.com2 days later
Common questions
Is CVE-2026-133168 being exploited?
Not confirmed. CVE-2026-133168 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-133168?
CVE-2026-133168 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-133168?
Yes. A fix has been recorded for CVE-2026-133168. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-133168 affect?
CVE-2026-133168 affects OFFIS DCMTK 3.7.1, PACS servers, DICOM viewers, and imaging apps using DCMTK 3.7.1, Any image-processing pipeline that decodes DICOM JPEG images via DCMTK. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-133168?
Upgrade DCMTK to the patched version; block/validate untrusted DICOM inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
5 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- vulncheck.com /advisories/dcmtk-3.7.1-heap-buffer-overflow-via-jpeg-encoder-planar-configurati
Patches (1)
- github.com /DCMTK/dcmtk/commit/c22836c449bb81834fee5d883e9ebd9d7dab90b9
Other links (3)
- support.dcmtk.org /redmine/issues/1298
- github.com /DCMTK/dcmtk/blob/DCMTK-3.7.1/dcmjpeg/libsrc/djcodece.cc#L1503-L1540
- github.com /DCMTK/dcmtk
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.