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 63% 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
37%
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 29× in last 7d / 71× 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-08-21 06:22 UTCEG score recompute
  2. 2026-08-21 06:22 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 18:46 UTCGHSA enrichment
  5. 2026-08-20 07:10 UTCGHSA enrichment
  6. 2026-08-19 19:34 UTCEG score recompute
  7. 2026-08-19 19:34 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 07:56 UTCGHSA enrichment
  10. 2026-08-18 20:20 UTCEG score recompute
  11. 2026-08-18 20:20 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 08:41 UTCGHSA enrichment
  14. 2026-08-17 21:05 UTCEG score recompute
  15. 2026-08-17 21:04 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 09:28 UTCGHSA enrichment
  18. 2026-08-16 21:52 UTCEG score recompute
  19. 2026-08-16 21:52 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 10:15 UTCEG score recompute
  22. 2026-08-16 10:15 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 22:40 UTCGHSA enrichment
  25. 2026-08-15 11:04 UTCEG score recompute
Show 46 more
  1. 2026-08-15 11:04 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 23:28 UTCGHSA enrichment
  4. 2026-08-14 11:52 UTCGHSA enrichment
  5. 2026-08-14 00:16 UTCEG score recompute
  6. 2026-08-14 00:16 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 12:39 UTCGHSA enrichment
  9. 2026-08-13 01:03 UTCEG score recompute
  10. 2026-08-13 01:03 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-12 13:27 UTCGHSA enrichment
  13. 2026-08-12 01:50 UTCGHSA enrichment
  14. 2026-08-11 14:14 UTCEG score recompute
  15. 2026-08-11 14:14 UTCGHSA enrichment
  16. 2026-08-11 02:38 UTCEG score recompute
  17. 2026-08-11 02:38 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 15:02 UTCGHSA enrichment
  20. 2026-08-10 03:26 UTCGHSA enrichment
  21. 2026-08-09 15:50 UTCEG score recompute
  22. 2026-08-09 15:50 UTCGHSA enrichment
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 04:14 UTCGHSA enrichment
  25. 2026-08-08 16:38 UTCEG score recompute
  26. 2026-08-08 16:38 UTCGHSA enrichment
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-08 05:01 UTCGHSA enrichment
  29. 2026-08-07 17:25 UTCEG score recompute 1.50
  30. 2026-08-07 17:25 UTCGHSA enrichment
  31. 2026-08-07 17:24 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  32. 2026-08-07 17:02 UTCEG score recompute
  33. 2026-08-07 17:02 UTCGHSA enrichment
  34. 2026-08-06 15:49 UTCEG score recompute
  35. 2026-08-06 15:49 UTCGHSA enrichment
  36. 2026-08-06 13:47 UTCEPSS rescore
  37. 2026-08-05 20:36 UTCEG score recompute
  38. 2026-08-05 20:36 UTCGHSA enrichment
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-04 19:25 UTCEG score recompute
  41. 2026-08-04 19:25 UTCGHSA enrichment
  42. 2026-08-04 18:56 UTCEG score recompute
  43. 2026-08-04 18:56 UTCGHSA enrichment
  44. 2026-08-04 18:24 UTCEG score recompute
  45. 2026-08-04 17:47 UTCEG score recompute
  46. 2026-08-04 17:46 UTCMITRE cvelistV5first tracked

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 62.7% 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.