Skip to main content
Mallory
HighVulnerability

CVE-2026-32748: Denial of Service 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
CVSS8.7High · v4
EPSS9.3%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Squid-Cache
IdentifiersCVE-2026-32748CWE-416 · Use After Free

CVE-2026-32748 is a premature resource release and heap use-after-free vulnerability in Squid's Internet Cache Protocol (ICP) request handling. A remote, unauthenticated attacker can send crafted ICP traffic to reliably and repeatedly crash the 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, unless vendor fixes have been applied. Exploitation requires ICP support to be enabled with a non-zero ICP port. 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.

Successful exploitation crashes Squid, disrupting proxy and caching availability. Repeated triggering can sustain a denial of service and disrupt clients or services that depend on the proxy. Confidentiality loss, integrity compromise, and code execution have not been established for this vulnerability.

Mitigation

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

Disable ICP support by setting icp_port to 0 and ensure the configuration change takes effect. Deployments with ICP disabled are not exposed to this attack. Denying ICP queries through icp_access rules does not mitigate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade to Squid 7.5 or a later fixed release, apply the published Squid 7 patch, or install a distribution-provided package update that explicitly fixes CVE-2026-32748. Distribution packages may include backported fixes without adopting the upstream 7.5 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-32748 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-32748 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-32748?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-32748.
Is there a patch for CVE-2026-32748?
Upgrade to Squid 7.5 or a later fixed release, apply the published Squid 7 patch, or install a distribution-provided package update that explicitly fixes CVE-2026-32748. Distribution packages may include backported fixes without adopting the upstream 7.5 version number.
What products are affected by CVE-2026-32748?
Squid-Cache Squid.
How severe is CVE-2026-32748?
CVE-2026-32748 has a CVSS v4 score of 8.7 (High) and an EPSS score of 9.3% (95th percentile) as of Nov 11, 2026.
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 activity10Community discussion across Reddit, Mastodon, and other social sources.