CVE-2025-33190

CVE-2025-33190 is a medium-severity vulnerability in Nvidia Dgx Os with a CVSS 3.x base score of 6.7. 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-787.

Key facts

Description

NVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware where an attacker could cause an out-of-bound write. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, or escalation of privileges.

Frequently asked questions

What is CVE-2025-33190?
NVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware where an attacker could cause an out-of-bound write. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, or escalation of privileges.
How severe is CVE-2025-33190?
CVE-2025-33190 has a CVSS 3.x base score of 6.7, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-33190 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-33190?
CVE-2025-33190 affects Nvidia Dgx Os. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-33190?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-33190 have an EU (EUVD) identifier?
Yes. CVE-2025-33190 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-199619.
When was CVE-2025-33190 published?
CVE-2025-33190 was published on 2025-11-25 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Nvidia Dgx Os

All CVEs affecting Nvidia Dgx Os →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →