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 30% 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
70%
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.

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
squid—7.6-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
squid—7.6-r0—
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.5-1 (6 versions)7.6-1—

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 115 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-08 00:29 UTCEG score recompute
  5. 2026-09-08 00:29 UTCVendor advisory
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-05 20:38 UTCEG score recompute
  9. 2026-09-05 20:38 UTCVendor advisory
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-31 04:30 UTCEG score recompute
  15. 2026-08-31 04:30 UTCVendor advisory
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 03:34 UTCEG score recompute
  18. 2026-08-30 03:34 UTCVendor advisory
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-27 12:29 UTCEG score recompute
  23. 2026-08-27 12:29 UTCVendor advisory
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-26 07:59 UTCEG score recompute
Show 75 more
  1. 2026-08-26 07:59 UTCVendor advisory
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 07:23 UTCEG score recompute
  4. 2026-08-25 07:23 UTCVendor advisory
  5. 2026-08-24 06:48 UTCVendor advisory
  6. 2026-08-23 06:13 UTCEG score recompute
  7. 2026-08-23 06:13 UTCVendor advisory
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 05:38 UTCEG score recompute
  10. 2026-08-22 05:38 UTCVendor advisory
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 05:03 UTCEG score recompute
  13. 2026-08-21 05:03 UTCVendor advisory
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 04:28 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-19 03:53 UTCEG score recompute
  18. 2026-08-19 03:53 UTCVendor advisory
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-18 02:28 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 23:56 UTCEG score recompute
  23. 2026-08-16 23:56 UTCVendor advisory
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 23:21 UTCEG score recompute
  27. 2026-08-15 23:21 UTCVendor advisory
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 22:45 UTCVendor advisory
  30. 2026-08-13 22:10 UTCEG score recompute
  31. 2026-08-13 22:10 UTCVendor advisory
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-12 21:35 UTCEG score recompute
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 21:00 UTCEG score recompute
  36. 2026-08-11 21:00 UTCVendor advisory
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 19:49 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 19:15 UTCEG score recompute
  41. 2026-08-08 19:15 UTCVendor advisory
  42. 2026-08-08 16:37 UTCEPSS rescore
  43. 2026-08-07 18:39 UTCEG score recompute
  44. 2026-08-06 17:57 UTCEG score recompute
  45. 2026-08-06 17:57 UTCVendor advisory
  46. 2026-08-06 13:47 UTCEPSS rescore
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 16:47 UTCEG score recompute
  49. 2026-08-04 16:47 UTCVendor advisory
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:39 UTCEPSS rescore
  52. 2026-08-03 16:12 UTCEG score recompute
  53. 2026-08-03 16:12 UTCVendor advisory
  54. 2026-08-03 10:36 UTCEPSS rescore
  55. 2026-08-02 15:37 UTCEG score recompute
  56. 2026-08-02 15:37 UTCVendor advisory
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 15:02 UTCEG score recompute
  59. 2026-08-01 15:02 UTCVendor advisory
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-31 14:26 UTCEG score recompute
  62. 2026-07-31 14:26 UTCVendor advisory
  63. 2026-07-30 16:28 UTCEPSS rescore
  64. 2026-07-30 13:48 UTCEG score recompute
  65. 2026-07-30 13:48 UTCVendor advisory
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-29 13:10 UTCEG score recompute
  68. 2026-07-29 13:10 UTCVendor advisory
  69. 2026-07-28 15:37 UTCEPSS rescore
  70. 2026-07-28 12:35 UTCEG score recompute
  71. 2026-07-28 12:35 UTCVendor advisory
  72. 2026-07-27 12:00 UTCEG score recompute
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 11:25 UTCEG score recompute
  75. 2026-07-26 11:25 UTCVendor advisory

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 29.8% 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

See which npm, PyPI, Go, and Maven packages are affected by 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