Loading vulnerability…
CVE-2026-82209 is an improper cookie-domain scope enforcement flaw in libcurl when built with libpsl support. When processing a Set-Cookie header whose Domain attribute exactly matches an origin host that is itself listed as a Public Suffix List entry, libcurl fails to enforce the public-suffix boundary. Rather than treating the cookie as host-only, it stores the cookie with a wildcard domain scope covering the public suffix. The flaw affects curl and libcurl versions 7.44.0 through versions before 8.22.0.
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.
A libcurl cookie-domain isolation flaw affecting builds with libpsl support enabled. A Set-Cookie Domain attribute equal to a public-suffix origin can be stored as a wildcard cookie for that suffix, causing the cookie to be sent to arbitrary sibling subdomains such as attacker.co.uk.
A domain-scoped Public Suffix List domain-cookie vulnerability in curl and libcurl fixed in this release.
A critical, network-accessible vulnerability tracked as CVE-2026-82209, affecting curl packages on listed Ubuntu and Debian Linux releases. The supplied CVSS v3 vector indicates unauthenticated remote exploitation with high confidentiality, integrity, and availability impact.
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.