# CVE-2025-9732: DCMTK dcm2img diybrpxt.h memory corruption

> A memory corruption vulnerability in DCMTK's dcm2img tool allows local attackers to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2025
- **Updated:** 2 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-9732, GHSA-qw76-8prh-rg34, MGASA-2025-0265, UBUNTU-CVE-2025-9732, openSUSE-SU-2025:15504-1

## What is CVE-2025-9732?

CVE-2025-9732 is a medium-severity memory corruption vulnerability in DCMTK, published on 31 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in DCMTK up to 3.6.9. This affects an unknown function in the library dcmimage/include/dcmtk/dcmimage/diybrpxt.h of the component dcm2img. Such manipulation leads to memory corruption. Local access is required to approach this attack. The name of the patch is 7ad81d69b. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dcmtk` | openSUSE:Tumbleweed | All versions | 3.6.9-4.1 |

Products: Offis Dcmtk.

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

Apply the vendor's patch.

## Is CVE-2025-9732 being exploited?

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

## Other vulnerabilities in DCMTK

- [CVE-2024-47796](https://insights.sbomify.com/CVE-2024-47796/): Memory corruption in DCMTK (high 8.4)
- [CVE-2024-52333](https://insights.sbomify.com/CVE-2024-52333/): Memory corruption in DCMTK (high 8.4)
- [CVE-2024-27628](https://insights.sbomify.com/CVE-2024-27628/): Memory corruption in n/a (high 8.1)
- [CVE-2022-43272](https://insights.sbomify.com/CVE-2022-43272/): Denial of service in n/a (high 7.5)
- [CVE-2021-41687](https://insights.sbomify.com/CVE-2021-41687/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9732 is a medium-severity memory corruption vulnerability in DCMTK, published on 31 Aug 2025. 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-2025-9732 exists.

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

## Sources

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

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