Loading vulnerability…
CVE-2026-80255 is a cookie-handling flaw in curl and libcurl affecting versions 7.44.0 through versions before 8.22.0. When parsing a Set-Cookie response header, curl fails to recognize the Secure attribute if a horizontal tab character, rather than a space, immediately precedes that attribute. curl consequently stores the cookie without its Secure flag, despite the server specifying Secure.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A curl cookie-parsing vulnerability in which a horizontal tab before the Secure attribute prevents the cookie from being marked Secure, potentially causing it to be transmitted over plaintext HTTP.
A secure-cookie attribute bypass caused by tab handling in curl and libcurl, remediated in this release.
A network-accessible, low-complexity curl vulnerability with no required privileges or user interaction, rated for high confidentiality, integrity, and availability impact. The referenced assessment identifies affected curl packages on specified Ubuntu and Debian releases.
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.