# CVE-2026-10528: Orthanc DICOM Server DCMTK FromDcmtkBridge.cpp read stack-based overflow

> A local attacker can trigger a stack-based buffer overflow in the Orthanc DICOM Server's DCMTK parser, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10528, GHSA-crj5-j279-vv6p, UBUNTU-CVE-2026-10528

## What is CVE-2026-10528?

CVE-2026-10528 is a medium-severity memory corruption vulnerability in Orthanc DICOM Server, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in Orthanc DICOM Server up to 1.12.11. This issue affects the function DcmItem::read of the file OrthancFramework/Sources/DicomParsing/FromDcmtkBridge.cpp of the component DCMTK Parser. Performing a manipulation results in stack-based buffer overflow. Attacking locally is a requirement. The exploit has been released to the public and may be used for attacks. The patch is named bae99026ca97. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-10528?


## How do I fix CVE-2026-10528?

Apply the vendor's patch.

## Is CVE-2026-10528 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10528 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10528 and fix it if it is affected.

What it is: CVE-2026-10528 is a medium-severity memory corruption vulnerability in Orthanc DICOM Server, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10528 exists.

Affected product: Orthanc DICOM Server. 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-2026-10528/ (Markdown: https://insights.sbomify.com/CVE-2026-10528/index.md)
```

## Sources

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

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