Synced 17 Sept 2026 15:07 UTC Account
← Squid

Squid vulnerabilities: known CVEs & security history

Squid · Proxy · 5 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Squid release lines — 5 in total. A CVE here doesn't mean your version is affected — check Squid's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Squid CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2023-46847 high 8.6 88% 2023
CVE-2026-33526 high 7.5 9% 2026
CVE-2026-32748 high 7.5 9% 2026
CVE-2026-47729 medium 6.5 2% 2026
CVE-2026-50012 medium 5.5 2% 2026

Is my Squid version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Squid version → · Monitor Squid for new CVEs →

Squid vulnerabilities — frequently asked

How many known vulnerabilities does Squid have?

IsItPatched tracks 5 CVEs for Squid. 0 are critical-severity and 3 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Squid have any actively-exploited vulnerabilities?

None of Squid's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Squid vulnerability?

Among tracked issues, CVE-2023-46847 (HIGH, CVSS 8.6) ranks highest — a Buffer overflow weakness.

Is Squid safe to use?

It depends on the version. The latest supported Squid release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Squid security status · Squid end-of-life · actively-exploited CVEs. Always verify against Squid's advisories — see our disclaimer.