Loading vulnerability…
CVE-2026-58160 is an out-of-bounds read vulnerability in Apache Traffic Server caused by improper bounds handling while parsing DNS answers. The flaw affects Apache Traffic Server versions 8.0.0 through 8.1.9, 9.0.0 through 9.2.14, and 10.0.0 through 10.1.3. A malformed or otherwise unexpected DNS response can cause the parser to read memory beyond the intended buffer while processing DNS answer data. This is a memory-safety issue in the DNS response parsing path and can lead to process instability and potentially unintended disclosure of memory contents.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced in a Fedora security update for the trafficserver package; no further technical details are provided in the content.
A vulnerability referenced in a Fedora security update for the trafficserver package; specific technical details are not provided in the content.
An out-of-bounds read vulnerability in Apache Traffic Server during DNS response parsing.
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.