Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Double-free in Go net LookupCNAME with cgo DNS resolver

IdentifiersCVE-2026-33811CWE-415· Double Free

CVE-2026-33811 is a memory-management vulnerability in Go's net package affecting the cgo DNS resolver path used by LookupCNAME. When an application performs a LookupCNAME call through the cgo resolver, a very long CNAME response can trigger a double-free of C-allocated memory. The resulting memory corruption condition causes the affected Go process to crash. The issue is tracked by the Go project as issue 78803 and was fixed by the Go maintainers.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes process termination due to a crash in the vulnerable DNS resolution path, resulting in a denial-of-service condition for applications that invoke LookupCNAME through the cgo resolver. Based on the provided information, the documented impact is limited to crash/availability loss; no evidence is provided here for code execution or confidentiality/integrity impact.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by avoiding the vulnerable code path where feasible: avoid using LookupCNAME against untrusted DNS infrastructure and prefer configurations that do not rely on the cgo DNS resolver until patched. More specific mitigations are not provided in the available content.

Remediation

Patch, then assume compromise.

Upgrade to a Go release that includes the fix for CVE-2026-33811. The provided content states that the double-free has been fixed and that the fix is included in Go 1.26.3 and Go 1.25.10 as part of the May 8, 2026 security releases.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GolangGoapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity12

Community discussion across Reddit, Mastodon, and other social sources.