CVE-2024-10838

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.9% (61st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-54131 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An integer underflow during deserialization may allow any unauthenticated user to read out of bounds heap memory. This may result into secret data or pointers revealing the layout of the address space to be included into a deserialized data structure, which may potentially lead to thread crashes or cause denial of service conditions.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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
0.9%
EPSS %ILE
61st
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

March 12, 2025

Last Modified

July 31, 2025

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github_release, github.
Web page

CycloneDDS: Integer Underflow in DDS_Security_Deserialize_ methods may lead to OOB read (#46) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignement/-/issues/46
GitHub advisoryMentions a patch (unverified)

Integer Underflow in DDS_Security_Deserialize_ methods may lead to OOB read · Advisory · eclipse-cyclonedds/cyclonedds · GitHub

https://github.com/eclipse-cyclonedds/cyclonedds/security/advisories/GHSA-6jj6-w25p-jc42
GitHub release Patch Available

0.10.5 (Lettres Dansantes)

Patch available: eclipse-cyclonedds/cyclonedds 0.10.5

https://github.com/eclipse-cyclonedds/cyclonedds/releases/tag/0.10.5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 246 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 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-10838?
CVE-2024-10838 is a critical-severity vulnerability; its CVE record was published on March 12, 2025. An integer underflow during deserialization may allow any unauthenticated user to read out of bounds heap memory. This may result into secret data or pointers revealing the layout of the address space to be included into a deserialized data structure, which may potentially lead to thread crashes or…
When was the CVE record for CVE-2024-10838 published?
The CVE record for CVE-2024-10838 was published on March 12, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 31, 2025; the record at its source may have been updated since.
Is CVE-2024-10838 actively exploited?
CVE-2024-10838 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-10838?
CVE-2024-10838 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-10838?
A fix for CVE-2024-10838 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-10838

Explore →

Is Your Infrastructure Affected by CVE-2024-10838?

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