cve.bz

CVE-2026-50012 squid-cache squid: Heap-based Buffer Overflow

5.5 mediumEPSS 1.4%Fix available

Medium (5.5) in squid-cache squid. EPSS 1.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 72nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-122 Heap-based Buffer Overflow
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-50012 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50012?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50012?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50012 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-50012

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-50012](https://cve.bz/cve/badge/CVE-2026-50012.svg)](https://cve.bz/cve/CVE-2026-50012)

HTML:

<a href="https://cve.bz/cve/CVE-2026-50012"><img src="https://cve.bz/cve/badge/CVE-2026-50012.svg" alt="CVE-2026-50012"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
squid-cache:squidbefore 7.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12squid5.7-2+deb12u6DEBIAN-CVE-2026-50012
Debian13squid6.13-2+deb13u2DEBIAN-CVE-2026-50012
Debian14squid7.6-1DEBIAN-CVE-2026-50012
Ubuntu22.04:LTSsquid5.9-0ubuntu0.22.04.7UBUNTU-CVE-2026-50012 USN-8941-1
Ubuntu24.04:LTSsquid6.14-0ubuntu0.24.04.4UBUNTU-CVE-2026-50012 USN-8941-1
Ubuntu25.10squid6.14-0ubuntu0.25.10.4UBUNTU-CVE-2026-50012
Ubuntu26.04:LTSsquid7.2-2ubuntu2.2UBUNTU-CVE-2026-50012
UbuntuPro:16.04:LTSsquid33.5.12-1ubuntu7.16+esm7UBUNTU-CVE-2026-50012 USN-8941-1
UbuntuPro:18.04:LTSsquid33.5.27-1ubuntu1.14+esm6UBUNTU-CVE-2026-50012 USN-8941-1
UbuntuPro:20.04:LTSsquid4.10-1ubuntu1.13+esm3UBUNTU-CVE-2026-50012 USN-8941-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 5 moresquid5.7-150400.3.41.1SUSE-SU-2026:4909-1
SUSELinux Enterprise Module for Server Applications 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6squid6.14-150600.3.20.1SUSE-SU-2026:4621-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0squid6.14-160000.1.1SUSE-SU-2026:24224-1
openSUSELeap 16.0squid6.14-160000.1.1openSUSE-SU-2026:22080-1
openSUSETumbleweedsquid7.7-2.1openSUSE-SU-2026:11937-1
Alpinev3.23, v3.24squid7.6-r0ALPINE-CVE-2026-50012
Azure Linux3squid6.13-5AZL-92447

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

To exploit this issue, an attacker must control a trusted cache peer server. Also, cache digests are not enabled in the default configuration. Squid deployments that do not use cache peering are not affected. Furthermore, even those that do are only vulnerable when the attacker controls a configured peer server within the same administrative domain. A compromised peer can reliably crash the Squid process via a heap-based buffer overflow during digest exchange, but code execution faces considerable practical security barriers.

Default Red Hat Enterprise Linux security features, including SELinux enforcement, Address Space Layout Randomization (ASLR) and NX (No-Execute) stack protection, significantly increase the difficulty of achieving arbitrary code execution, limiting the impact of this vulnerability.

Due to these reasons, this vulnerability has been rated with a moderate severity.

Red Hat's mitigation

To mitigate this vulnerability, restrict or disable cache digest processing for cache peers by adding the appropriate settings to the squid.conf configuration file:

Disable cache digests for any cache_peer not under direct control by adding the no-digest option. This completely removes the vulnerability for those peers at the cost of increased bandwidth. Use of HTCP or ICP as alternative protocols can reduce that cost.

~~~

# Example of disabling digests for an untrusted peer.

cache_peer untrusted.server.example.com parent 3128 3130 no-digest

~~~

Audit the Squid configuration and ensure that all configured cache_peer entries are under direct control and are trusted. Restricting cache peering exclusively to trusted domains greatly reduces the risk of exploitation.

~~~

# Example of a fully trusted peer without the no-digest flag.

cache_peer trusted.internal.example.com parent 3128 3130

~~~

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10squidFix deferred
Red Hat Enterprise Linux 6squidFix deferred
Red Hat Enterprise Linux 6squid34Fix deferred
Red Hat Enterprise Linux 7squidFix deferred
Red Hat Enterprise Linux 8squidFix deferred
Red Hat Enterprise Linux 8squid:4/squidFix deferred
Red Hat Enterprise Linux 9squidFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-50012.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON