A buffer overflow in DCMTK git master v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a crafted DCM file.

published 2025-02-18 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-4574

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits: 0; none known

Patch / fix

distros 2 links 1

debian opensuse

dcmtk Debian 12 3.6.7-9~deb12u3
dcmtk Debian 14, Debian 13 3.6.9-4

debian advisories DEBIAN-CVE-2025-25472

dcmtk Package Hub 15 SP6, openSUSE Leap 15.6 3.6.9-bp156.4.6.1
dcmtk openSUSE Tumbleweed 3.6.9-2.1

opensuse advisories openSUSE-SU-2025:0068-1 openSUSE-SU-2025:14823-1

git.dcmtk.org/?p=dcmtk.git;a=commit;h=410ffe2019b9db6a8f4036daac742a6f5e… commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-25472 updated 2026-06-28 cvss 7.4

dcmtk: Buffer Overflow in DCMTK Leading to DoS

Red Hat Enterprise Linux AI (RHEL AI) dcmtk
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 20 mo ago (2025-02-20)

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Classification

Weakness

CWE-120 Buffer Copy without Checking Size of Input

References

git.dcmtk.org /?p=dcmtk.git;a=commit;h=410ffe2019b9db6a8f4036daac742a6f5e4d36c2
patch
lists.debian.org /debian-lts-announce/2025/06/msg00025.html
mailing-list, third-party-advisory

Sources

CVE List CVE-2025-25472
NVD CVE-2025-25472

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary