VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

squid: vulnerability history, versions and safety

squid is a package in the Debian ecosystem. Vulert records 199 vulnerabilities for it across 31 releases, from Nov -0001 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
199 vulnerabilities recorded U199
i
13 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 12 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all squid vulnerabilities

Vulert verdict on squid i

Updated on 23 Oct 2026

Careful: 13 of the 199 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 199 vulnerabilities on record across 2026 years, 3 in the last year.

What to do: Plan around the 13 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 199 over 2026 years · 3 in the last year i
  • Latest disclosure 12 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 13 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for squid, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 31 of 31 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 3
  • 1999 2
  • 2002 8
  • 2004 12
  • 2005 38
  • 2007 8
  • 2008 2
  • 2009 6
  • 2010 4
  • 2012 2
  • 2013 2
  • 2014 8
  • 2015 6
  • 2016 10
  • 2018 7
  • 2019 18
  • 2020 21
  • 2021 9
  • 2022 5
  • 2023 8
  • 2024 11
  • 2025 7
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 199 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for squid

The 5 most severe of 199 vulnerabilities recorded for this package

Search all 199 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Squid Cache Manager Access Bypass Vulnerability in Squid 4.7 9.8 critical 4.8-1 15 Apr 2020
Heap Buffer Overflow Vulnerability in Squid Package - CVE-2025-54574 9.8 critical No fix published 01 Aug 2025
Critical Elevation of Privilege Vulnerability in Squid Package 9.8 critical No fix published 14 Jan 2025
Heap-Based Buffer Overflow in Squid: CVE-2019-12526 9.8 critical 4.9-1 26 Nov 2019
Access Control Bypass in Squid Proxy Server 9.1 critical 4.9-1 26 Nov 2019

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About squid

Is squid safe to use?

Vulert records 199 vulnerabilities for squid in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 199 not yet rated. 13 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does squid have?

199 vulnerabilities are recorded for squid in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 199 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new squid vulnerabilities disclosed?

3 vulnerabilities were recorded for squid in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of squid are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor squid for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the squid version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.