CVSS 3.1
5.5 mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:HMedium (5.5) in squid-cache squid. EPSS 1.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:HExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| squid-cache:squid | before 7.6 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | squid | 5.7-2+deb12u6 | DEBIAN-CVE-2026-50012 |
| Debian | 13 | squid | 6.13-2+deb13u2 | DEBIAN-CVE-2026-50012 |
| Debian | 14 | squid | 7.6-1 | DEBIAN-CVE-2026-50012 |
| Ubuntu | 22.04:LTS | squid | 5.9-0ubuntu0.22.04.7 | UBUNTU-CVE-2026-50012 USN-8941-1 |
| Ubuntu | 24.04:LTS | squid | 6.14-0ubuntu0.24.04.4 | UBUNTU-CVE-2026-50012 USN-8941-1 |
| Ubuntu | 25.10 | squid | 6.14-0ubuntu0.25.10.4 | UBUNTU-CVE-2026-50012 |
| Ubuntu | 26.04:LTS | squid | 7.2-2ubuntu2.2 | UBUNTU-CVE-2026-50012 |
| Ubuntu | Pro:16.04:LTS | squid3 | 3.5.12-1ubuntu7.16+esm7 | UBUNTU-CVE-2026-50012 USN-8941-1 |
| Ubuntu | Pro:18.04:LTS | squid3 | 3.5.27-1ubuntu1.14+esm6 | UBUNTU-CVE-2026-50012 USN-8941-1 |
| Ubuntu | Pro:20.04:LTS | squid | 4.10-1ubuntu1.13+esm3 | UBUNTU-CVE-2026-50012 USN-8941-1 |
| SUSE | Linux 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 more | squid | 5.7-150400.3.41.1 | SUSE-SU-2026:4909-1 |
| SUSE | Linux Enterprise Module for Server Applications 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6 | squid | 6.14-150600.3.20.1 | SUSE-SU-2026:4621-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | squid | 6.14-160000.1.1 | SUSE-SU-2026:24224-1 |
| openSUSE | Leap 16.0 | squid | 6.14-160000.1.1 | openSUSE-SU-2026:22080-1 |
| openSUSE | Tumbleweed | squid | 7.7-2.1 | openSUSE-SU-2026:11937-1 |
| Alpine | v3.23, v3.24 | squid | 7.6-r0 | ALPINE-CVE-2026-50012 |
| Azure Linux | 3 | squid | 6.13-5 | AZL-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 rates this Moderate.
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.
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
~~~
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | squid | Fix deferred | |
| Red Hat Enterprise Linux 6 | squid | Fix deferred | |
| Red Hat Enterprise Linux 6 | squid34 | Fix deferred | |
| Red Hat Enterprise Linux 7 | squid | Fix deferred | |
| Red Hat Enterprise Linux 8 | squid | Fix deferred | |
| Red Hat Enterprise Linux 8 | squid:4/squid | Fix deferred | |
| Red Hat Enterprise Linux 9 | squid | Fix 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.
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).