# CVE-2025-5943: MicroDicom DICOM Viewer Out-of-bounds Write

> Remote attackers can execute arbitrary code by tricking users into opening malicious DICOM files or visiting malicious websites.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** GHSA-863r-cfhv-7rmg

## What is CVE-2025-5943?

CVE-2025-5943 is a high-severity memory corruption vulnerability in MicroDicom DICOM Viewer, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-5943?


## How do I fix CVE-2025-5943?

No fix has been published for CVE-2025-5943 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5943 being exploited?

There is no known exploitation of CVE-2025-5943 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5943 and fix it if it is affected.

What it is: CVE-2025-5943 is a high-severity memory corruption vulnerability in MicroDicom DICOM Viewer, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-5943 in the wild and no public exploit code.

Affected product: MicroDicom DICOM Viewer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5943/ (Markdown: https://insights.sbomify.com/CVE-2025-5943/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5943
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5943
- OSV: https://osv.dev/vulnerability/CVE-2025-5943

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5943/
Summaries are generated and may contain mistakes; the official description above is the record.