CVE-2026-50012

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 1.4%, top 31% 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
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.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 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.

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

Published

July 16, 2026

Last Modified

July 20, 2026

Advisory Details (4)

Auto-updated Jul 16, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v7.6

Patch available: squid-cache/squid SQUID_7_6

https://github.com/squid-cache/squid/releases/tag/SQUID_7_6
github_commit

commit 19fcfe922717 (squid-cache/squid)

Fix landed in squid-cache/squid commit 19fcfe922717 — awaiting tagged release

https://github.com/squid-cache/squid/commit/19fcfe922717c8b255270c032dcde4071c003bcd
github_pr

Harden peerDigestSwapInMask against invalid cache digest reply

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

https://github.com/squid-cache/squid/pull/2423
github Patch Available

SQUID-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-9284

Vendor 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 12× in last 7d / 22× 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-07-28 15:37 UTCEPSS rescore
  2. 2026-07-28 12:35 UTCEG score recompute
  3. 2026-07-28 12:35 UTCVendor advisory
  4. 2026-07-27 12:00 UTCEG score recompute
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 11:25 UTCEG score recompute
  7. 2026-07-26 11:25 UTCVendor advisory
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:18 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:25 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:35 UTCEG score recompute
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-17 14:14 UTCEG score recompute
  21. 2026-07-16 16:30 UTCEG score recompute
  22. 2026-07-16 16:28 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50012?
CVE-2026-50012 is a medium vulnerability published on July 16, 2026. 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/peerdigest.cc), Squid is vulnerable to a heap-based buffer overflow: a cache digest's on-the-wire size may be larger than the masksize declared…
When was CVE-2026-50012 disclosed?
CVE-2026-50012 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50012 actively exploited?
CVE-2026-50012 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 31.0% of all scored CVEs.
What is the CVSS score of CVE-2026-50012?
CVE-2026-50012 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-50012?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50012, 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-50012

Explore →

Is Your Infrastructure Affected by CVE-2026-50012?

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

Start Free Scan →Browse All CVEs