What is the CVSS score of EUVD-2026-52818?

EUVD-2026-52818 has a CVSS 3.1 base score of 8.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H. EPSS exploitation probability: 0.3%.

Which versions of NVIDIA Dynamo are affected by EUVD-2026-52818?

NVIDIA Dynamo for Linux (versions 0 through v1.1.0) contains a remote deserialization vulnerability that allows unauthenticated attackers to disrupt service availability and compromise data integrity…

How to fix or mitigate EUVD-2026-52818?

Within 24 hours, inventory all NVIDIA Dynamo for Linux instances running versions 0 through v1.1.0 across your environment, with priority mapping of systems exposed to untrusted networks or internet connectivity. Within 7 days, implement firewall rules and network segmentation to restrict inbound access to Dynamo services to authorized internal networks only, and deploy intrusion detection monitoring to identify suspicious deserialization payloads or exploitation attempts. Within 30 days, establish contact with NVIDIA to track patch availability, develop a transition plan to patched versions upon release, and maintain continuous security monitoring and logging of Dynamo service activity for indicators of compromise.

NVIDIA Dynamo EUVD-2026-52818

| CVE-2026-47623 HIGH

Deserialization of Untrusted Data (CWE-502)

2026-08-04 nvidia

GHSA-xc2p-88hh-m8f9

Denial Of Service Deserialization Nvidia Dynamo

8.2

CVSS 3.1 · Vendor: nvidia

Severity by source

Vendor (nvidia) PRIMARY

8.2 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

vuln.today AI

8.2 HIGH

Network-reachable deserialization with no authentication required; impact limited to availability crash and minor integrity tampering, no confidentiality exposure.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (nvidia).

CVSS VectorVendor: nvidia

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 04, 2026 - 18:07 vuln.today

CVE Published

Aug 04, 2026 - 17:33 cve.org

HIGH 8.2

DescriptionCVE.org

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.

AnalysisAI

Deserialization of untrusted data in NVIDIA Dynamo for Linux (versions 0 through v1.1.0) exposes unauthenticated remote attackers to denial-of-service conditions and data integrity compromise. The flaw is rooted in CWE-502 - unsafe handling of externally supplied serialized objects - and carries a CVSS 8.2 score driven by a fully unauthenticated, low-complexity network attack vector. No public exploit code and no active exploitation have been identified at time of analysis, but the absence of authentication and configuration prerequisites makes the attack surface broad for any internet-accessible Dynamo deployment.

Technical ContextAI

NVIDIA Dynamo is an AI inference and serving framework for Linux environments, identified by CPE cpe:2.3:a:nvidia:dynamo:*:*:*:*:*:*:*:*. CWE-502 (Deserialization of Untrusted Data) describes a root-cause class where an application deserializes data from an untrusted source without adequate validation - an attacker can craft serialized payloads that, when processed, manipulate the application's object graph to cause crashes or corrupt runtime state. In distributed AI inference stacks like Dynamo, serialization is commonly used for inter-process communication, model metadata exchange, or RPC mechanisms, making deserialization endpoints natural attack surfaces. The CVSS vector (AV:N) confirms the vulnerable deserialization path is reachable over the network.

RemediationAI

The primary remediation is to upgrade NVIDIA Dynamo beyond v1.1.0; the NVIDIA product security advisory at https://github.com/NVIDIA/product-security/tree/main/2026/5842 should be consulted for the exact fixed release version, as a specific patched version number was not included in the available input data. Until a patch is applied, network-level compensating controls should be considered: restrict access to Dynamo's network-accessible endpoints using host-based firewall rules or network ACLs to limit inbound connections to trusted clients only, noting this trade-off reduces availability and usability. If Dynamo is deployed behind an API gateway or load balancer, configure request validation to reject malformed or oversized serialized payloads at the perimeter. Disabling or sandboxing deserialization-heavy features within Dynamo - if the framework permits it - would further reduce exposure, but may impact inference pipeline functionality.