Skip to main content
Mallory
CriticalVulnerability

CVE-2026-33526: Heap Use-After-Free in Squid ICP Request Handling

Published Mar 26, 2026 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.2Critical · v4
EPSS9.3%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Squid-Cache
IdentifiersCVE-2026-33526CWE-416 · Use After Free

CVE-2026-33526 is a heap use-after-free vulnerability in Squid's Internet Cache Protocol (ICP) request handling that allows remote attackers to reliably and repeatedly crash the proxy service. Affected upstream releases span Squid 3.x through 7.4, including the 3.5.28, 4.17, 5.9, and 6.14 branch releases. Exploitation requires ICP support to be enabled through a non-zero icp_port setting. Denying ICP queries through icp_access rules does not prevent exploitation. Squid 7.5 fixes the vulnerability.

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 remote, unauthenticated attacker can repeatedly crash Squid, denying proxy service to clients and potentially disrupting dependent systems. Availability is the established impact; code execution and information disclosure have not been demonstrated for this vulnerability.

Mitigation

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

Disable ICP support by explicitly configuring icp_port 0, or leave ICP disabled. Denying queries with icp_access rules is not an effective mitigation.

Remediation

Patch, then assume compromise.

Upgrade to Squid 7.5 or a later fixed release, or install a distribution-provided package containing the backported fix. Debian trixie provides the fix in version 6.13-2+deb13u2. For installations maintained from source, apply the upstream fix appropriate to the deployed branch; an upstream patch is available for Squid 7.

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-33526 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-33526 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-33526?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-33526.
Is there a patch for CVE-2026-33526?
Upgrade to Squid 7.5 or a later fixed release, or install a distribution-provided package containing the backported fix. Debian trixie provides the fix in version 6.13-2+deb13u2.
What products are affected by CVE-2026-33526?
Squid-Cache Squid.
How severe is CVE-2026-33526?
CVE-2026-33526 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 9.3% (95th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

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

View more in app →
+4 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 activity11Community discussion across Reddit, Mastodon, and other social sources.