Squid is a caching proxy for the Web. Prior to 7.6, due to an improper validation of syntactic correctness of input in the FTP gateway (src/clients/FtpGateway.cc), Squid is vulnerable to an out-of-bounds read: when a listing entry date in the TypeA or TypeB directory-listing formats is not followed by a filename, parsing was not restricted to the input buffer, so a trusted client accessing a misbehaving FTP server through Squid's gateway feature could read memory from random unrelated transactions. This issue is fixed in version 7.6.
CVE-2026-47729
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.9%, top 23% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 78.1%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 20, 2026
Advisory Details (5)
Auto-updated Jul 16, 2026v7.6
Patch available: squid-cache/squid SQUID_7_6
https://github.com/squid-cache/squid/releases/tag/SQUID_7_6commit 865a131c7d55 (squid-cache/squid)
Fix landed in squid-cache/squid commit 865a131c7d55 — awaiting tagged release
https://github.com/squid-cache/squid/commit/865a131c7d557e68c965043d98c2eccae26deef8Improve parsing of certain FTP directory listing formats (#2408)
Fix merged in squid-cache/squid PR #2409 on 2026-05-17 — awaiting tagged release
https://github.com/squid-cache/squid/pull/2409Improve parsing of certain FTP directory listing formats
Upstream fix in progress (PR #2408 · squid-cache/squid, state=closed)
https://github.com/squid-cache/squid/pull/2408SQUID-2026:4 Memory disclosure in FTP gateway · Advisory · squid-cache/squid · GitHub
https://github.com/squid-cache/squid/security/advisories/GHSA-8c37-pxjq-qwrgVendor Advisories for CVE-2026-47729(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:35 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 16:30 UTCEG score recompute
- 2026-07-16 16:28 UTCMITRE cvelistV5first tracked
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoC0xBlackash/CVE-2026-47729First seen Jun 21, 2026
CVE-2026-47729
Open source ↗
Frequently asked(5)
What is CVE-2026-47729?
When was CVE-2026-47729 disclosed?
Is CVE-2026-47729 actively exploited?
What is the CVSS score of CVE-2026-47729?
How do I remediate CVE-2026-47729?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-47729
Is Your Infrastructure Affected by CVE-2026-47729?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.