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.5%, top 27% 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)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 2%
- EPSS %ILE
- 73%
- 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.
Affected Packages
(6 across 6 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| squid | — | 7.6-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| squid | — | 7.6-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| squid | 4.13-10 ... 4.13-10+deb11u6 (7 versions) | 4.13-10+deb11u7 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| squid | 5.7-2 ... 5.7-2+deb12u5 (6 versions) | 5.7-2+deb12u6 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| squid | 6.13-2, 6.13-2+deb13u1 | 6.13-2+deb13u2 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| squid | 6.13-2 ... 7.5-1 (6 versions) | 7.6-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 59× 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.
Showing the most recent 100 of 115 total refreshes for this CVE.
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 00:29 UTCEG score recompute
- 2026-09-08 00:29 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 20:38 UTCEG score recompute
- 2026-09-05 20:38 UTCVendor advisory
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-31 03:42 UTCEG score recompute
- 2026-08-31 03:42 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 03:34 UTCEG score recompute
- 2026-08-30 03:34 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 23:53 UTCEG score recompute
- 2026-08-27 23:53 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 23:48 UTCEG score recompute
- 2026-08-26 23:48 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-25 23:51 UTCEG score recompute
- 2026-08-25 23:51 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 23:38 UTCEG score recompute
- 2026-08-24 23:38 UTCVendor advisory
- 2026-08-23 23:41 UTCEG score recompute
- 2026-08-23 23:41 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 23:45 UTCEG score recompute
- 2026-08-22 23:45 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 23:48 UTCVendor advisory
- 2026-08-20 23:52 UTCEG score recompute
- 2026-08-20 23:52 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 23:55 UTCEG score recompute
- 2026-08-19 23:55 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:56 UTCEG score recompute
- 2026-08-18 19:56 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:19 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:23 UTCEG score recompute
- 2026-08-16 14:23 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 14:27 UTCEG score recompute
- 2026-08-15 14:27 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 14:30 UTCEG score recompute
- 2026-08-14 14:30 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 14:33 UTCVendor advisory
- 2026-08-12 14:37 UTCEG score recompute
- 2026-08-12 14:37 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 14:40 UTCEG score recompute
- 2026-08-11 14:40 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 14:47 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 14:51 UTCEG score recompute
- 2026-08-08 14:51 UTCVendor advisory
- 2026-08-06 14:58 UTCEG score recompute
- 2026-08-06 14:58 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 15:01 UTCEG score recompute
- 2026-08-05 15:01 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 13:01 UTCEG score recompute
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 11:58 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 11:11 UTCEG score recompute
- 2026-08-02 11:11 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 11:14 UTCEG score recompute
- 2026-08-01 11:14 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 11:17 UTCEG score recompute
- 2026-07-31 11:17 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 11:21 UTCEG score recompute
- 2026-07-30 11:21 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 11:22 UTCEG score recompute
- 2026-07-29 11:22 UTCVendor advisory
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 11:25 UTCEG score recompute
- 2026-07-28 11:25 UTCVendor advisory
- 2026-07-27 11:24 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
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 ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
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
See which npm, PyPI, Go, and Maven packages are affected by 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.