CVE-2025-5943: MicroDicom DICOM Viewer · Out-of-bounds Write
Affects MicroDicom DICOM ViewerSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MicroDicom DICOM Viewer | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European healthcare organizations should implement the following specific measures: 1) Immediately audit all systems running MicroDicom DICOM Viewer and restrict its use to trusted personnel only. 2) Employ strict file validation and scanning procedures for all incoming DICOM files, including those received via email or downloaded from the internet, using advanced malware detection tools capable of analyzing medical image files. 3) Educate medical staff and IT personnel about the risks of opening untrusted DICOM files and visiting suspicious websites, emphasizing the importance of verifying file sources. 4) Utilize application whitelisting and sandboxing techniques to isolate MicroDicom Viewer processes, limiting the potential impact of exploitation. 5) Monitor network traffic and endpoint behavior for anomalies indicative of exploitation attempts, such as unexpected code execution or memory corruption alerts. 6) Engage with MicroDicom vendor support channels to obtain patches or updates as soon as they become available and apply them promptly. 7) Consider alternative DICOM viewers with a stronger security track record until this vulnerability is resolved.
Description
MicroDicom DICOM Viewer suffers from an out-of-bounds write vulnerability. Remote attackers are able to exploit this issue to potentially execute arbitrary code on affected installations of DICOM Viewer. User interaction is required to exploit the vulnerability in that the user must either visit a malicious website or open a malicious DICOM file locally.