Inference-process crash via out-of-bounds read
Published Oct 6, 2026 · Updated Oct 6, 2026
Out-of-bounds read in NVIDIA TensorRT 11.1 and earlier allows attackers to crash an inference process through crafted input. The public material reviewed does not identify the affected function or explain which input reaches the invalid memory read. Exposure depends on an application processing attacker-controlled input with the affected TensorRT runtime; no standalone TensorRT network endpoint is established.
Summary
What happened
Out-of-bounds read in NVIDIA TensorRT 11.1 and earlier allows attackers to crash an inference process through crafted input. The public material reviewed does not identify the affected function or explain which input reaches the invalid memory read. Exposure depends on an application processing attacker-controlled input with the affected TensorRT runtime; no standalone TensorRT network endpoint is established.
The record
- CVE
- CVE-2026-65122
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- DPDK Project
- Product
- TensorRT
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 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=0 to 11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started