CVE-2026-47729: Squidbleed
- Vendor
- Squid-Cache
Squidbleed is a heap out-of-bounds read vulnerability in the FTP gateway of Squid versions before 7.6 without a vendor-backported fix. When a TypeA or TypeB directory-listing entry ends after its date without a filename, a missing NUL-terminator check in whitespace-skipping logic allows the parser to advance beyond the input buffer. A subsequent xstrdup() operation can copy adjacent heap contents into the filename rendered in the gateway response. An authorized proxy client accessing an attacker-controlled FTP server can thereby obtain memory fragments from unrelated transactions handled by the Squid worker.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can disclose other users' cleartext HTTP request data, including Authorization headers, credentials, cookies, session tokens, and API keys. Shared proxy deployments are particularly exposed because reused heap buffers can contain unrelated users' requests. Decrypted traffic in TLS-inspecting deployments may also be exposed; HTTP content carried inside opaque HTTPS CONNECT tunnels is not exposed through this mechanism. The direct impact is confidentiality loss, not remote code execution or a demonstrated integrity or availability compromise.
Mitigation
If you can’t patch tonight, do this now.
Disable FTP gateway access using Squid protocol ACLs and deny rules until patched. Block outbound TCP port 21 from the proxy as an additional control against the described exploitation path, and restrict proxy access to authorized clients. Monitor for repeated FTP directory-listing requests, unusual external FTP destinations, and unexpected outbound FTP connections. Rotate credentials, API keys, cookies, and session tokens that may have been exposed.
Remediation
Patch, then assume compromise.
Upgrade to Squid 7.6 or a later fixed release, or install distribution packages containing the backported fix. Debian trixie provides a fixed package in version 6.13-2+deb13u2. The code fix adds a NUL-terminator guard before strchr() in the FTP listing parser's whitespace-skipping loop. For custom builds or packages with unclear patch provenance, verify that this guard is present rather than relying solely on the upstream version number.
Exploits
1 exploit validated by Mallory's analysis.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-47729 exploited in the wild?
- Yes. As of Nov 13, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-47729?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-47729, the earliest disclosed Jun 21, 2026.
- Is there a patch for CVE-2026-47729?
- Upgrade to Squid 7.6 or a later fixed release, or install distribution packages containing the backported fix. Debian trixie provides a fixed package in version 6.13-2+deb13u2.
- What products are affected by CVE-2026-47729?
- Squid-Cache Squid.
- How severe is CVE-2026-47729?
- CVE-2026-47729 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 1.5% (75th percentile) as of Nov 13, 2026.
Recent activity
115 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.