A heap-based out-of-bounds read in DcmRLECodecDecoder::decodeFrame() in dcmdata/libsrc/dcrleccd.cc of OFFIS DCMTK 3.7.0 allows an attacker to read up to 63 bytes of adjacent heap memory, or cause a crash, via a crafted RLE Lossless DICOM file whose pixel data fragment is shorter than the 64-byte RLE header. The function copies 64 bytes without checking the fragment length, a check that the sibling function decode() already performs. Applications that decode RLE images frame by frame (for example, through DcmPixelData::getUncompressedFrame()) are affected. The dcmdrle command-line tool uses decode() and is not affected. The issue is fixed in commit 45469f3c30037e9c7159290e4bb74cd7b3b9ef1d.
CVE-2026-44034
MEDIUMPre-NVD 4.44.4Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 4.4 from GitHub Security Advisory published 2026-10-08. A secondary CVSS source baseline 4.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.4
- EG Score
- 4.4MEDIUMhigh confidence
- EG Risk
- 20EG Risk 20/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity44% × 45%The EG Score, 4.4 of 10.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 1st
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 8, 2026
Last Modified
October 8, 2026
Advisory Details (2)
Auto-updated Oct 8, 2026Patch available. Sources: github_commit.
GitHub commit Patch Available
commit 45469f3c3003 (DCMTK/dcmtk)
Patch available: DCMTK/dcmtk latest (contains commit 45469f3c3003)
https://github.com/DCMTK/dcmtk/commit/45469f3c30037e9c7159290e4bb74cd7b3b9ef1dVendor Advisories for CVE-2026-44034(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dcmtk | 3.6.7-11 ... 3.7.0-1 (40 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dcmtk | 3.6.9-5 ... 3.7.0-1 (15 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dcmtk | 3.6.9-5 ... 3.7.0-1 (12 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 20× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-12 16:05 UTCEG score recompute
- 2026-10-11 23:41 UTCGHSA enrichmentGHSA-mmr5-x4mp-rpf4 · GitHub CVSS 4.4
- 2026-10-11 19:47 UTCEG score recompute
- 2026-10-11 17:02 UTCEG score recompute
- 2026-10-11 14:27 UTCEG score recompute
- 2026-10-10 22:53 UTCEG score recompute
- 2026-10-10 22:53 UTCGHSA enrichmentGHSA-mmr5-x4mp-rpf4 · GitHub CVSS 4.4
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-09 22:06 UTCEG score recompute
- 2026-10-09 22:06 UTCGHSA enrichmentGHSA-mmr5-x4mp-rpf4 · GitHub CVSS 4.4
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-08 21:18 UTCEG score recompute
- 2026-10-08 21:18 UTCGHSA enrichmentGHSA-mmr5-x4mp-rpf4 · GitHub CVSS 4.4
- 2026-10-08 15:23 UTCEG score recompute
- 2026-10-08 14:45 UTCEG score recompute
- 2026-10-08 13:32 UTCEG score recompute
- 2026-10-08 13:04 UTCEG score recomputeFirst assessed: 4.4 MEDIUM
- 2026-10-08 13:01 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:dcmtk
Frequently asked(5)
What is CVE-2026-44034?
CVE-2026-44034 is a medium-severity vulnerability; its CVE record was published on October 8, 2026. A heap-based out-of-bounds read in DcmRLECodecDecoder::decodeFrame() in dcmdata/libsrc/dcrleccd.cc of OFFIS DCMTK 3.7.0 allows an attacker to read up to 63 bytes of adjacent heap memory, or cause a crash, via a crafted RLE Lossless DICOM file whose pixel data fragment is shorter than the 64-byte…
When was the CVE record for CVE-2026-44034 published?
The CVE record for CVE-2026-44034 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-44034 actively exploited?
CVE-2026-44034 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44034?
CVE-2026-44034 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44034?
A fix for CVE-2026-44034 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44034 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44034
Is Your Infrastructure Affected by CVE-2026-44034?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.