CVE-2026-50254 is a missing-release-of-memory vulnerability in the OFFIS DCMTK Toolkit affecting versions prior to 3.7.0. An unauthenticated remote client can repeatedly open a DICOM association and send an A-ASSOCIATE-RQ containing many Extended Negotiation items followed by a malformed or truncated Extended Negotiation item. This drives an error path that leaks memory instead of releasing parsed data structures. The issue is particularly impactful against storescp in its default single-process mode, where repeated crafted connection requests cause resident memory usage to grow rapidly until the process is killed or otherwise stops accepting DICOM connections. Upstream reporting identifies the fix as commit 23f181f7a.
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.
5 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 remotely exploitable memory leak vulnerability in the OFFIS DCMTK Toolkit that allows an unauthenticated attacker to repeatedly send crafted connection requests, causing memory growth and eventual denial of service of the storescp service in default single-process mode.
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.