CVE-2026-47623

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.2EG
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.2Exploit: 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 contains a vulnerability where an attacker could cause deserialization of untrusted data. A successful exploit of this vulnerability might lead to denial of service and data tampering.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
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
generic
https://www.cve.org/CVERecord?id=CVE-2026-47623

Vendor Advisories for CVE-2026-47623(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 26× in last 7d / 65× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:58 UTCGHSA enrichment
  3. 2026-08-20 08:20 UTCGHSA enrichment
  4. 2026-08-19 19:42 UTCEG score recompute
  5. 2026-08-19 19:42 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:04 UTCGHSA enrichment
  8. 2026-08-18 18:26 UTCEG score recompute
  9. 2026-08-18 18:26 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 05:46 UTCGHSA enrichment
  12. 2026-08-17 17:08 UTCEG score recompute
  13. 2026-08-17 17:07 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 04:30 UTCGHSA enrichment
  16. 2026-08-16 15:52 UTCEG score recompute
  17. 2026-08-16 15:52 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 03:14 UTCEG score recompute
  20. 2026-08-16 03:14 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 14:36 UTCGHSA enrichment
  23. 2026-08-15 01:58 UTCEG score recompute
  24. 2026-08-15 01:58 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 40 more
  1. 2026-08-14 13:20 UTCGHSA enrichment
  2. 2026-08-14 00:42 UTCEG score recompute
  3. 2026-08-14 00:42 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 12:04 UTCGHSA enrichment
  6. 2026-08-12 23:26 UTCEG score recompute
  7. 2026-08-12 23:26 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 10:49 UTCGHSA enrichment
  10. 2026-08-11 22:11 UTCEG score recompute
  11. 2026-08-11 22:11 UTCGHSA enrichment
  12. 2026-08-11 09:30 UTCEG score recompute
  13. 2026-08-11 09:30 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 20:52 UTCGHSA enrichment
  16. 2026-08-10 08:13 UTCGHSA enrichment
  17. 2026-08-09 19:35 UTCEG score recompute
  18. 2026-08-09 19:35 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 06:58 UTCGHSA enrichment
  21. 2026-08-08 18:20 UTCEG score recompute
  22. 2026-08-08 18:20 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 05:42 UTCGHSA enrichment
  25. 2026-08-07 17:04 UTCEG score recompute
  26. 2026-08-07 17:04 UTCGHSA enrichment
  27. 2026-08-07 04:27 UTCGHSA enrichment
  28. 2026-08-06 15:49 UTCEG score recompute
  29. 2026-08-06 15:49 UTCGHSA enrichment
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 09:19 UTCGHSA enrichment
  32. 2026-08-05 20:41 UTCEG score recompute
  33. 2026-08-05 20:41 UTCGHSA enrichment
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 08:03 UTCGHSA enrichment
  36. 2026-08-04 19:25 UTCEG score recompute
  37. 2026-08-04 19:25 UTCGHSA enrichment
  38. 2026-08-04 18:21 UTCEG score recompute
  39. 2026-08-04 17:47 UTCEG score recompute
  40. 2026-08-04 17:46 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47623?
CVE-2026-47623 is a high vulnerability published on August 4, 2026. NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. A successful exploit of this vulnerability might lead to denial of service and data tampering.
When was CVE-2026-47623 disclosed?
CVE-2026-47623 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-47623 actively exploited?
CVE-2026-47623 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 68.6% of all scored CVEs.
What is the CVSS score of CVE-2026-47623?
CVE-2026-47623 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-47623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47623, 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-47623

Explore →

Is Your Infrastructure Affected by CVE-2026-47623?

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

Start Free Scan →Browse All CVEs