CVE-2026-47620
CVE-2026-47620 is a medium-severity vulnerability in Nvidia Dynamo with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: Medium (CVSS 3.x base score 6.5)
- EPSS exploit prediction: 0% (17th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Nvidia Dynamo
- Published:
- Last modified:
Description
NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. A successful exploit of this vulnerability might lead to data tampering and denial of service.
Frequently asked questions
- What is CVE-2026-47620?
- NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. A successful exploit of this vulnerability might lead to data tampering and denial of service.
- How severe is CVE-2026-47620?
- CVE-2026-47620 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.
- Is CVE-2026-47620 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-47620?
- CVE-2026-47620 affects Nvidia Dynamo. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-47620?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-47620 published?
- CVE-2026-47620 was published on 2026-08-04 and last updated on 2026-08-07.
References
- https://github.com/NVIDIA/product-security/tree/main/2026/5842
- https://nvd.nist.gov/vuln/detail/CVE-2026-47620
- https://www.cve.org/CVERecord?id=CVE-2026-47620
Affected products (1)
- cpe:2.3:a:nvidia:dynamo:*:*:*:*:*:*:*:*
More vulnerabilities in Nvidia Dynamo
- CVE-2026-24254 — Critical (CVSS 9.8): NVIDIA Dynamo for Linux contains a vulnerability in the multimodal serving topology, where an attacker could cause an…
- CVE-2026-47623 — High (CVSS 8.2): NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. A…
- CVE-2026-24253 — High (CVSS 8.2): NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause an out-of-bounds write. A successful…
- CVE-2026-47618 — High (CVSS 7.5): NVIDIA Dynamo for Linux contains a vulnerability in the Rust multimodal media fetcher where an attacker could cause…
- CVE-2026-47617 — High (CVSS 7.5): NVIDIA Dynamo for Linux contains a vulnerability in the multimodal media fetcher where an attacker may cause…
- CVE-2026-47616 — High (CVSS 7.5): NVIDIA Dynamo for Linux contains a vulnerability in the multimodal media fetcher where an attacker may cause…
All CVEs affecting Nvidia Dynamo →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-64720 — Critical (CVSS 9.8): A race condition was addressed with improved state handling. This issue is fixed in iOS 26.6 and iPadOS 26.6, macOS…