CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NMedium (6.5) in squid-cache squid. EPSS 1.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExplain CVE-2026-47729 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-47729?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-47729?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-47729 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-47729 |
| Debian | 13 | squid | 6.13-2+deb13u2 | DEBIAN-CVE-2026-47729 |
| Debian | 14 | squid | 7.6-1 | DEBIAN-CVE-2026-47729 |
| Ubuntu | 22.04:LTS | squid | 5.9-0ubuntu0.22.04.7 | UBUNTU-CVE-2026-47729 USN-8941-1 |
| Ubuntu | 24.04:LTS | squid | 6.14-0ubuntu0.24.04.4 | UBUNTU-CVE-2026-47729 USN-8941-1 |
| Ubuntu | 25.10 | squid | 6.14-0ubuntu0.25.10.4 | UBUNTU-CVE-2026-47729 |
| Ubuntu | 26.04:LTS | squid | 7.2-2ubuntu2.2 | UBUNTU-CVE-2026-47729 |
| Ubuntu | Pro:16.04:LTS | squid3 | 3.5.12-1ubuntu7.16+esm7 | UBUNTU-CVE-2026-47729 USN-8941-1 |
| Ubuntu | Pro:18.04:LTS | squid3 | 3.5.27-1ubuntu1.14+esm6 | UBUNTU-CVE-2026-47729 USN-8941-1 |
| Ubuntu | Pro:20.04:LTS | squid | 4.10-1ubuntu1.13+esm3 | UBUNTU-CVE-2026-47729 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-47729 |
| Azure Linux | 3 | squid | 6.13-5 | AZL-92444 |
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 have a valid account on the Squid proxy and must also control an FTP server reachable from the proxy on port 21. HTTPS traffic handled via CONNECT tunnels (the vast majority of modern web traffic) is opaque to the proxy because the underlying request data is encrypted and Squid does not have access to it. The impact is limited to information disclosure of cleartext HTTP request contents or traffic in TLS-terminating (SSL bump) proxy configurations where Squid decrypts and inspects traffic. FTP protocol usage has declined considerably in most environments since major browsers removed FTP support, further narrowing the practical attack surface. Due to these reasons, this vulnerability has been rated with a moderate severity.
When FTP access is not required, block FTP traffic at the proxy by adding the following settings to the squid.conf configuration file above any custom 'http_access allow' rules:
~~~
acl FTP proto FTP
http_access deny FTP
~~~
When FTP access is required, configure Squid to only allow FTP access to specific and trusted destination domains. See the example below for restricting FTP access to the 'trusted.server.example.com' domain:
~~~
acl FTP proto FTP
acl ftp_allowlist dstdomain .trusted.server.example.com
http_access deny FTP !ftp_allowlist
~~~
| 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-47729.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.