NVIDIA HGX/DGX B300 CX8 MCU hardware internal or debug modes allow override of locks
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in NVIDIA HGX and DGX B300. Impacted is an unknown function of the component CX8 MCU. This manipulation causes hardware internal or debug modes allow override of locks. This vulnerability is registered as CVE-2025-33242. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in NVIDIA HGX and DGX B300 (affected version unknown) and classified as problematic. Affected by this vulnerability is an unknown functionality of the component CX8 MCU. The manipulation with an unknown input leads to a hardware internal or debug modes allow override of locks vulnerability. The CWE definition for the vulnerability is CWE-1234. System configuration protection may be bypassed during debug mode. As an impact it is known to affect integrity, and availability. The summary by CVE is:
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.
This vulnerability is known as CVE-2025-33242 since 04/15/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation requires an enhanced level of successful authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/04/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1342). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Dell PowerEdge
Product
Vendor
Name
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (nvidia): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hardware internal or debug modes allow override of locksCWE: CWE-1234 / CWE-489
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/15/2025 CVE reserved03/25/2026 Advisory disclosed
03/25/2026 VulDB entry created
05/04/2026 VulDB entry last update
Sources
Vendor: nvidia.comStatus: Not defined
CVE: CVE-2025-33242 (🔒)
GCVE (CVE): GCVE-0-2025-33242
GCVE (VulDB): GCVE-100-352885
CERT Bund: WID-SEC-2026-1342 - Dell PowerEdge: Schwachstelle ermöglicht Manipulation von Daten und Denial of Service
Entry
Created: 03/25/2026 07:21Updated: 05/04/2026 12:54
Changes: 03/25/2026 07:21 (59), 03/29/2026 11:35 (1), 05/04/2026 12:54 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.