cve.bz

CVE-2026-47729 squid-cache squid: Out-of-bounds Read

6.5 mediumEPSS 1.5%Fix available

Medium (6.5) in squid-cache squid. EPSS 1.5% 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 validation of syntactic correctness of input in the FTP gateway (src/clients/FtpGateway.cc), Squid is vulnerable to an out-of-bounds read: when a listing entry date in the TypeA or TypeB directory-listing formats is not followed by a filename, parsing was not restricted to the input buffer, so a trusted client accessing a misbehaving FTP server through Squid's gateway feature could read memory from random unrelated transactions. This issue is fixed in version 7.6.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
1.5% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 75th 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-16. 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-125 Out-of-bounds Read
CWE-1289 Improper Validation of Unsafe Equivalence in Input
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-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.

Badge for a README or a site

CVE-2026-47729

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-47729](https://cve.bz/cve/badge/CVE-2026-47729.svg)](https://cve.bz/cve/CVE-2026-47729)

HTML:

<a href="https://cve.bz/cve/CVE-2026-47729"><img src="https://cve.bz/cve/badge/CVE-2026-47729.svg" alt="CVE-2026-47729"></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-47729
Debian13squid6.13-2+deb13u2DEBIAN-CVE-2026-47729
Debian14squid7.6-1DEBIAN-CVE-2026-47729
Ubuntu22.04:LTSsquid5.9-0ubuntu0.22.04.7UBUNTU-CVE-2026-47729 USN-8941-1
Ubuntu24.04:LTSsquid6.14-0ubuntu0.24.04.4UBUNTU-CVE-2026-47729 USN-8941-1
Ubuntu25.10squid6.14-0ubuntu0.25.10.4UBUNTU-CVE-2026-47729
Ubuntu26.04:LTSsquid7.2-2ubuntu2.2UBUNTU-CVE-2026-47729
UbuntuPro:16.04:LTSsquid33.5.12-1ubuntu7.16+esm7UBUNTU-CVE-2026-47729 USN-8941-1
UbuntuPro:18.04:LTSsquid33.5.27-1ubuntu1.14+esm6UBUNTU-CVE-2026-47729 USN-8941-1
UbuntuPro:20.04:LTSsquid4.10-1ubuntu1.13+esm3UBUNTU-CVE-2026-47729 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-47729
Azure Linux3squid6.13-5AZL-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

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

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

~~~

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-47729.

GitHub PoC

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.

Detection rules

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.

  • Emerging Threats Open ET HUNTING FTP (passive) LIST Response NUL Byte After Timestamp sid 2071362
  • Emerging Threats Open ET HUNTING FTP (active) LIST Response NUL Byte After Timestamp sid 2071364

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON