Skip to content
Noroxi
CVE-2026-47729· NVD / CVE Program· CNA GitHub_M

Squid: Memory disclosure in FTP gateway

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.

MediumCVSS 6.5 · v3.1—Proof of concept Fix available
Published
Jul 16, 2026
Updated
Jul 19, 2026
EPSS
2.4% · 84th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
squid-cachesquid

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • squid-cache squidbefore 7.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • squid-cache squid

    • < 7.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.23squidbefore 7.6-r07.6-r0
Debian:12squidbefore 5.7-2+deb12u65.7-2+deb12u6
Debian:13squidbefore 6.13-2+deb13u26.13-2+deb13u2
Debian:14squidbefore 7.6-17.6-1

Same product

squid-cache: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-46847Squid: denial of service in http digest authentication
    57Plan
  • CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy
    56Plan
  • CVE-2023-49285Denial of Service in HTTP Message Processing in Squid
    56Plan
  • CVE-2021-31806An issue was discovered in Squid before 4.15 and 5.x before 5.0.6.
    55Plan
  • CVE-2020-8450An issue was discovered in Squid before 4.10.
    51Plan
  • CVE-2024-25111SQUID-2024:1 Denial of Service in HTTP Chunked Decoding
    50Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
squid-cache squid7.6 · descriptionVendor (CNA)
azl3 squid 6.13-4 on Azure Linux 3.06.13-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 squid 6.13-5 on Azure Linux 3.06.13-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:squid7.6-r0 · Alpine:v3.23Package registry (OSV)
debian:squid5.7-2+deb12u6 · Debian:12Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:52026-06-21

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-26 d
  2. Published
  3. TodaySep 30, 2026+76 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-33515113 days apartSquid has issues in ICP message handling
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records