CVE-2025-25475

CVE-2025-25475 is a high-severity vulnerability in Offis Dcmtk with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-476.

Key facts

Description

A NULL pointer dereference in the component /libsrc/dcrleccd.cc of DCMTK v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a crafted DICOM file.

Frequently asked questions

What is CVE-2025-25475?
A NULL pointer dereference in the component /libsrc/dcrleccd.cc of DCMTK v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a crafted DICOM file.
How severe is CVE-2025-25475?
CVE-2025-25475 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-25475 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-25475?
CVE-2025-25475 primarily affects Offis Dcmtk. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-25475?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-25475 have an EU (EUVD) identifier?
Yes. CVE-2025-25475 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-4573.
When was CVE-2025-25475 published?
CVE-2025-25475 was published on 2025-02-18 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Offis Dcmtk

All CVEs affecting Offis Dcmtk →

Other CWE-476 (NULL Pointer Dereference) vulnerabilities

Browse all CWE-476 (NULL Pointer Dereference) vulnerabilities →