Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
UnratedPublic exploit

Squidbleed

IdentifiersCVE-2026-47729CWE-125

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation results in information disclosure from Squid process memory. The leaked data can include fragments of unrelated users' cleartext HTTP requests, such as HTTP Authorization headers, usernames and passwords, cookies, bearer tokens, API keys, session tokens, internal URLs, and other sensitive request artifacts. The impact is most significant in shared multi-user proxy environments because one authorized proxy user may recover data belonging to other users traversing the same Squid instance. Standard HTTPS carried through opaque CONNECT tunnels is generally not exposed, but cleartext HTTP traffic and TLS-terminating / TLS-inspecting Squid deployments may expose decrypted request contents. The vulnerability does not primarily provide code execution; it provides cross-transaction memory disclosure that can enable credential theft, session hijacking, impersonation, and follow-on compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable Squid's FTP gateway / FTP support entirely if it is not operationally required. Additional mitigations described in the content include blocking outbound FTP from the proxy, removing port 21 from allowed Safe_ports policy where feasible, and restricting the proxy's ability to reach attacker-controlled external FTP servers. Monitor for repeated FTP directory-listing requests or unusual outbound FTP activity from Squid hosts. In higher-risk shared proxy environments, reduce exposure by limiting shared use, minimizing cleartext HTTP, and reviewing TLS interception deployments. Rotate secrets that may have been exposed.

Remediation

Patch, then assume compromise.

Upgrade Squid to a release that contains the fix for CVE-2026-47729 and verify that the patch is actually present in the deployed source/package, due to conflicting references in the provided content about whether the fix landed in 7.6 or 7.7. The fix described in the content adds a NUL-terminator guard before the vulnerable strchr() calls in FtpGateway.cc / ftpListParseParts(). Distribution users should install vendor backports where available and confirm package status with their OS vendor. Debian's advisory indicates fixed squid packages were issued for Debian stable. After patching, organizations should rotate potentially exposed credentials, cookies, API keys, and session tokens that may have traversed the vulnerable proxy.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2026-47729MaturityPoCVerified exploit

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.

0xBlackashDisclosed Jun 21, 2026pythonmarkdownnetworkweb
EXPOSURE SURFACE

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.

VendorProductType
DebianSquidapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity70

Community discussion across Reddit, Mastodon, and other social sources.