Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilitywidely-deployed-product-advisory

Squid ICP Use-After-Free Flaws Enable Remote Denial of Service

Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen Mar 26, 2026

Squid ICP Use-After-Free Flaws Enable Remote Denial of Service

Two high-severity vulnerabilities, CVE-2026-32748 and CVE-2026-33526, were disclosed in Squid that allow remote denial-of-service attacks through malformed Internet Cache Protocol (ICP) traffic. The flaws stem from heap use-after-free conditions in both ICP response and ICP request handling, with one advisory also citing premature resource release. Affected systems are Squid deployments running versions prior to 7.5.

The bugs are only exploitable where administrators have explicitly enabled ICP by setting a non-zero icp_port, and the advisories warn that icp_access rules do not mitigate the issue. Squid 7.5 contains the fixes, and the disclosures reference upstream patches, a GitHub security advisory, and an Openwall oss-security post. Organizations using Squid with ICP enabled should prioritize upgrading and review whether ICP is necessary in exposed environments.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Mar 26, 2026
  1. Mar 26, 20268mo ago

    CVE-2026-32748 and CVE-2026-33526 are publicly disclosed

    Two high-severity Squid vulnerabilities, CVE-2026-32748 and CVE-2026-33526, were publicly documented with references to a fixing commit, GitHub security advisory, and an Openwall oss-security post. The advisories noted that icp_access rules do not mitigate the issues.

  2. Mar 26, 20268mo ago

    Squid fixes two ICP-related DoS flaws in version 7.5

    Squid released version 7.5 to fix two remote denial-of-service vulnerabilities in ICP request and response handling, both caused by heap use-after-free conditions. The flaws affect versions prior to 7.5 and are exploitable only when ICP support is explicitly enabled with a non-zero icp_port.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.