What is the CVSS score of EUVD-2025-208976?

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

Which versions of Nvidia are affected by EUVD-2025-208976?

NVIDIA Triton Inference Server contains a critical race condition vulnerability that allows remote attackers to crash the service without authentication, impacting organizations relying on AI/ML…

How to fix or mitigate EUVD-2025-208976?

Within 24 hours: inventory all Triton Inference Server instances, document versions and network exposure, and assess criticality of dependent AI/ML applications. Within 7 days: implement network segmentation to restrict Triton access to trusted internal networks only, enable request rate limiting and connection throttling at network perimeter, and establish monitoring for abnormal connection patterns. Within 30 days: coordinate with NVIDIA for patch availability, evaluate alternative inference server solutions if patch timeline is unacceptable, and conduct load testing of mitigations to validate effectiveness.

Nvidia EUVD-2025-208976

| CVE-2025-33254 HIGH

Race Condition (CWE-362)

2026-03-24 nvidia

GHSA-gf35-gc84-4gf8

Denial Of Service Nvidia Race Condition

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 24, 2026 - 20:31 euvd

EUVD-2025-208976

Analysis Generated

Mar 24, 2026 - 20:31 vuln.today

CVE Published

Mar 24, 2026 - 20:26 nvd

HIGH 7.5

DescriptionCVE.org

NVIDIA Triton Inference Server contains a vulnerability where an attacker may cause internal state corruption. A successful exploit of this vulnerability may lead to a denial of service.

AnalysisAI

NVIDIA Triton Inference Server contains a race condition vulnerability (CWE-362) that allows unauthenticated remote attackers to corrupt internal server state, resulting in a denial of service. The vulnerability affects NVIDIA Triton Inference Server across multiple versions and can be exploited over the network with low attack complexity requiring no privileges or user interaction. With a CVSS score of 7.5 (High) and an EPSS score not provided, this represents a significant availability risk for organizations running AI/ML inference workloads.

Technical ContextAI

NVIDIA Triton Inference Server is an open-source inference serving software that enables deployment of trained AI models from multiple frameworks (TensorFlow, PyTorch, ONNX, etc.) in production environments. The vulnerability stems from CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization, commonly known as a Race Condition), where multiple threads or processes access shared resources without proper locking mechanisms. In the context of Triton, this likely involves race conditions during request handling, model loading/unloading, or shared memory operations that manage inference state. The affected product is identified via CPE as cpe:2.3:a:nvidia:triton_inference_server:*:*:*:*:*:*:*:*, indicating broad version coverage pending specific version details from the vendor advisory.

RemediationAI

Organizations should immediately consult the NVIDIA security bulletin at https://nvidia.custhelp.com/app/answers/detail/a_id/5790 to identify affected versions and obtain the patched release of NVIDIA Triton Inference Server. Apply the vendor-provided security update as soon as possible following standard change management procedures. Until patching can be completed, implement network-level mitigations including restricting access to Triton Server endpoints to trusted IP ranges using firewall rules or network policies, deploying rate limiting to reduce race condition exploitation windows, and monitoring for unusual patterns of concurrent requests or server crashes that may indicate exploitation attempts. Consider placing Triton behind a reverse proxy or API gateway to add additional request filtering and anomaly detection capabilities.