Skip to main content
Mallory
MediumVulnerability

CVE-2026-33515: Squid ICP Out-of-Bounds Read and Memory Disclosure

Published Mar 26, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS6.9Medium · v4
EPSS1.1%66th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Squid-Cache
IdentifiersCVE-2026-33515CWE-125 · Out-of-bounds Read

CVE-2026-33515 is an out-of-bounds read vulnerability in Squid's Internet Cache Protocol (ICP) message handling caused by improper input validation. Malformed ICP requests can cause error responses to include small amounts of process memory, potentially exposing sensitive information to a remote attacker. The vulnerability affects unpatched Squid versions 3.0 through 7.4 when ICP is explicitly 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.

An unauthenticated remote attacker can obtain small amounts of Squid process memory through error responses to invalid ICP requests. The disclosed memory may contain sensitive information. Arbitrary code execution, service disruption, and specific categories of exposed secrets are not established for this vulnerability.

Mitigation

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

Disable ICP by explicitly configuring icp_port 0, or leave ICP support disabled. Denying ICP queries through icp_access rules does not mitigate this vulnerability.

Remediation

Patch, then assume compromise.

Upgrade to Squid 7.5 or later, or install a distribution-maintained package containing the backported fix. Debian trixie provides a fix in version 6.13-2+deb13u2. For source-based Squid 7 installations, an upstream patch is available; apply the SQUID-2026:1 prerequisite patch first and account for possible patch application conflicts. Users of packaged installations should follow their vendor's security update guidance rather than relying solely on the upstream 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-33515 exploited in the wild?
As of Oct 27, 2026, Mallory has no reports of CVE-2026-33515 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-33515?
As of Oct 27, 2026, Mallory has found no public exploit for CVE-2026-33515.
Is there a patch for CVE-2026-33515?
Upgrade to Squid 7.5 or later, or install a distribution-maintained package containing the backported fix. Debian trixie provides a fix in version 6.13-2+deb13u2.
What products are affected by CVE-2026-33515?
Squid-Cache Squid.
How severe is CVE-2026-33515?
CVE-2026-33515 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 1.1% (66th percentile) as of Oct 27, 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 activity6Community discussion across Reddit, Mastodon, and other social sources.