Squidbleed
CVE-2026-47729, dubbed Squidbleed, is an out-of-bounds read / heap buffer over-read in Squid Proxy's FTP gateway and FTP directory-listing parser. The flaw is triggered when Squid processes crafted or truncated FTP directory listings from a misbehaving or attacker-controlled FTP server. Multiple sources in the provided content describe the root cause as improper validation of syntactic correctness of input, specifically whitespace-skipping logic in FtpGateway.cc / ftpListParseParts() that can call strchr() on a NUL terminator without first checking for end-of-string. When a listing contains a parseable timestamp but no filename, the parser can advance past the intended buffer boundary and copy adjacent heap memory into the generated FTP directory listing response. Because Squid reuses heap buffers without zeroing them, the disclosed memory may contain remnants of unrelated prior transactions, including other users' cleartext HTTP request data. The issue affects Squid deployments using the FTP gateway feature; the content indicates fixes were released around Squid 7.6/7.7, with some versioning confusion, so defenders are advised to verify the actual patch/backport rather than rely solely on version labels.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a compact standalone proof-of-concept exploit for CVE-2026-47729 ('Squidbleed'), targeting Squid's FTP handling to trigger an information disclosure condition. The repository contains only two files: a README and a single Python exploit script, making CVE-2026-47729.py the clear entry point. The exploit has two tightly integrated components in one script. First, it starts an attacker-controlled FTP server that emulates enough FTP behavior to satisfy a client: USER/PASS, SYST, PWD, TYPE, EPSV, LIST/NLST, and QUIT. The key malicious behavior is in the LIST/NLST handling, where it sends a crafted truncated directory listing line and closes the data connection, intended to trigger the vulnerable memory over-read behavior in Squid. Second, the script acts as a poller/harvester against a target Squid proxy. It repeatedly opens a TCP connection to the configured proxy (default 127.0.0.1:3128) and sends an HTTP GET request for an ftp:// URL pointing to the attacker FTP server (default ftp://anon:x@127.0.0.1:2222/). It then reads the proxy response body and searches for leaked data embedded in HTML href content. The script URL-decodes the leaked bytes and applies regex extraction for Basic and Bearer tokens. Basic tokens are additionally Base64-decoded and printed as username:password when possible. Operationally, the exploit is multithreaded: one background thread runs the FTP server, multiple worker threads continuously poll the proxy, and a status thread reports polling rate, hit count, and distinct token counts. This is not merely a detector; it actively attempts exploitation and harvests sensitive material from leaked memory. There is no post-exploitation shell or code execution payload—its purpose is credential and token disclosure from a vulnerable Squid instance.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
90 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A heap over-read vulnerability in Squid that can leak cleartext HTTP data; referred to as 'Squidbleed' and notable for affecting long-standing code.
A heap over-read vulnerability in Squid that can leak cleartext HTTP data; referenced as 'Squidbleed'.
Unknown
A vulnerability in Squid proxy deployments that can expose sensitive data from memory, including credentials, cookies, API keys, and session tokens.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.