Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Out-of-Bounds Read in Squid ICP Message Handling

IdentifiersCVE-2026-33515CWE-125· Out-of-bounds Read

CVE-2026-33515 is an out-of-bounds read vulnerability in Squid's handling of ICP (Internet Cache Protocol) traffic, caused by improper input validation. When a vulnerable Squid instance processes malformed or invalid ICP requests, it may read memory beyond the intended bounds and include small portions of process memory in error responses. According to the provided content, the issue affects Squid versions 3.0 through 7.4, specifically including 3.x through 3.5.28, 4.x through 4.17, 5.x through 5.9, 6.x through 6.14, and 7.x through 7.4. The flaw is only reachable on deployments where ICP support is explicitly enabled via a non-zero icp_port. The issue was fixed in Squid 7.5.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows a remote attacker to trigger memory disclosure from the Squid process by sending invalid ICP requests. The disclosed data is described as small amounts of memory, but it may contain sensitive information present in process memory at the time of the out-of-bounds read. The primary security impact is information disclosure rather than code execution or service compromise.

Mitigation

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

If patching cannot be performed immediately, disable ICP support. Squid explicitly recommends not enabling ICP and, where necessary, setting icp_port 0 to disable it. The provided content states that icp_access rules do not mitigate this vulnerability, so filtering ICP queries with access rules should not be relied upon as a workaround.

Remediation

Patch, then assume compromise.

Upgrade Squid to version 7.5 or later, or apply the vendor-provided patch for supported Squid 7 releases if an immediate full upgrade is not possible. For distribution-packaged deployments, install the vendor-maintained fixed package versions. The provided Debian advisory indicates that stable distribution users should upgrade to squid version 6.13-2+deb13u2 or later fixed package versions supplied by Debian.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
DebianSquidapplication
Squid-CacheSquidapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.