Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-47729: Squidbleed

Published Jul 16, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS6.5Medium · v3.1
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Squid-Cache
IdentifiersCVE-2026-47729CWE-125 · Out-of-bounds Read

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-47729This 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.0xBlackash · Disclosed Jun 21, 2026 · python · markdown · network · webOperational
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
Squid-CacheSquidapplication
FAQ

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.
Activity feed

Recent activity

115 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+26 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity82Community discussion across Reddit, Mastodon, and other social sources.