Squid is a caching proxy for the Web. Prior to 7.6, due to an improper input validation bug in cache digest reply handling (peerDigestSwapInMask in src/peer_digest.cc), Squid is vulnerable to a heap-based buffer overflow: a cache digest's on-the-wire size may be larger than the mask_size declared within the digest, so a trusted peer sending a maliciously crafted reply to a cache_digest request message can trigger the overflow. This attack is limited to Squid instances compiled with the --enable-cache-digests option and configured with cache_peer entries. This issue is fixed in version 7.6.
CVE-2026-50012
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 2.3%, top 19% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EPSS
- 81.1%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 20, 2026
Advisory Details (4)
Auto-updated Jul 16, 2026v7.6
Patch available: squid-cache/squid SQUID_7_6
https://github.com/squid-cache/squid/releases/tag/SQUID_7_6commit 19fcfe922717 (squid-cache/squid)
Fix landed in squid-cache/squid commit 19fcfe922717 — awaiting tagged release
https://github.com/squid-cache/squid/commit/19fcfe922717c8b255270c032dcde4071c003bcdHarden peerDigestSwapInMask against invalid cache digest reply
Upstream fix in progress (PR #2423 · squid-cache/squid, state=closed)
https://github.com/squid-cache/squid/pull/2423SQUID-2026:5 Memory corruption in cache_digest reply handling · Advisory · squid-cache/squid · GitHub
https://github.com/squid-cache/squid/security/advisories/GHSA-5vmx-9x64-9284Vendor Advisories for CVE-2026-50012(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 11× in last 7d / 11× 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-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:35 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 14:14 UTCEG score recompute
- 2026-07-16 16:30 UTCEG score recompute
- 2026-07-16 16:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2005-0116NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2004-2771EG 0.0EPSS 93%NONE
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2003-1569EG 0.0NONE
- CVE-2003-1568EG 0.0NONE
Frequently asked(5)
What is CVE-2026-50012?
When was CVE-2026-50012 disclosed?
Is CVE-2026-50012 actively exploited?
What is the CVSS score of CVE-2026-50012?
How do I remediate CVE-2026-50012?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-50012
Is Your Infrastructure Affected by CVE-2026-50012?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.