Skip to main content
Mallory
MediumVulnerability

CVE-2026-50012: Heap-based buffer overflow in Squid cache digest reply handling

Published Jul 16, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS5.5Medium · v3.1
EPSS1.4%72nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Squid-Cache
IdentifiersCVE-2026-50012CWE-122 · Heap-based Buffer Overflow

CVE-2026-50012 is a heap-based buffer overflow in Squid versions before 7.6 without a vendor backport. Improper input validation in peerDigestSwapInMask allows a cache digest reply's on-the-wire size to exceed the mask_size declared within the digest, causing a heap buffer overflow. A trusted cache peer can trigger the flaw by returning a maliciously crafted response to a cache_digest request. Affected deployments must be compiled with --enable-cache-digests and configured with cache_peer entries. Exploitation can cause memory corruption and crash the proxy.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

A malicious trusted peer can cause heap memory corruption and potentially crash Squid, disrupting proxy availability. The CVSS v3.1 assessment indicates high availability impact, low integrity impact, and no confidentiality impact. Arbitrary code execution is not established.

Mitigation

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

Until patched, eliminate the vulnerable cache digest processing path by using a Squid build without --enable-cache-digests or removing cache_peer configuration where operationally feasible. These measures follow from the exploitation prerequisites; no specific vendor-endorsed interim workaround is identified.

Remediation

Patch, then assume compromise.

Upgrade to Squid 7.6 or later, or install a distribution-provided package containing the backported fix. Debian trixie provides the fix in squid 6.13-2+deb13u2. For other distributions, install the applicable vendor security update rather than relying solely on the upstream version number.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
Squid-CacheSquidapplication
FAQ

Frequently asked questions

Is CVE-2026-50012 exploited in the wild?
As of Nov 13, 2026, Mallory has no reports of CVE-2026-50012 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-50012?
As of Nov 13, 2026, Mallory has found no public exploit for CVE-2026-50012.
Is there a patch for CVE-2026-50012?
Upgrade to Squid 7.6 or later, or install a distribution-provided package containing the backported fix. Debian trixie provides the fix in squid 6.13-2+deb13u2.
What products are affected by CVE-2026-50012?
Squid-Cache Squid.
How severe is CVE-2026-50012?
CVE-2026-50012 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 1.4% (72nd percentile) as of Nov 13, 2026.
Activity feed

Recent activity

40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity24Community discussion across Reddit, Mastodon, and other social sources.