Skip to main content
VulnerabilityPublished

CVE-2025-33242: NVIDIA HGX and DGX B300 · Hardware Internal or Debug Modes Allow Override of Locks

Affects NVIDIA HGX and DGX B300Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NVIDIAHGX and DGX B300Affected
  • =All versions prior to and including 1.0
Fixed in–

AI-suggested

To mitigate CVE-2025-33242, organizations should implement a multi-layered approach: 1) Restrict and monitor privileged access to NVIDIA HGX and DGX B300 systems, ensuring that only authorized personnel have high-level privileges. 2) Employ network segmentation and strict firewall rules to limit network access to these systems, reducing exposure to remote attackers. 3) Continuously monitor system logs and hardware behavior for anomalies indicative of register tampering or unstable states. 4) Engage with NVIDIA support and subscribe to their security advisories to obtain patches or firmware updates as soon as they become available. 5) Implement hardware attestation and integrity verification mechanisms where possible to detect unauthorized modifications at the MCU level. 6) Conduct regular security audits and penetration testing focused on hardware and firmware components. 7) Prepare incident response plans specifically addressing hardware-level compromises to minimize downtime and data integrity risks. These steps go beyond generic advice by focusing on access control, monitoring, and proactive engagement with the vendor for timely remediation.

Description

NVIDIA B300 MCU contains a vulnerability in the CX8 MCU that could allow a malicious actor to modify unsupported registries, causing a bad state. A successful exploit of this vulnerability might lead to denial of service and data tampering.

References

Community reviews

Loading reviews…