Heap-based Buffer Overflow in Squid cache_digest reply handling
CVE-2026-50012 is an improper input validation vulnerability in Squid that affects cache digest processing. When Squid sends cache_digest request messages, a trusted peer/server can respond with maliciously crafted replies that trigger a heap-based buffer overflow in the receiving Squid instance. The issue is specifically described as a heap-based buffer overflow caused by insufficient validation of input associated with cache_digest replies. The vulnerability is limited to Squid builds compiled with the --enable-cache-digests option. Public reporting indicates the issue was fixed in Squid 7.6, with an associated patch published in the squid-cache repository as commit 19fcfe922717c8b255270c032dcde4071c003bcd.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.