Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. This attack is limited to Squid deployments that explicitly enable ICP support (i.e. configure non-zero icp_port). This problem cannot be mitigated by denying ICP queries using icp_access rules. Version 7.5 contains a patch.
CVE-2026-33515
MEDIUMNVD 6.56.9Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.9(low)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 61%
- KEV
- Not listed
Published
March 26, 2026
Last Modified
June 17, 2026
References (5)
- security-advisories@githubhttps://github.com/squid-cache/squid/commit/8138e909d2058d4401e0ad49b583afaec912b165
- security-advisories@githubhttps://github.com/squid-cache/squid/pull/2220
- security-advisories@githubhttps://github.com/squid-cache/squid/pull/2220#discussion_r2727683637
- security-advisories@githubhttps://github.com/squid-cache/squid/security/advisories/GHSA-84p4-hcx7-jj7c
- af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2026/03/25/4
Vendor Advisories for CVE-2026-33515(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-125
Frequently asked(5)
What is CVE-2026-33515?
CVE-2026-33515 is a medium vulnerability published on March 26, 2026. Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding…
When was CVE-2026-33515 disclosed?
CVE-2026-33515 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33515 actively exploited?
CVE-2026-33515 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 39.4% of all scored CVEs.
What is the CVSS score of CVE-2026-33515?
CVE-2026-33515 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.9. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-33515?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33515, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33515
Is Your Infrastructure Affected by CVE-2026-33515?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.