VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

squid: vulnerability history, versions and safety

squid is a package in the Debian ecosystem. Vulert records 8 vulnerabilities for it across 5 releases, from Apr 2004 to Nov 2005. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded U8
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

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

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 07 Nov 2005. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 8 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 8 over 1 year · 0 in the last year i
  • Latest disclosure 07 Nov 2005 i
  • Highest CVSS n/a i
  • With no published fix 0 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.

i
Version Vulert vulnerabilities Fix published Details
2.4.6-2woody10 U1 Yes Details →
2.4.6-2woody9 U1 Yes Details →
2.4.6-2woody8 U2 Yes Details →
2.4.6-2woody7 U3 Yes Details →
2.4.6-2woody4 U6 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2004 2
  • 2005 6

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

03 Vulnerabilities

Recorded vulnerabilities for squid

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
ACL Bypass Vulnerability in squid N/A unrated 2.4.6-2woody2 03 Apr 2004
Vulnerability in Squid - Multiple Issues N/A unrated 2.4.6-2woody4 29 Oct 2004
Buffer Overflow and Integer Overflow in Squid N/A unrated 2.4.6-2woody5 20 Jan 2005
Vulnerability in Squid - Several Issues N/A unrated 2.4.6-2woody6 04 Feb 2005
Vulnerability in squid - Missing Input Sanitizing N/A unrated 2.4.6-2woody7 23 Feb 2005

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 8 vulnerabilities for squid in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 8 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does squid have?

8 vulnerabilities are recorded for squid in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 8 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?

0 vulnerabilities were recorded for squid in the last 12 months, and the oldest entry in this database dates to 03 Apr 2004. 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.