# CVE-2025-36521: MicroDicom DICOM Viewer Out-of-bounds Read

> An attacker can cause memory corruption and potential code execution by tricking a user into opening a malicious DICOM file in MicroDicom Viewer.

- **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:** 1 May 2025
- **Updated:** 1 May 2025
- **Also known as:** GHSA-cm8f-5fx7-mv6c

## What is CVE-2025-36521?

CVE-2025-36521 is a high-severity memory corruption vulnerability in MicroDicom DICOM Viewer, published on 1 May 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 is vulnerable to an out-of-bounds read which may allow an attacker to cause memory corruption within the application. The user must open a malicious DCM file for exploitation.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2025-36521 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-36521 is a high-severity memory corruption vulnerability in MicroDicom DICOM Viewer, published on 1 May 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-36521 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-36521/ (Markdown: https://insights.sbomify.com/CVE-2025-36521/index.md)
```

## Sources

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

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