CVE-2024-1635

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-02-20. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2024-0747 (ENISA EUVD) · GHSA-w6qf-42m7-vh68 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A vulnerability was found in Undertow. This vulnerability impacts a server that supports the wildfly-http-client protocol. Whenever a malicious user opens and closes a connection with the HTTP port of the server and then closes the connection immediately, the server will end with both memory and open file limits exhausted at some point, depending on the amount of memory available. At HTTP upgrade to remoting, the WriteTimeoutStreamSinkConduit leaks connections if RemotingConnection is closed by Remoting ServerConnectionOpenListener. Because the remoting connection originates in Undertow as part of the HTTP upgrade, there is an external layer to the remoting connection. This connection is unaware of the outermost layer when closing the connection during the connection opening procedure. Hence, the Undertow WriteTimeoutStreamSinkConduit is not notified of the closed connection in this scenario. Because WriteTimeoutStreamSinkConduit creates a timeout task, the whole dependency tree leaks via that task, which is added to XNIO WorkerThread. So, the workerThread points to the Undertow conduit, which contains the connections and causes the leak.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
36
EG Risk 36/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation4.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
4.6%
EPSS %ILE
91st
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
4.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 19, 2024

Last Modified

November 4, 2026

Advisory Details (10)

Auto-updated Aug 4, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:3354
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:1866
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:1864
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:1862
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:1861
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2024:1860
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:1677
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2024:1676
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2024:1675
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2024:1674

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-wildfly-elytron-0:1.10.17-1.Final_redhat_00001.1.el7eap2025-06-25redhat
redhateap7-xml-security-0:2.0.10-2.redhat_00002.1.ep7.el72025-04-28redhat
redhatpatch2024-07-25redhat
redhatpatch2024-05-23redhat
redhatrh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el7sso2024-04-16redhat
redhatrh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el8sso2024-04-16redhat
redhatrh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el9sso2024-04-16redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-462024-04-16redhat
redhatundertow2024-04-16redhat
redhateap7-undertow-0:2.2.30-1.SP1_redhat_00001.1.el9eap2024-04-04redhat
redhateap7-undertow-0:2.2.30-1.SP1_redhat_00001.1.el7eap2024-04-04redhat
redhateap7-undertow-0:2.2.30-1.SP1_redhat_00001.1.el8eap2024-04-04redhat
redhatio.undertow/undertow-core:2.2.30.SP1-redhat-000012024-04-04redhat
mavenio.undertow:undertow-core @ 2.3.12.Final (fixes >= 2.3.0.Final, < 2.3.12.Final)—ghsa
mavenio.undertow:undertow-core @ 2.2.31.Final (fixes < 2.2.31.Final)—ghsa

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

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
undertow1.3.11-1 ... 2.3.8-2 (53 versions)
  • every version up to 2.3.18-1: fixed in 2.3.18-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.undertow:undertow-core1.0.0.Alpha1 ... 2.2.9.Final (299 versions)
  • 2.3.0.Final up to 2.3.12.Final: fixed in 2.3.12.Final
  • every version up to 2.2.31.Final: fixed in 2.2.31.Final
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 250 rows on record for this CVE, as 96 entries (4 repeats merged).

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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  2. 2026-11-11 16:34 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  3. 2026-11-11 12:58 UTCEchelonGraph re-scored
  4. 2026-11-11 12:58 UTCVendor advisory
  5. 2026-11-11 12:58 UTCGHSA enrichmentGHSA-w6qf-42m7-vh68 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-10 16:38 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  7. 2026-11-09 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  8. 2026-11-08 16:35 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  9. 2026-11-07 16:35 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  10. 2026-11-06 16:31 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  11. 2026-11-05 16:33 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  12. 2026-11-04 21:26 UTCEchelonGraph re-scored
  13. 2026-11-04 21:26 UTCVendor advisory
  14. 2026-11-04 21:26 UTCGHSA enrichmentGHSA-w6qf-42m7-vh68 · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-04 21:16 UTCEchelonGraph re-scored
  16. 2026-11-04 21:16 UTCVendor advisory
  17. 2026-11-04 21:16 UTCGHSA enrichmentGHSA-w6qf-42m7-vh68 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-04 16:32 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  19. 2026-11-03 16:41 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  20. 2026-11-03 12:04 UTCEchelonGraph re-scored
  21. 2026-11-03 12:04 UTCVendor advisory
  22. 2026-11-03 12:03 UTCGHSA enrichmentGHSA-w6qf-42m7-vh68 · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-11-01 16:31 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  24. 2026-11-01 08:16 UTCEchelonGraph re-scored
  25. 2026-11-01 08:16 UTCGHSA enrichmentGHSA-w6qf-42m7-vh68 · GitHub severity HIGH · GitHub CVSS 7.5
Show 71 more
  1. 2026-10-31 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  2. 2026-10-30 16:31 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  3. 2026-10-29 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  4. 2026-10-28 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  5. 2026-10-27 20:31 UTCEchelonGraph re-scored
  6. 2026-10-27 20:31 UTCVendor advisory
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  9. 2026-10-25 17:20 UTCEchelonGraph re-scored
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  12. 2026-10-23 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  13. 2026-10-22 16:31 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  14. 2026-10-21 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  15. 2026-10-20 20:44 UTCEchelonGraph re-scored
  16. 2026-10-20 20:44 UTCVendor advisory
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  20. 2026-10-18 07:30 UTCEchelonGraph re-scored
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  23. 2026-10-15 16:29 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  26. 2026-10-12 18:04 UTCEchelonGraph re-scored
  27. 2026-10-12 16:31 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  28. 2026-10-11 21:29 UTCEchelonGraph re-scored
  29. 2026-10-11 16:23 UTCEchelonGraph re-scored
  30. 2026-10-11 13:45 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  31. 2026-10-10 19:58 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  32. 2026-10-09 20:05 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  33. 2026-10-08 17:07 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  34. 2026-10-07 23:46 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  35. 2026-10-07 22:25 UTCEchelonGraph re-scored
  36. 2026-10-07 22:25 UTCVendor advisory
  37. 2026-10-07 21:45 UTCEchelonGraph re-scored
  38. 2026-10-07 21:45 UTCVendor advisory
  39. 2026-10-06 15:15 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  40. 2026-10-05 17:41 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  41. 2026-10-03 14:23 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  42. 2026-10-02 04:33 UTCEchelonGraph re-scored
  43. 2026-10-02 04:33 UTCVendor advisory
  44. 2026-10-02 03:32 UTCEchelonGraph re-scored
  45. 2026-10-02 03:32 UTCVendor advisory
  46. 2026-10-01 19:48 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  47. 2026-09-30 16:48 UTCEchelonGraph re-scored
  48. 2026-09-30 15:01 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  49. 2026-09-29 15:17 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  50. 2026-09-28 13:49 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  51. 2026-09-27 13:43 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  52. 2026-09-26 00:23 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  53. 2026-09-25 22:15 UTCOSV refresh
  54. 2026-09-24 14:01 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  55. 2026-09-23 13:46 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  56. 2026-09-22 14:46 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  57. 2026-09-20 20:14 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  58. 2026-09-19 15:40 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  59. 2026-09-18 19:26 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  60. 2026-09-16 14:06 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  61. 2026-09-16 05:11 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  62. 2026-09-15 03:08 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  63. 2026-09-13 16:45 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  64. 2026-09-11 14:51 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  65. 2026-09-11 09:34 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  66. 2026-09-08 21:58 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  67. 2026-09-07 15:59 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  68. 2026-09-06 13:46 UTCEPSS rescoreEPSS 4.6% · 90th percentile
  69. 2026-09-06 13:00 UTCOSV refresh
  70. 2026-09-05 15:26 UTCEPSS rescoreEPSS 4.6% · 91st percentile
  71. 2026-09-04 13:58 UTCEPSS rescoreEPSS 4.6% · 90th percentile

Frequently asked(5)

What is CVE-2024-1635?
CVE-2024-1635 is a high-severity vulnerability; its CVE record was published on February 19, 2024. A vulnerability was found in Undertow. This vulnerability impacts a server that supports the wildfly-http-client protocol. Whenever a malicious user opens and closes a connection with the HTTP port of the server and then closes the connection immediately, the server will end with both memory and…
When was CVE-2024-1635 made public?
CVE-2024-1635 was made public on October 27, 2023: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on February 19, 2024. EchelonGraph's copy of the record carries a last-modified date of November 4, 2026; the record at its source may have been updated since.
Is CVE-2024-1635 actively exploited?
CVE-2024-1635 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.6% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-1635?
CVE-2024-1635 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-1635?
A fix for CVE-2024-1635 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-1635 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1635

Explore →

Is Your Infrastructure Affected by CVE-2024-1635?

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