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

Squid ICP Flaws Expose Proxies to DoS and Memory Disclosure

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

Squid ICP Flaws Expose Proxies to DoS and Memory Disclosure

Squid disclosed three security issues in its Internet Cache Protocol (ICP) request handling, including CVE-2026-33515, an out-of-bounds read that can leak small amounts of process memory in error responses to malformed ICP requests. The memory disclosure bug affects Squid versions 3.0 through 7.4 when ICP support is explicitly enabled with a non-zero icp_port, and the project said icp_access rules do not mitigate the issue. The flaw was reported and fixed by Joshua Rogers of ZeroPath and Alex Rousskov of The Measurement Factory.

The advisories also include SQUID-2026:1 and SQUID-2026:2, both describing denial-of-service conditions in ICP request handling, indicating a broader weakness in how Squid processes ICP traffic. Squid said the memory disclosure issue is fixed in version 7.5, and it published a patch for supported 7.x stable releases; administrators that cannot patch were advised to disable ICP or set icp_port 0 to remove exposure.

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.

3 events · Sep 7, 2025 – Mar 25, 2026
  1. Mar 25, 20268mo ago

    GitHub republishes Squid security advisories including SQUID-2026:3

    GitHub security advisories for the squid-cache/squid project listed SQUID-2026:3 alongside related ICP-handling advisories SQUID-2026:1 and SQUID-2026:2. This reflects broader publication of the Squid advisory set through GitHub's advisory channel.

  2. Sep 7, 20251y ago

    Squid publishes advisory SQUID-2026:3 and releases fixes for CVE-2026-33515

    Squid published security advisory SQUID-2026:3 for CVE-2026-33515, warning that invalid ICP requests can trigger error responses that leak small amounts of memory containing potentially sensitive information. Squid said icp_access rules do not mitigate the issue, recommended disabling ICP or setting "icp_port 0" as a workaround, and released a fix in Squid 7.5 plus a patch for Squid 7 stable releases.

  3. Sep 7, 20251y ago

    ZeroPath and The Measurement Factory discover and fix CVE-2026-33515

    Joshua Rogers of ZeroPath and Alex Rousskov of The Measurement Factory discovered and fixed an out-of-bounds read vulnerability in Squid ICP message handling, later assigned CVE-2026-33515. The flaw affects Squid versions 3.0 through 7.4 when ICP 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.