High severity · published Oct 27, 2026
CVE-2026-65119
NVIDIA TensorRT-LLM for any platform contains a vulnerability in KvCacheAwareRouter tokenizer loading, where an attacker could cause inclusion of functionality from an untrusted…
New
8.4
CVSS
–
EPSS
No
On KEV
Description
NVIDIA TensorRT-LLM for any platform contains a vulnerability in KvCacheAwareRouter tokenizer loading, where an attacker could cause inclusion of functionality from an untrusted control sphere. A successful exploit might lead to code execution, information disclosure, data tampering, and denial of service.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
TE
TensorRT-LLM · NVIDIA
1.3.0rc24 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-65119
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-65119
github.com
https://github.com/NVIDIA/product-security/tree/main/2026/5883
nvd.nist.gov
https://nvd.nist.gov/vuln/detail/CVE-2026-65119
www.cve.org
https://www.cve.org/CVERecord?id=CVE-2026-65119
More from TensorRT-LLM
9.8
CVE-2026-24163
NVIDIA TRT-LLM for any platform contains a vulnerability in RPC testing, where an attacker could cause an unsafe deserialization
9.8
CVE-2026-24142
NVIDIA TRT-LLM for any platform contains a deserialization vulnerability and unsafe serialized handle
9.8
CVE-2025-33255
NVIDIA TRT-LLM for any platform contains a vulnerability in MPI server, where an attacker could cause an unsafe deserialization
8.4
CVE-2026-24233
NVIDIA TensorRT-LLM for Linux contains a vulnerability in the restricted unpickler used for model weight deserialization, where a local, unauthenticated attacker could cause…
7.8
CVE-2026-47472
NVIDIA TensorRT-LLM contains a vulnerability in its inter-process communication layer where an attacker with local same-user access could cause deserialization