CVE Tools
Track your stack

Dicom

8 CVEs tracked since 2017. Since Feb 2017, none of them reached CISA KEV.

Dicom CVEs per month

Feb 2017 to Jun 2022. Point at a month, or focus the strip and use the arrow keys.
Dicom CVEs per month, with the share now in CISA KEV
MonthCVEsIn CISA KEV
2017-0210
2017-03null or fewer
2017-04null or fewer
2017-05null or fewer
2017-06null or fewer
2017-07null or fewer
2017-08null or fewer
2017-09null or fewer
2017-10null or fewer
2017-11null or fewer
2017-12null or fewer
2018-01null or fewer
2018-02null or fewer
2018-03null or fewer
2018-04null or fewer
2018-05null or fewer
2018-06null or fewer
2018-07null or fewer
2018-08null or fewer
2018-09null or fewer
2018-10null or fewer
2018-11null or fewer
2018-12null or fewer
2019-01null or fewer
2019-02null or fewer
2019-03null or fewer
2019-04null or fewer
2019-05null or fewer
2019-06null or fewer
2019-07null or fewer
2019-08null or fewer
2019-09null or fewer
2019-10null or fewer
2019-11null or fewer
2019-12null or fewer
2020-01null or fewer
2020-02null or fewer
2020-03null or fewer
2020-04null or fewer
2020-05null or fewer
2020-06null or fewer
2020-07null or fewer
2020-08null or fewer
2020-09null or fewer
2020-10null or fewer
2020-11null or fewer
2020-12null or fewer
2021-01null or fewer
2021-02null or fewer
2021-03null or fewer
2021-04null or fewer
2021-05null or fewer
2021-06null or fewer
2021-07null or fewer
2021-08null or fewer
2021-09null or fewer
2021-10null or fewer
2021-11null or fewer
2021-12null or fewer
2022-01null or fewer
2022-02null or fewer
2022-03null or fewer
2022-04null or fewer
2022-05null or fewer
2022-0670

Products

The products that kept showing up in Dicom's monthly top three, with their CVEs summed over those months.

  1. Dcmtk82 months

Latest CVEs

The 15 most recently published vulnerabilities affecting Dicom.

  1. CVE-2025-14841OFFIS DCMTK dcmqrscp dcmqrdbi.cc startMoveRequest null pointer dereference3.3
  2. CVE-2025-14607OFFIS DCMTK dcmdata dcbytstr.cc makeDicomByteString memory corruption6.3
  3. CVE-2022-4981DCMTK dcmqrscp dcmqrcnf.cc readPeerList null pointer dereference3.3
  4. CVE-2020-36855DCMTK dcmqrscp parseQuota stack-based overflow5.3
  5. CVE-2025-9732DCMTK dcm2img diybrpxt.h memory corruption5.3
  6. CVE-2025-2357DCMTK dcmjpls JPEG-LS Decoder memory corruption6.3
  7. CVE-2025-25475A NULL pointer dereference in the component /libsrc/dcrleccd.cc of DCMTK v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a crafted DICOM file.7.5
  8. CVE-2025-25474DCMTK v3.6.9+ DEV was discovered to contain a buffer overflow via the component /dcmimgle/diinpxt.h.6.5
  9. CVE-2025-25472A buffer overflow in DCMTK git master v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a crafted DCM file.5.3
  10. CVE-2024-52333An improper array index validation vulnerability exists in the determineMinMax functionality of OFFIS DCMTK 3.6.8. A specially crafted DICOM file can lead to an out-of-bounds write. An attacker can...8.4
  11. CVE-2024-47796An improper array index validation vulnerability exists in the nowindow functionality of OFFIS DCMTK 3.6.8. A specially crafted DICOM file can lead to an out-of-bounds write. An attacker can provid...8.4
  12. CVE-2024-27628Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to execute arbitrary code via the EctEnhancedCT method component.8.1
  13. CVE-2024-34509dcmdata in DCMTK before 3.6.9 has a segmentation fault via an invalid DIMSE message.5.3
  14. CVE-2024-34508dcmnet in DCMTK before 3.6.9 has a segmentation fault via an invalid DIMSE message.4.3
  15. CVE-2024-28130An incorrect type conversion vulnerability exists in the DVPSSoftcopyVOI_PList::createFromImage functionality of OFFIS DCMTK 3.6.8. A specially crafted malformed file can lead to arbitrary code exe...7.5

The record

Peak rank
#98 in Jun 2022
Busiest month shown
Jun 2022, 7 CVEs
Months with a KEV entry
0 since Feb 2017
Monthly snapshots
2 since 2017
Dicom's full record, month by month

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store