Overview 5 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 2 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
5
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
5
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
20.0%
Working exploit published
1
20.0%
Proof of concept only
3
60.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 1 / year
20131
Not applicable1
Medium1
not blocked1
Working exploit published1
20140
20150
20161
Not applicable1
High1
not blocked1
Proof of concept only1
20170
20181
Not applicable1
Medium1
not blocked1
Proof of concept only1
20190
20200
20210
20220
20230
20240
20251
Not applicable1
Critical1
not blocked1
Exploited1
20261
Not applicable1
Medium1
not blocked1
Proof of concept only1
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-47729 | Medium | 2026-07-16 | Not applicable | Proof of concept only | 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-2025-62168 | Critical | 2025-10-17 | Not applicable | Exploited | Squid is a caching proxy for the Web. In Squid versions prior to 7.2, a failure to redact HTTP authentication credentials in error handling allows information disclosure. The vulnerability allows a script to bypass browser security protections and learn the credentials a trusted client uses to authenticate. This potentially allows a remote client to identify security tokens or credentials used internally by a web application using Squid for backend load balancing. These attacks do not require Squid to be configured with HTTP authentication. The vulnerability is fixed in version 7.2. As a workaround, disable debug information in administrator mailto links generated by Squid by configuring squid.conf with email_err_data off. |
| CVE-2018-19131 | Medium | 2018-11-09 | Not applicable | Proof of concept only | Squid before 4.4 has XSS via a crafted X.509 certificate during HTTP(S) error page generation for certificate errors. |
| CVE-2016-2569 | High | 2016-02-27 | Not applicable | Proof of concept only | Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not properly append data to String objects, which allows remote servers to cause a denial of service (assertion failure and daemon exit) via a long string, as demonstrated by a crafted HTTP Vary header. |
| CVE-2013-4123 | Medium | 2013-09-16 | Not applicable | Working exploit published | client_side_request.cc in Squid 3.2.x before 3.2.13 and 3.3.x before 3.3.8 allows remote attackers to cause a denial of service via a crafted port number in a HTTP Host header. |