CVE-2026-50012: Squid: Memory corruption in cache_digest reply handling

Published Jun 12, 2026
·
Updated

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 within the digest, so a trusted peer sending a maliciously crafted reply to a cachedigest request message can trigger the overflow. This attack is limited to Squid instances compiled with the --enable-cache-digests option and configured with cachepeer entries. This issue is fixed in version 7.6.

Other sources

Squid: Memory corruption in cachedigest reply handling

Microsoft

Affected Software

3 affected componentsFixes available
Squid Squid<7.6
Squid-Cache Squid<7.6
Microsoft azl3 squid 6.13-4<6.13-5
6.13-5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.13-5
  2. Upgrade

    Upgrade squid to a version that resolves this vulnerability.

    Fixed in 7.6
  3. Compensating control

    If you cannot upgrade immediately, limit or remove trust for cache peers configured with cache_peer entries, because exploitation requires Squid instances that are compiled with --enable-cache-digests and configured with cache_peer.

Event History

Jul 16, 2026
CVE Published
via MITRE·04:11 PM
Data Sourced
via MITRE·04:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 18, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-50012?

The severity of CVE-2026-50012 is classified as high due to its potential to allow unauthorized access.

2

How do I fix CVE-2026-50012?

To mitigate CVE-2026-50012, update your Squid installation to the latest version that includes the security patch.

3

What systems are affected by CVE-2026-50012?

CVE-2026-50012 affects all versions of Squid prior to the patched release.

4

What types of attacks can exploit CVE-2026-50012?

CVE-2026-50012 can be exploited to launch unauthorized actions against the Squid server due to improper access controls.

5

Is there a workaround for CVE-2026-50012 if I cannot update?

As a temporary workaround for CVE-2026-50012, you can restrict access by modifying the Squid configuration to limit user permissions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203