CVE-2026-1801 is an HTTP request-smuggling vulnerability in the libsoup HTTP client/server library. The flaw is in the soup_filter_input_stream_read_line() parsing logic for chunked HTTP requests. libsoup accepts malformed chunk headers containing a lone line-feed character where HTTP requires a carriage-return/line-feed sequence. This parsing discrepancy can cause a crafted network message to be interpreted and processed as multiple HTTP requests.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
An HTTP request-smuggling vulnerability in libsoup caused by non-RFC-compliant parsing of chunked-request headers. A remote unauthenticated attacker can send crafted chunked requests that libsoup interprets as multiple HTTP requests, potentially resulting in information disclosure.
A libsoup vulnerability included in NewStart CGSL advisory NS-SA-2026-0100; technical details are not provided.
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.