Squid is an open source caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to a Collapse of Data into Unsafe Value bug ,Squid may be vulnerable to a Denial of Service attack against HTTP header parsing. This problem allows a remote client or a remote server to perform Denial of Service when sending oversized headers in HTTP messages. In versions of Squid prior to 6.5 this can be achieved if the request_header_max_size or reply_header_max_size settings are unchanged from the default. In Squid version 6.5 and later, the default setting of these parameters is safe. Squid will emit a critical warning in cache.log if the administrator is setting these parameters to unsafe values. Squid will not at this time prevent these settings from being changed to unsafe values. Users are advised to upgrade to version 6.5. There are no known workarounds for this vulnerability. This issue is also tracked as SQUID-2024:2
CVE-2024-25617
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.0 because EPSS predicted 88% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.
Also known asEUVD-2024-22939 (ENISA EUVD)Source: ENISA EUVD
- High exploitation likelihood — EPSS 88%
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 74EG Risk 74/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation88% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 88%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.3 MEDIUM): a likelihood of exploitation, not impact.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 88% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
February 14, 2024
Last Modified
June 25, 2025
Advisory Details (3)
Auto-updated Oct 13, 2026SQUID-2024:2 Denial of Service in HTTP Header parser · Advisory · squid-cache/squid · GitHub
https://github.com/squid-cache/squid/security/advisories/GHSA-h5x6-w8mv-xfprcommit 72a3bbd5e431 (squid-cache/squid)
Fix landed in squid-cache/squid commit 72a3bbd5e431 — awaiting tagged release
https://github.com/squid-cache/squid/commit/72a3bbd5e431597c3fdb56d752bc56b010ba3817Vendor Advisories for CVE-2024-25617(9)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2024:2777Red Hat Product SecurityHigh
Red Hat Security Advisory: squid:4 security update
- RHSA-2024:1833Red Hat Product SecurityHigh
Red Hat Security Advisory: squid security update
- RHSA-2024:1832Red Hat Product SecurityHigh
Red Hat Security Advisory: squid:4 security update
- RHSA-2024:1787Red Hat Product SecurityHigh
Red Hat Security Advisory: squid security update
- RHSA-2024:1375Red Hat Product SecurityHigh
Red Hat Security Advisory: squid:4 security update
- RHSA-2024:1376Red Hat Product SecurityHigh
Red Hat Security Advisory: squid security update
- RHSA-2024:1184Red Hat Product SecurityHigh
Red Hat Security Advisory: squid security update
- RHSA-2024:1066Red Hat Product SecurityHigh
Red Hat Security Advisory: squid:4 security update
- +1 more
Patch Availability(11)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | squidclient (3.5.12-1ubuntu7.16+esm3) @ xenial | 2026-11-01 | ubuntu |
| ubuntu | squidclient (6.1-2ubuntu1.3) @ mantic | 2026-11-01 | ubuntu |
| redhat | squid:4-8020020240313150557.4cda2c84 | 2024-05-09 | redhat |
| redhat | squid-7:5.2-1.el9_0.6 | 2024-04-16 | redhat |
| redhat | squid:4-8040020240312224211.522a0ee4 | 2024-04-16 | redhat |
| redhat | squid-7:3.5.20-17.el7_9.10 | 2024-04-11 | redhat |
| redhat | squid-7:5.5-6.el9_3.8 | 2024-03-19 | redhat |
| redhat | squid:4-8090020240314114525.a75119d5 | 2024-03-19 | redhat |
| redhat | squid-7:5.5-5.el9_2.5 | 2024-03-06 | redhat |
| redhat | squid:4-8060020240227214219.ad008a3a | 2024-03-04 | redhat |
| redhat | squid:4-8080020240227184832.63b34585 | 2024-03-01 | redhat |
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.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| squid | 4.13-10, 4.13-10+deb11u1, 4.13-10+deb11u2 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| squid | 5.7-2 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| squid | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| squid | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 17× in last 7d / 55× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 93 of 145 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 52 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:31 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-11-01 15:34 UTCVendor advisory
- 2026-10-31 17:47 UTCEG score recompute
- 2026-10-31 17:47 UTCVendor advisory
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-30 19:58 UTCEG score recompute
- 2026-10-30 19:58 UTCVendor advisory
- 2026-10-29 22:11 UTCEG score recompute
- 2026-10-29 22:11 UTCVendor advisory
- 2026-10-29 00:24 UTCEG score recompute
- 2026-10-29 00:24 UTCVendor advisory
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-28 02:36 UTCEG score recompute
- 2026-10-28 02:36 UTCVendor advisory
- 2026-10-27 04:44 UTCEG score recompute
- 2026-10-27 04:44 UTCVendor advisory
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-26 02:30 UTCVendor advisory
- 2026-10-25 17:16 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-25 04:43 UTCEG score recompute
- 2026-10-25 04:43 UTCVendor advisory
- 2026-10-24 06:56 UTCEG score recompute
- 2026-10-24 06:56 UTCVendor advisory
- 2026-10-23 09:09 UTCEG score recompute
Show 68 moreShow fewer
- 2026-10-23 09:09 UTCVendor advisory
- 2026-10-22 11:17 UTCEG score recompute
- 2026-10-22 11:17 UTCVendor advisory
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-21 13:29 UTCEG score recompute
- 2026-10-21 13:29 UTCVendor advisory
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-20 15:17 UTCEG score recompute
- 2026-10-20 15:17 UTCVendor advisory
- 2026-10-19 15:46 UTCVendor advisory
- 2026-10-18 17:58 UTCEG score recompute
- 2026-10-18 17:58 UTCVendor advisory
- 2026-10-18 07:24 UTCEG score recompute
- 2026-10-17 20:08 UTCEG score recompute
- 2026-10-17 20:08 UTCVendor advisory
- 2026-10-16 22:18 UTCEG score recompute
- 2026-10-16 22:18 UTCVendor advisory
- 2026-10-15 18:55 UTCEG score recompute
- 2026-10-15 18:55 UTCVendor advisory
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-14 12:40 UTCEG score recompute
- 2026-10-14 12:40 UTCVendor advisory
- 2026-10-13 12:34 UTCEG score recompute
- 2026-10-13 12:34 UTCVendor advisory
- 2026-10-12 14:45 UTCEG score recompute
- 2026-10-12 14:45 UTCVendor advisory
- 2026-10-11 21:24 UTCEG score recompute
- 2026-10-11 16:18 UTCEG score recompute
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-30 19:14 UTCOSV refresh
- 2026-09-30 16:59 UTCEG score recompute
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-09-12 01:53 UTCOSV refresh
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-24 07:28 UTCOSV refresh
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-08-08 04:19 UTCOSV refresh
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-30 01:29 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-25 14:16 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-24 14:16 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-23 02:34 UTCEG score recompute
- 2026-07-22 21:22 UTCEG score recompute▲ 3.70
- 2026-07-22 21:22 UTCVendor advisory
- 2026-07-22 14:07 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-19 02:28 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-15 16:56 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-14 19:40 UTCOSV refresh
- 2026-07-13 06:11 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-06 02:22 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-07-01 15:05 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-06-30 23:21 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-06-28 04:55 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-06-27 03:07 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-06-26 20:37 UTCOSV refresh
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:11:squid
- CVE-2005-0194EG 10.0EPSS p92HIGH
- CVE-2004-0541EG 10.0EPSS p99HIGH
- CVE-2020-15049EG 9.9EPSS p93CRITICAL
- CVE-2025-21311EG 9.8CRITICAL
- CVE-2020-11945EG 9.8EPSS p98CRITICAL
- CVE-2019-12519EG 9.8EPSS p94CRITICAL
- CVE-2019-12524EG 9.8EPSS p90CRITICAL
- CVE-2019-12526EG 9.8EPSS p97CRITICAL
- CVE-2019-12525EG 9.8EPSS p98CRITICAL
- CVE-2025-54574EG 9.3EPSS p98CRITICAL
Same vendor
10 shownredhat:RHSA-2024:1375 · redhat:RHSA-2024:1787 · ubuntu:USN-6857-1
- CVE-2024-25111NVD 8.6EG 8.9EPSS p99HIGH
- CVE-2023-50269NVD 7.5EG 8.3EPSS p99HIGH
- CVE-2023-49285NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2023-49286EG 7.5EPSS p96HIGH
- CVE-2022-41318EG 8.6HIGH
- CVE-2024-23638NVD 6.5EG 7.9EPSS p99HIGH
- CVE-2023-49288EG 7.5EPSS p92HIGH
- CVE-2023-46728EG 7.5EPSS p93HIGH
- CVE-2023-5824EG 7.5HIGH
- CVE-2023-46724EG 7.5EPSS p91HIGH
Frequently asked(5)
What is CVE-2024-25617?
When was the CVE record for CVE-2024-25617 published?
Is CVE-2024-25617 actively exploited?
What is the CVSS score of CVE-2024-25617?
How do I remediate CVE-2024-25617?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-25617
Is Your Infrastructure Affected by CVE-2024-25617?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.