Loading vulnerability…
CVE-2025-23311 is a stack-based buffer overflow in NVIDIA Triton Inference Server affecting all versions up to and including 25.06. The issue is in Triton’s HTTP request handling path, where attacker-controlled request fragmentation influences stack allocation. According to the provided content, the vulnerable code uses libevent’s evbuffer_peek() during HTTP processing and then uses the number of returned buffer segments as the size argument to alloca(), without proper bounds checking. By sending a specially crafted HTTP request, including abuse of chunked transfer encoding to create a very large number of small segments, a remote attacker can force excessive stack allocation and trigger stack exhaustion. The content states this can lead to a segmentation fault and may also enable remote code execution, information disclosure, or data tampering.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.