CVE-2026-33515

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 1.0%, top 39% of all CVEs by exploit prediction. 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: epss, nvd
6.5EG
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.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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 computed
Severity65% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
62%
KEV
Not listed

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 3, 2026
Patch available. Sources: github_commit, github_pr, github.
generic Patch Available

oss-security - [ADVISORY] SQUID-2026:3 Out of Bounds Read in ICP message handling (CVE-2026-33515)

http://www.openwall.com/lists/oss-security/2026/03/25/4
github Patch Available

SQUID-2026:3 Out of Bounds Read in ICP message handling · Advisory · squid-cache/squid · GitHub

https://github.com/squid-cache/squid/security/advisories/GHSA-84p4-hcx7-jj7c
github_pr

ICP: Fix validation of packet sizes and URLs

Upstream fix in progress (PR #2220 · squid-cache/squid, state=closed)

https://github.com/squid-cache/squid/pull/2220#discussion_r2727683637
github_pr

ICP: Fix validation of packet sizes and URLs

Upstream fix in progress (PR #2220 · squid-cache/squid, state=closed)

https://github.com/squid-cache/squid/pull/2220
github_commit

commit 8138e909d205 (squid-cache/squid)

Fix landed in squid-cache/squid commit 8138e909d205 — awaiting tagged release

https://github.com/squid-cache/squid/commit/8138e909d2058d4401e0ad49b583afaec912b165

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
squid4.13-10 ... 4.13-10+deb11u6 (7 versions)4.13-10+deb11u7—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
squid5.7-2 ... 5.7-2+deb12u5 (6 versions)5.7-2+deb12u6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
squid6.13-2, 6.13-2+deb13u16.13-2+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
squid6.13-2, 7.1-1, 7.2-1, 7.2-2, 7.4-17.5-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:11 UTCEPSS rescore
  18. 2026-09-02 14:01 UTCOSV refresh
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 50 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:17 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 10:12 UTCEG score recompute
  13. 2026-08-16 10:12 UTCVendor advisory
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 06:30 UTCEG score recompute
  17. 2026-08-14 06:30 UTCVendor advisory
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 20:47 UTCEG score recompute
  20. 2026-08-12 20:47 UTCVendor advisory
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 08:25 UTCEG score recompute
  23. 2026-08-11 08:25 UTCVendor advisory
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 07:08 UTCEG score recompute
  26. 2026-08-10 07:08 UTCVendor advisory
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-09 06:03 UTCEG score recompute
  29. 2026-08-09 06:03 UTCVendor advisory
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 16:26 UTCEG score recompute
  32. 2026-08-07 16:26 UTCVendor advisory
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 00:55 UTCEG score recompute
  35. 2026-08-06 00:55 UTCVendor advisory
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 10:38 UTCEPSS rescore
  39. 2026-08-03 23:39 UTCEG score recompute
  40. 2026-08-03 23:39 UTCVendor advisory
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-02 15:26 UTCEG score recompute▼ 0.40
  43. 2026-08-02 15:26 UTCVendor advisory
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-30 16:28 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-27 14:13 UTCEPSS rescore
  49. 2026-07-27 12:50 UTCEG score recompute
  50. 2026-07-27 12:50 UTCVendor advisory

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 37.5% 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).
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33515

Explore →

Is Your Infrastructure Affected by CVE-2026-33515?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs