What is the CVSS score of CVE-2025-23343?

CVE-2025-23343 has a CVSS 3.1 base score of 7.6 (High). CVSS vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Nvdebug are affected by CVE-2025-23343?

Organizations using NVIDIA NVDebug tool face notable risk from CVE-2025-23343, a path traversal vulnerability rated CVSS 7.6.

How to fix or mitigate CVE-2025-23343?

Within 30 days: Identify all affected systems and apply vendor patches as part of regular patch cycle. Review file handling controls and restrict upload directories.

Nvdebug CVE-2025-23343

HIGH

Path Traversal (CWE-22)

2025-09-09 psirt@nvidia.com

Denial Of Service Information Disclosure Path Traversal Nvdebug Nvidia

7.6

CVSS 3.1

CVSS VectorNVD

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

Attack Vector

Adjacent

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:11 vuln.today

CVE Published

Sep 09, 2025 - 21:15 nvd

HIGH 7.6

DescriptionNVD

The NVIDIA NVDebug tool contains a vulnerability that may allow an actor to write files to restricted components. A successful exploit of this vulnerability may lead to information disclosure, denial of service, and data tampering.

AnalysisAI

The NVIDIA NVDebug tool contains a vulnerability that may allow an actor to write files to restricted components. Rated high severity (CVSS 7.6). No vendor patch available.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. The NVIDIA NVDebug tool contains a vulnerability that may allow an actor to write files to restricted components. A successful exploit of this vulnerability may lead to information disclosure, denial of service, and data tampering. Affected products include: Nvidia Nvdebug.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.