CVE-2024-1635

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 22.7%, top 4% of all CVEs by exploit prediction. 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, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 5%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EPSS
90.5%
KEV
Not listed

Published

February 19, 2024

Last Modified

June 10, 2026

References (15)

Vendor Advisories for CVE-2024-1635(8)

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 / EcosystemFixed in / 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.el9sso2024-04-16redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-462024-04-16redhat
redhatundertow2024-04-16redhat
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
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
redhatio.undertow/undertow-core:2.2.30.SP1-redhat-000012024-04-04redhat
redhateap7-undertow-0:2.2.30-1.SP1_redhat_00001.1.el8eap2024-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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.undertow:undertow-core1.0.0.Alpha1 ... 2.2.9.Final (299 versions)2.2.31.Final—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

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 9× in last 7d / 41× 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-11 08:26 UTCEPSS rescore
  2. 2026-07-09 19:09 UTCEPSS rescore
  3. 2026-07-08 15:13 UTCEPSS rescore
  4. 2026-07-07 13:45 UTCEPSS rescore
  5. 2026-07-07 13:45 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-06 02:22 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-05 02:29 UTCEPSS rescore
  10. 2026-07-04 06:30 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-29 14:05 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-27 03:07 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-26 20:09 UTCOSV refresh
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-24 14:04 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-21 14:55 UTCEPSS rescore
Show 52 more
  1. 2026-06-21 14:55 UTCEPSS rescore
  2. 2026-06-21 01:58 UTCEPSS rescore
  3. 2026-06-21 01:58 UTCEPSS rescore
  4. 2026-06-19 19:24 UTCEPSS rescore
  5. 2026-06-19 19:24 UTCEPSS rescore
  6. 2026-06-18 17:51 UTCEPSS rescore
  7. 2026-06-17 17:52 UTCEPSS rescore
  8. 2026-06-17 17:51 UTCEPSS rescore
  9. 2026-06-16 17:51 UTCEPSS rescore
  10. 2026-06-16 17:51 UTCEPSS rescore
  11. 2026-06-15 17:47 UTCEPSS rescore
  12. 2026-06-14 23:16 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-13 22:59 UTCEPSS rescore
  15. 2026-06-12 23:11 UTCEPSS rescore
  16. 2026-06-12 23:11 UTCEPSS rescore
  17. 2026-06-11 13:59 UTCEPSS rescore
  18. 2026-06-11 13:59 UTCEPSS rescore
  19. 2026-06-10 22:17 UTCEPSS rescore
  20. 2026-06-10 22:17 UTCEPSS rescore
  21. 2026-06-10 13:21 UTCEPSS rescore
  22. 2026-06-10 13:21 UTCEPSS rescore
  23. 2026-06-09 06:00 UTCOSV refresh
  24. 2026-06-08 14:16 UTCEPSS rescore
  25. 2026-06-08 14:16 UTCEPSS rescore
  26. 2026-06-07 15:24 UTCEPSS rescore
  27. 2026-06-07 15:24 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-04 13:11 UTCEPSS rescore
  33. 2026-06-04 13:11 UTCEPSS rescore
  34. 2026-06-04 13:11 UTCEPSS rescore
  35. 2026-06-02 20:12 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-05-31 00:15 UTCEPSS rescore
  40. 2026-05-31 00:15 UTCEPSS rescore
  41. 2026-05-29 13:43 UTCEPSS rescore
  42. 2026-05-28 13:44 UTCEPSS rescore
  43. 2026-05-28 13:44 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-27 13:40 UTCEPSS rescore
  46. 2026-05-26 13:43 UTCEPSS rescore
  47. 2026-05-26 13:43 UTCEPSS rescore
  48. 2026-05-26 07:18 UTCEPSS rescore
  49. 2026-05-26 07:18 UTCEPSS rescore
  50. 2026-05-26 07:18 UTCEPSS rescore
  51. 2026-05-24 08:16 UTCEG score recompute
  52. 2026-05-24 08:16 UTCVendor advisory

Related CVEs(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 in the National Vulnerability Database on February 19, 2024, with the most recent update on June 10, 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 90.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-1635?
CVE-2024-1635 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2024-1635?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-1635, 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

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.

Start Free Scan →Browse All CVEs