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 Web Proxy’s FTP gateway and FTP directory-listing parser, reported to date back to legacy NetWare-related parsing logic introduced in 1997. The flaw is triggered when Squid processes a crafted or truncated FTP directory listing from a misbehaving or attacker-controlled FTP server, particularly where the parser encounters a parseable timestamp followed by no filename. Multiple sources in the provided content describe the vulnerable logic as whitespace-skipping code in FtpGateway.cc/ftpListParseParts() that calls strchr() on input without first ensuring the current byte is not the terminating NUL, allowing the parser to advance past the intended buffer boundary and read adjacent heap memory. Because Squid reuses heap buffers without zeroing them, the over-read may disclose remnants of unrelated prior transactions, including cleartext HTTP request material from other users traversing the same proxy.

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 can disclose sensitive data from Squid process memory to the attacker. Reported exposed data includes fragments of other users’ cleartext HTTP requests, HTTP Authorization headers, usernames and passwords, cookies, bearer tokens, API keys, and session tokens. The impact is most serious in shared multi-user proxy deployments because leaked memory may belong to unrelated users or applications using the same Squid instance. Standard HTTPS carried through opaque CONNECT tunnels is generally not exposed, but deployments that proxy cleartext HTTP or terminate/decrypt TLS for inspection may leak decrypted request data. The issue is primarily an information disclosure vulnerability rather than direct code execution, but theft of authentication material can enable account compromise, impersonation, and follow-on access to internal or external services.

Mitigation

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

If immediate patching is not possible, disable Squid’s FTP gateway / FTP support where operationally feasible, as this removes the vulnerable attack surface. Additional mitigations described in the content include blocking outbound FTP from the proxy, removing port 21 from allowed Safe_ports policy where appropriate, restricting which clients may use the proxy, and monitoring for repeated FTP directory-listing requests to unusual or attacker-controlled external FTP servers. Because sensitive material may already have been exposed, rotate potentially leaked credentials, tokens, cookies, and API keys after remediation, especially in shared proxy environments or TLS-inspecting deployments.

Remediation

Patch, then assume compromise.

Upgrade to a Squid release or vendor backport that contains the fix for CVE-2026-47729. The provided content contains conflicting statements about whether the fix first shipped in Squid 7.6 or 7.7, so defenders should verify the actual patch/backport rather than rely solely on version strings. The described fix adds a NUL-terminator guard before the vulnerable strchr() calls in FtpGateway.cc, i.e., logic equivalent to checking *copyFrom before whitespace-skipping. Where distribution packages are used, apply the vendor security update that explicitly addresses CVE-2026-47729. Debian also issued squid updates addressing multiple vulnerabilities, including this CVE, in fixed package versions for supported releases.
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 activity73

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