Unauthenticated memory disclosure via shared-memory key confusion
Published Aug 6, 2025 · Updated Aug 6, 2025
Out-of-bounds read in NVIDIA Triton Inference Server before 25.07 allows remote attackers to disclose memory through a crafted request. The shared-memory registration API accepts the Python backend's private IPC region key as user-owned, enabling inference requests to read beyond intended bounds. No authentication or user interaction is required, but exploitation has high complexity and exposes memory without directly altering data or availability.
Summary
What happened
Out-of-bounds read in NVIDIA Triton Inference Server before 25.07 allows remote attackers to disclose memory through a crafted request. The shared-memory registration API accepts the Python backend's private IPC region key as user-owned, enabling inference requests to read beyond intended bounds. No authentication or user interaction is required, but exploitation has high complexity and exposes memory without directly altering data or availability.
The record
- CVE
- CVE-2025-23334
- Published
- Aug 6, 2025
- Updated
- Aug 6, 2025
- Vendor
- DPDK Project
- Product
- Triton Inference Server
- Classifications
- CWE-125
- 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