CVE-2024-1635

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 4.6% (91st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation5% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
4.6%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 19, 2024

Last Modified

October 7, 2026

Advisory Details (10)

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

Affected: Red Hat Enterprise Linux 7.

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

Affected: Red Hat Enterprise Linux 9.

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

Affected: Red Hat Enterprise Linux 8.

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

Affected: Red Hat Enterprise Linux 7.

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

Vendor Advisories for CVE-2024-1635(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

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
redhatundertow2024-04-16redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-462024-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

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 10× in last 7d / 38× 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.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:07 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-07 22:25 UTCEG score recompute
  5. 2026-10-07 22:25 UTCVendor advisory
  6. 2026-10-07 21:45 UTCEG score recompute
  7. 2026-10-07 21:45 UTCVendor advisory
  8. 2026-10-06 15:15 UTCEPSS rescore
  9. 2026-10-05 17:41 UTCEPSS rescore
  10. 2026-10-03 14:23 UTCEPSS rescore
  11. 2026-10-02 04:33 UTCEG score recompute
  12. 2026-10-02 04:33 UTCVendor advisory
  13. 2026-10-02 03:32 UTCEG score recompute
  14. 2026-10-02 03:32 UTCVendor advisory
  15. 2026-10-01 19:48 UTCEPSS rescore
  16. 2026-10-01 19:48 UTCEPSS rescore
  17. 2026-09-30 16:48 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescore
  19. 2026-09-30 15:01 UTCEPSS rescore
  20. 2026-09-29 15:17 UTCEPSS rescore
  21. 2026-09-28 13:49 UTCEPSS rescore
  22. 2026-09-27 13:43 UTCEPSS rescore
  23. 2026-09-26 00:23 UTCEPSS rescore
  24. 2026-09-25 22:15 UTCOSV refresh
  25. 2026-09-24 14:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-24 14:01 UTCEPSS rescore
  2. 2026-09-23 13:46 UTCEPSS rescore
  3. 2026-09-23 13:46 UTCEPSS rescore
  4. 2026-09-22 14:46 UTCEPSS rescore
  5. 2026-09-20 20:14 UTCEPSS rescore
  6. 2026-09-19 15:40 UTCEPSS rescore
  7. 2026-09-18 19:26 UTCEPSS rescore
  8. 2026-09-16 14:06 UTCEPSS rescore
  9. 2026-09-16 05:11 UTCEPSS rescore
  10. 2026-09-15 03:08 UTCEPSS rescore
  11. 2026-09-13 16:45 UTCEPSS rescore
  12. 2026-09-11 14:51 UTCEPSS rescore
  13. 2026-09-11 09:34 UTCEPSS rescore
  14. 2026-09-08 21:58 UTCEPSS rescore
  15. 2026-09-07 15:59 UTCEPSS rescore
  16. 2026-09-06 13:46 UTCEPSS rescore
  17. 2026-09-06 13:00 UTCOSV refresh
  18. 2026-09-05 15:26 UTCEPSS rescore
  19. 2026-09-04 13:58 UTCEPSS rescore
  20. 2026-09-04 05:04 UTCEPSS rescore
  21. 2026-09-02 14:10 UTCEPSS rescore
  22. 2026-09-01 13:52 UTCEPSS rescore
  23. 2026-08-30 19:15 UTCEPSS rescore
  24. 2026-08-30 01:20 UTCEPSS rescore
  25. 2026-08-28 21:39 UTCEPSS rescore
  26. 2026-08-27 14:23 UTCEPSS rescore
  27. 2026-08-26 14:44 UTCEPSS rescore
  28. 2026-08-25 13:47 UTCEPSS rescore
  29. 2026-08-23 00:17 UTCEPSS rescore
  30. 2026-08-21 23:47 UTCEPSS rescore
  31. 2026-08-20 22:53 UTCEPSS rescore
  32. 2026-08-19 23:34 UTCOSV refresh
  33. 2026-08-19 17:02 UTCEPSS rescore
  34. 2026-08-18 13:46 UTCEPSS rescore
  35. 2026-08-17 13:45 UTCEPSS rescore
  36. 2026-08-16 14:54 UTCEPSS rescore
  37. 2026-08-16 02:12 UTCEPSS rescore
  38. 2026-08-15 01:28 UTCEPSS rescore
  39. 2026-08-13 21:58 UTCEPSS rescore
  40. 2026-08-12 13:49 UTCEPSS rescore
  41. 2026-08-11 13:40 UTCEPSS rescore
  42. 2026-08-10 23:58 UTCEPSS rescore
  43. 2026-08-09 13:45 UTCEPSS rescore
  44. 2026-08-09 13:45 UTCEPSS rescore
  45. 2026-08-08 16:35 UTCEPSS rescore
  46. 2026-08-07 16:25 UTCEPSS rescore
  47. 2026-08-06 13:45 UTCEPSS rescore
  48. 2026-08-05 19:15 UTCEPSS rescore
  49. 2026-08-04 18:26 UTCEG score recompute
  50. 2026-08-04 18:26 UTCVendor advisory
  51. 2026-08-04 18:01 UTCEG score recompute
  52. 2026-08-04 18:01 UTCVendor advisory
  53. 2026-08-04 15:08 UTCEPSS rescore
  54. 2026-08-04 10:36 UTCEPSS rescore
  55. 2026-08-04 08:20 UTCEG score recompute
  56. 2026-08-04 08:20 UTCVendor advisory
  57. 2026-08-04 07:32 UTCEG score recompute
  58. 2026-08-04 07:32 UTCVendor advisory
  59. 2026-08-03 10:34 UTCEPSS rescore
  60. 2026-08-02 02:25 UTCEPSS rescore
  61. 2026-08-02 02:25 UTCEPSS rescore
  62. 2026-08-01 12:36 UTCOSV refresh
  63. 2026-08-01 04:14 UTCEPSS rescore
  64. 2026-08-01 04:14 UTCEPSS rescore
  65. 2026-07-30 16:26 UTCEPSS rescore
  66. 2026-07-30 01:29 UTCEPSS rescore
  67. 2026-07-28 15:34 UTCEPSS rescore
  68. 2026-07-27 14:11 UTCEPSS rescore
  69. 2026-07-25 14:16 UTCEPSS rescore
  70. 2026-07-24 14:16 UTCEPSS rescore
  71. 2026-07-23 14:17 UTCEPSS rescore
  72. 2026-07-23 14:17 UTCEPSS rescore
  73. 2026-07-23 02:32 UTCEG score recompute
  74. 2026-07-22 23:19 UTCEG score recompute
  75. 2026-07-22 14:07 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-1635?
CVE-2024-1635 is a high vulnerability 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 disclosed?
CVE-2024-1635 was first published on February 19, 2024, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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.

Book a Demo →Browse All CVEs