Adjacent-network privilege escalation and data tampering
Published Nov 4, 2025 · Updated Nov 4, 2025
Communication-channel restriction in NVIDIA Run:ai before 2.22.48 allows remote authenticated users to escalate privileges on adjacent networks. NVIDIA has not published the affected component or the operation that fails to restrict the channel to intended endpoints. Exploitation requires low privileges, high complexity, adjacent-network access, and user interaction; it permits data tampering and limited information disclosure without service interruption.
Summary
What happened
Communication-channel restriction in NVIDIA Run:ai before 2.22.48 allows remote authenticated users to escalate privileges on adjacent networks. NVIDIA has not published the affected component or the operation that fails to restrict the channel to intended endpoints. Exploitation requires low privileges, high complexity, adjacent-network access, and user interaction; it permits data tampering and limited information disclosure without service interruption.
The record
- CVE
- CVE-2025-33176
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- DPDK Project
- Product
- NVIDIA Run:ai
- Classifications
- CWE-923
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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 2.22.48
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