CVE-2026-24163

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

NVIDIA TRT-LLM for any platform contains a vulnerability in RPC testing, where an attacker could cause an unsafe deserialization. A successful exploit of this vulnerability might lead to code execution, denial of service, data tampering, and information disclosure.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic
https://www.cve.org/CVERecord?id=CVE-2026-24163

Vendor Advisories for CVE-2026-24163(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 57× 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 166 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24163?
CVE-2026-24163 is a critical vulnerability published on May 20, 2026. NVIDIA TRT-LLM for any platform contains a vulnerability in RPC testing, where an attacker could cause an unsafe deserialization. A successful exploit of this vulnerability might lead to code execution, denial of service, data tampering, and information disclosure.
When was CVE-2026-24163 disclosed?
CVE-2026-24163 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24163 actively exploited?
CVE-2026-24163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.2% of all scored CVEs.
What is the CVSS score of CVE-2026-24163?
CVE-2026-24163 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-24163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24163, 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

Explore the affected products and dependency analysis for CVE-2026-24163

Explore →

Is Your Infrastructure Affected by CVE-2026-24163?

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

Start Free Scan →Browse All CVEs