CVE-2026-35505 is a high-severity memory management flaw in OFFIS DCMTK affecting versions 3.7.0 and earlier. The vulnerability is caused by missing release of allocated memory on an association-handling error path. According to the provided context, an unauthenticated client can send a crafted DICOM A-ASSOCIATE-RQ in which presentation-context structures are parsed and allocated, and a later presentation context triggers a translation failure or similar parse/validation error before the parsed PDU graph is freed. Repeating these malformed connection requests leaks memory over time. The context also notes an analogous SCU-side error path in long-running DCMTK clients when parsing a malformed A-ASSOCIATE-AC from a rogue server. The issue is classified as CWE-401 (Missing Release of Memory after Effective Lifetime).
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity memory leak vulnerability in OFFIS DCMTK affecting versions prior to 3.7.0. Successful exploitation could exhaust service memory or crash imaging services.
A high-severity memory leak / denial-of-service vulnerability in the OFFIS DCMTK Toolkit that allows an unauthenticated remote attacker to repeatedly send crafted connection requests, causing memory growth until the service becomes unresponsive or is killed.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.