CVE Intelligence
High Memory corruption

CVE-2025-9732 — DCMTK dcm2img diybrpxt.h memory corruption

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.

Published Aug 31, 2025 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (high)+6
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.18%
ahead of 7% of scored CVEs · Oct 19, 2026
Affects
Offis
Dcmtk
CVSS base
7.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Offis Dcmtk).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Offis Dcmtk ≤ 3.6.9 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.8 CVSS 4.0 Medium — — cna@vuldb.com via NIST National Vulnerability Database
4.8 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium 1.8 3.4 cna@vuldb.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.3 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.3 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
4.3 CVSS 2.0 Medium 3.1 6.4 cna@vuldb.com via NIST National Vulnerability Database
4.3 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 19, 2026
  • Fix documented
    Oct 19, 2026 · NIST National Vulnerability Database
  • Affected products added · offis/dcmtk
    Oct 19, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.8
    Oct 19, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 19, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 19, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Aug 31, 2025 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

6 on the record

Elsewhere on this site

Offis
every CVE for this vendor
Memory corruption
same class
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-44037 Uncontrolled recursion in DCMTK JSON reader allows denial of service 11d
  • CVE-2026-44038 Global buffer out-of-bounds read in DCMTK JPEG Huffman decoding 11d
  • CVE-2026-44033 Uncontrolled recursion in the DCMTK bundled XML parser allows denial of service 11d
  • CVE-2026-44035 Uncontrolled recursion in DCMTK DICOMDIR parsing allows denial of service 11d
  • CVE-2026-44034 Heap out-of-bounds read in DCMTK RLE decodeFrame() 11d
  • CVE-2026-44036 Uncontrolled recursion in DCMTK xml2dcm allows denial of service 11d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-9732 is "DCMTK dcm2img diybrpxt.h memory corruption", rated High. It affects Dcmtk (Offis); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.