Restricted-component file writes via path traversal
Published Sep 9, 2025 · Updated Feb 26, 2026
Path traversal in NVIDIA NVDebug Tool before 1.7.0 allows attackers to write files into restricted system components. NVIDIA has not disclosed the affected function or path input, but identifies the flaw as CWE-22 path traversal that permits an out-of-bound write. Exploitation requires adjacent access, low privileges, high complexity, and user interaction; successful writes can expose or tamper with data or interrupt service.
Summary
What happened
Path traversal in NVIDIA NVDebug Tool before 1.7.0 allows attackers to write files into restricted system components. NVIDIA has not disclosed the affected function or path input, but identifies the flaw as CWE-22 path traversal that permits an out-of-bound write. Exploitation requires adjacent access, low privileges, high complexity, and user interaction; successful writes can expose or tamper with data or interrupt service.
The record
- CVE
- CVE-2025-23343
- Published
- Sep 9, 2025
- Updated
- Feb 26, 2026
- Vendor
- DPDK Project
- Product
- NVIDIA NVDebug Tool
- Classifications
- CWE-22, CAPEC-126, T1565.001
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions prior to 1.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo