Loading vulnerability…
CVE-2026-58055 is an HTTP request/response smuggling vulnerability in nghttp2's nghttpx proxy through version 1.69.0. The flaw occurs when nghttpx forwards an HTTP/1.1 Upgrade request that also includes a Content-Length header and request body onto reusable keep-alive backend connections, while re-adding the Upgrade and Connection headers and passing Content-Length unchanged. This creates an ambiguous request framing condition between the proxy and backend. If the backend parses the resulting message in a way that favors attacker-controlled interpretation, the discrepancy can be exploited to smuggle a subsequent request through the proxy boundary and poison the backend response queue.
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.
9 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.