Squid vulnerabilitiesRanked by how likely they are to be used.
Squid is made by Squid-Cache. We track 106 published vulnerabilities in it, across 318 versions. None of them is on the list of flaws known to be exploited today. If you run Squid, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Squid vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Squid's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Squid flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 96%CVE-2021-31806Medium
An issue was discovered in Squid before 4.15 and 5.x before 5.0.6.
- 88%CVE-2023-46847High
Squid is vulnerable to a Denial of Service, where a remote attacker can perform buffer overflow attack by writing up to 2 MB of arbitrary data to heap memory when Squid is configured to accept HTTP Digest Authentication.
- 88%CVE-2023-49285High
Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more.
- 88%CVE-2024-25617Medium
Squid is an open source caching proxy for the Web supporting HTTP, HTTPS, FTP, and more.
- 80%CVE-2013-4123Medium
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.
- 80%CVE-2016-4553High
client_side.cc in Squid before 3.5.18 and 4.x before 4.0.10 does not properly ignore the Host header when absolute-URI is provided, which allows remote attackers to conduct cache-poisoning attacks via an HTTP request.
- 80%CVE-2021-33620Medium
Squid before 4.15 and 5.x before 5.0.6 allows remote servers to cause a denial of service (affecting availability to all clients) via an HTTP response.
- 78%CVE-2016-4054High
Buffer overflow in Squid 3.x before 3.5.17 and 4.x before 4.0.9 allows remote attackers to execute arbitrary code via crafted Edge Side Includes (ESI) responses.
- 76%CVE-2014-7141Medium
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.
- 74%CVE-2019-13345Medium
The cachemgr.cgi web module of Squid through 4.7 has XSS via the user_name or auth parameter.
Running Squid? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to a memory-management bug, it is vulnerable to a Denial of Service attack (against all clients using the proxy) via HTTP Range request processing.
- Matched to
- Squid on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 106 published vulnerabilities listed under the name Squid, across 318 versions.
None of Squid's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Squid. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.