Remote code execution via internal shared-memory registration
Published Aug 6, 2025 · Updated Aug 6, 2025
Out-of-bounds write in NVIDIA Triton Inference Server before 25.07 allows remote attackers to execute code through the Python backend. The shared-memory registration API accepts the Python backend's private IPC memory key and lets inference requests write into internal data and control structures. The API requires no authentication, but exploitation is high complexity and depends on obtaining the private key and corrupting suitable structures.
Summary
What happened
Out-of-bounds write in NVIDIA Triton Inference Server before 25.07 allows remote attackers to execute code through the Python backend. The shared-memory registration API accepts the Python backend's private IPC memory key and lets inference requests write into internal data and control structures. The API requires no authentication, but exploitation is high complexity and depends on obtaining the private key and corrupting suitable structures.
The record
- CVE
- CVE-2025-23319
- Published
- Aug 6, 2025
- Updated
- Aug 6, 2025
- Vendor
- DPDK Project
- Product
- Triton Inference Server
- Classifications
- CWE-805, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2025CVE publishedPublication date reported by the CVE source.
- Aug 6, 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 25.07
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