Loading vulnerability…
CVE-2026-58175 is a high-severity memory management vulnerability in Apache Traffic Server caused by improper release of memory while handling HostDB SRV records in HostDB processing. 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. Repeated processing of affected SRV record handling paths can cause memory to accumulate instead of being freed after its effective lifetime, resulting in progressive resource exhaustion. Published classifications map the issue to CWE-401.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical or high-severity vulnerability in Apache Traffic Server addressed by released security updates.
A memory leak vulnerability in Apache Traffic Server triggered when handling HostDB SRV records, impacting availability.
A memory leak vulnerability in Apache Traffic Server involving HostDB SRV record handling.
A high-severity memory leak vulnerability in Apache Traffic Server related to handling HostDB SRV records, which can impact availability.
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.