# CVE-2025-14607: OFFIS DCMTK dcmdata dcbytstr.cc makeDicomByteString memory corruption

> Remote attackers can trigger memory corruption in the DCMTK library via crafted DICOM data, potentially leading to code execution or crashes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Dec 2025
- **Updated:** 24 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-14607, GHSA-8cqp-6cwx-f84x, UBUNTU-CVE-2025-14607

## What is CVE-2025-14607?

CVE-2025-14607 is a medium-severity memory corruption vulnerability in OFFIS DCMTK, published on 13 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in OFFIS DCMTK up to 3.6.9. Affected by this issue is the function DcmByteString::makeDicomByteString of the file dcmdata/libsrc/dcbytstr.cc of the component dcmdata. The manipulation results in memory corruption. The attack can be launched remotely. Upgrading to version 3.7.0 can resolve this issue. The patch is identified as 4c0e5c10079392c594d6a7abd95dd78ac0aa556a. You should upgrade the affected component.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Upgrade to a fixed version.

## Is CVE-2025-14607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14607 is a medium-severity memory corruption vulnerability in OFFIS DCMTK, published on 13 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14607 in the wild and no public exploit code.

Affected product: OFFIS DCMTK. 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-14607/ (Markdown: https://insights.sbomify.com/CVE-2025-14607/index.md)
```

## Sources

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

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