Loading vulnerability…
CVE-2026-33811 is a double-free vulnerability in the Go standard library's net package. When LookupCNAME uses the cgo DNS resolver, processing an excessively long CNAME response can cause C memory to be freed twice, crashing the application. Exposure depends on the application invoking the affected lookup path with the cgo resolver. The vulnerability is rated High with a CVSS v3.0 score of 7.5.
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.
182 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A double-free vulnerability in the stdlib library's LookupCNAME functionality when using the cgo DNS resolver. A very long CNAME response can cause a crash and denial of service. The advisory rates it High, with a CVSS v3 base score of 7.5 and availability impact only.
Referenced vulnerability covered by the Oracle Linux image-builder security advisory; its technical details are not provided.
Unknown
A denial-of-service vulnerability in Go's net package, where a long CNAME response processed by LookupCNAME can cause resource exhaustion or service disruption.
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.