{"id":"CVE-2026-44034","aliases":["DEBIAN-CVE-2026-44034","EUVD-2026-94937","GHSA-mmr5-x4mp-rpf4","UBUNTU-CVE-2026-44034"],"status":"published","title":"Heap out-of-bounds read in DCMTK RLE decodeFrame()","description":"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.","severity":{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00107,"percentile":0.01141,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-125"],"published":"2026-10-08T12:55:09Z","modified":"2026-10-20T17:21:11Z","affected":[{"source":"osv","ecosystem":"Debian:12","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.7-11","3.6.7-12","3.6.7-13","3.6.7-14","3.6.7-15","3.6.7-8","3.6.7-9","3.6.7-9.1","3.6.7-9~deb12u1","3.6.7-9~deb12u2","3.6.7-9~deb12u3","3.6.7-9~deb12u4","3.6.8-1","3.6.8-2","3.6.8-3","3.6.8-4","3.6.8-5","3.6.8-6","3.6.8-7","3.6.8~git20221024.b8950f9-1","3.6.8~git20221024.b8950f9-2","3.6.8~git20221024.b8950f9-3","3.6.8~git20231027.1549d8c-1","3.6.8~git20231027.1549d8c-2","3.6.9-1","3.6.9-2","3.6.9-3","3.6.9-4","3.6.9-5","3.6.9-6","3.7.0+really3.6.9-1","3.7.0+really3.7.0-0+exp1","3.7.0+really3.7.0-1","3.7.0+really3.7.0-2","3.7.0+really3.7.0-3","3.7.0+really3.7.0-4","3.7.0+really3.7.0-5","3.7.0+really3.7.0-6","3.7.0+really3.7.0-7","3.7.0-1"]},{"source":"osv","ecosystem":"Debian:13","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.9-5","3.6.9-5+deb13u1","3.6.9-5+deb13u2","3.6.9-5+deb13u3","3.6.9-6","3.7.0+really3.6.9-1","3.7.0+really3.7.0-0+exp1","3.7.0+really3.7.0-1","3.7.0+really3.7.0-2","3.7.0+really3.7.0-3","3.7.0+really3.7.0-4","3.7.0+really3.7.0-5","3.7.0+really3.7.0-6","3.7.0+really3.7.0-7","3.7.0-1"]},{"source":"osv","ecosystem":"Debian:14","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.9-5","3.6.9-6","3.7.0+really3.6.9-1","3.7.0+really3.7.0-0+exp1","3.7.0+really3.7.0-1","3.7.0+really3.7.0-2","3.7.0+really3.7.0-3","3.7.0+really3.7.0-4","3.7.0+really3.7.0-5","3.7.0+really3.7.0-6","3.7.0+really3.7.0-7","3.7.0-1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.0-15.1","3.6.1~20150629-5","3.6.1~20150924-4","3.6.1~20150924-5","3.6.1~20150924-5ubuntu0.1~esm1","3.6.1~20150924-5ubuntu0.1~esm2","3.6.1~20150924-5ubuntu0.1~esm3"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2-2","3.6.2-2build1","3.6.2-3","3.6.2-3build1","3.6.2-3build2","3.6.2-3build3","3.6.2-3ubuntu0.1~esm1","3.6.2-3ubuntu0.1~esm2","3.6.2-3ubuntu0.1~esm3"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.4-2.1","3.6.4-2.1build1","3.6.4-2.1build2","3.6.4-2.1ubuntu0.1~esm1","3.6.4-2.1ubuntu0.1","3.6.4-2.1ubuntu0.1+esm1","3.6.4-2.1ubuntu0.2","3.6.4-2.1ubuntu0.2+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.5-1","3.6.6-3ubuntu1","3.6.6-3ubuntu2","3.6.6-4","3.6.6-5","3.6.6-5ubuntu0.1~esm1","3.6.6-5ubuntu0.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.7-9","3.6.7-9.1build2","3.6.7-9.1build3","3.6.7-9.1build4","3.6.7-9.1ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.7.0+really3.6.9-1","3.7.0+really3.7.0-2","3.7.0+really3.7.0-5","3.7.0+really3.7.0-6","3.7.0+really3.7.0-7ubuntu1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"dcmtk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.9-5build1","3.6.9-6","3.7.0+really3.6.9-1"]}],"products":[{"vendor":"offis","product":"dcmtk"}],"references":[{"url":"https://support.dcmtk.org/redmine/issues/1213","tags":["issue-tracking","vendor-advisory","web","report"]},{"url":"https://github.com/DCMTK/dcmtk/commit/45469f3c30037e9c7159290e4bb74cd7b3b9ef1d","tags":["patch","fix","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-44034"},{"url":"https://github.com/advisories/GHSA-mmr5-x4mp-rpf4"},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-44034","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-44034","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-44034","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-44034","title":"Heap out-of-bounds read in DCMTK RLE decodeFrame()","description":"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.","status":"published","published":"2026-10-08T12:55:09.201Z","modified":"2026-10-08T14:09:23.67Z","cvss":[{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium","assessor":"cna"},{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T13:42:49.132798Z"}],"euvd":[{"id":"EUVD-2026-94937","description":"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.","status":"published","published":"2026-10-08T12:55:09Z","modified":"2026-10-08T14:09:23Z","cvss":[{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-02T17:27:32.642438Z"}],"ghsa":[{"id":"GHSA-mmr5-x4mp-rpf4","title":"A heap-based out-of-bounds read in DcmRLECodecDecoder::decodeFrame() in dcmdata/libsrc/dcrleccd...","description":"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.","status":"published","published":"2026-10-08T15:32:58Z","modified":"2026-10-08T15:32:59Z","cvss":[{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"},{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","level":"medium"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T15:12:56.476072Z"}],"nvd":[{"id":"CVE-2026-44034","description":"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.","status":"published","published":"2026-10-08T13:17:17.347Z","modified":"2026-10-08T21:10:00.133Z","cvss":[{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"},{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","level":"medium","assessor":"secondary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:12:55.142936Z"}],"osv":[{"id":"CVE-2026-44034","description":"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.","status":"published","published":"2026-10-08T13:17:17.347Z","modified":"2026-10-20T17:21:11.37186477Z","cvss":[{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-02T15:45:04.820169Z"},{"id":"DEBIAN-CVE-2026-44034","description":"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.","status":"published","published":"2026-10-08T13:17:17.347Z","modified":"2026-10-09T11:00:08.067612091Z","cvss":[{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-02T15:45:55.669088Z"},{"id":"UBUNTU-CVE-2026-44034","description":"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.","status":"published","published":"2026-10-08T13:17:00Z","modified":"2026-10-17T12:58:18.787169751Z","cvss":[{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","level":"medium"},{"version":"4.0","score":4.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-02T16:56:22.075798Z"}]}}