CVE-2026-47619

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 62% 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 — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

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

NVIDIA Dynamo for Linux examples and recipes contain a vulnerability where an attacker could cause a system failure. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 7, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

product-security/2026/5842 at main · NVIDIA/product-security · GitHub

https://github.com/NVIDIA/product-security/tree/main/2026/5842

Vendor Advisories for CVE-2026-47619(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 24× in last 7d / 98× 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 165 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47619?
CVE-2026-47619 is a high vulnerability published on August 4, 2026. NVIDIA Dynamo for Linux examples and recipes contain a vulnerability where an attacker could cause a system failure. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure.
When was CVE-2026-47619 disclosed?
CVE-2026-47619 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47619 actively exploited?
CVE-2026-47619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47619?
CVE-2026-47619 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-47619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47619, 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-47619

Explore →

Is Your Infrastructure Affected by CVE-2026-47619?

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