CVE-2005-0095

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS: 69%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

The WCCP message parsing code in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial of service (crash) via malformed WCCP messages with source addresses that are spoofed to reference Squid's home router and invalid WCCP_I_SEE_YOU cache numbers.

CVSS v3
—
EG Score
0.0(none)
EPSS
99.3%
KEV
Not listed

Published

January 15, 2005

Last Modified

June 16, 2026

References (32)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusquid () @ warty2026-05-31ubuntu
redhatsquid-7:2.5.STABLE6-3.4E.32005-02-15redhat
redhatsquid-7:2.5.STABLE3-6.3E.72005-02-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:24 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-11 08:22 UTCEPSS rescore
  4. 2026-07-09 06:45 UTCOSV refresh
  5. 2026-07-02 14:00 UTCEPSS rescore
  6. 2026-06-27 03:04 UTCEPSS rescore
  7. 2026-06-25 13:46 UTCEPSS rescore
  8. 2026-06-24 14:01 UTCEPSS rescore
  9. 2026-06-23 21:29 UTCEPSS rescore
  10. 2026-06-20 19:12 UTCOSV refresh
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-17 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-16 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-15 17:44 UTCEPSS rescore
  18. 2026-06-14 23:13 UTCEPSS rescore
  19. 2026-06-14 23:13 UTCEPSS rescore
  20. 2026-06-13 22:56 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-11 13:55 UTCEPSS rescore
  23. 2026-06-10 22:14 UTCEPSS rescore
  24. 2026-06-10 13:17 UTCEPSS rescore
  25. 2026-06-08 14:13 UTCEPSS rescore
Show 29 more
  1. 2026-06-07 15:21 UTCEPSS rescore
  2. 2026-06-06 13:44 UTCEPSS rescore
  3. 2026-06-06 13:44 UTCEPSS rescore
  4. 2026-06-05 22:43 UTCEPSS rescore
  5. 2026-06-05 22:43 UTCEPSS rescore
  6. 2026-06-05 06:07 UTCEPSS rescore
  7. 2026-06-05 06:07 UTCEPSS rescore
  8. 2026-06-04 13:09 UTCEPSS rescore
  9. 2026-06-04 13:09 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-06-01 13:49 UTCEPSS rescore
  12. 2026-05-31 14:26 UTCEG score recompute
  13. 2026-05-31 14:26 UTCVendor advisory
  14. 2026-05-31 14:26 UTCGHSA enrichment
  15. 2026-05-31 00:13 UTCEPSS rescore
  16. 2026-05-31 00:13 UTCEPSS rescore
  17. 2026-05-29 13:40 UTCEPSS rescore
  18. 2026-05-29 13:40 UTCEPSS rescore
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-27 13:37 UTCEPSS rescore
  23. 2026-05-26 07:16 UTCEPSS rescore
  24. 2026-05-26 07:16 UTCEPSS rescore
  25. 2026-05-22 21:15 UTCEPSS rescore
  26. 2026-05-22 21:13 UTCOSV refresh
  27. 2026-05-20 11:20 UTCEPSS rescore
  28. 2026-05-20 11:20 UTCEPSS rescore
  29. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2005-0095?
CVE-2005-0095 is a none vulnerability published on January 15, 2005. The WCCP message parsing code in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial of service (crash) via malformed WCCP messages with source addresses that are spoofed to reference Squid's home router and invalid WCCPISEE_YOU cache numbers.
When was CVE-2005-0095 disclosed?
CVE-2005-0095 was first published in the National Vulnerability Database on January 15, 2005, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-0095 actively exploited?
CVE-2005-0095 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2005-0095?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-0095, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-0095

Explore →

Is Your Infrastructure Affected by CVE-2005-0095?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs