NVIDIA Corp. NVIDIA Triton Inference Server

Name: NVIDIA Corp. NVIDIA Triton Inference Server
Brand: NVIDIA Corp.

productRU

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

KEV-listed

EPSS ≥ 10%

by severity

4critical6high3medium0low

updated 2026-10-27

vulnerabilities (37)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2025-23320US	—	1.00% (63rd)	Exploit	no fix	2025-08-06	≤ 25.07
CVE-2025-23311US	—	2.71% (86th)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-23317US	critical9.8	2.25% (83rd)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-23310US	—	1.89% (79th)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-23319US	critical9.8	1.61% (76th)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-33201US	—	0.94% (61st)	—	no fix	2025-12-03	≤ 25.10
CVE-2023-31036US	high8.8	0.85% (58th)	—	no fix	2024-01-12	≤ 2.40
CVE-2025-23318US	critical9.8	0.80% (56th)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-23334US	high7.5	0.78% (56th)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-23316US	—	0.71% (53rd)	—	no fix	2025-09-17	≤ 25.08
CVE-2025-33211US	—	0.68% (52nd)	—	no fix	2025-12-03	≤ 25.10
CVE-2025-23331US	—	0.65% (51st)	—	no fix	2025-08-06	≤ 25.06
CVE-2025-23322US	—	0.61% (49th)	—	no fix	2025-08-06	≤ 25.06
CVE-2025-23323US	—	0.59% (48th)	—	no fix	2025-08-06	≤ 25.05
CVE-2025-23327US	critical9.1	0.57% (47th)	—	no fix	2025-08-06	≤ 25.05
CVE-2025-23333US	high7.5	0.56% (46th)	—	no fix	2025-08-06	≤ 25.07
CVE-2025-23335US	high7.5	0.55% (46th)	—	no fix	2025-08-06	≤ 25.05
CVE-2024-0095US	high7.2	0.54% (45th)	—	no fix	2024-06-13	20.10 → 24.05
CVE-2025-23321US	—	0.53% (45th)	—	no fix	2025-08-06	≤ 25.07
CVE-2026-24146US	—	0.53% (45th)	—	no fix	2026-04-07	≤ 26.02
CVE-2025-23326US	—	0.52% (44th)	—	no fix	2025-08-06	≤ 25.05
CVE-2025-23325US	—	0.52% (44th)	—	no fix	2025-08-06	≤ 25.05
CVE-2025-23324US	—	0.52% (44th)	—	no fix	2025-08-06	≤ 25.05
CVE-2026-24174US	—	0.52% (44th)	—	no fix	2026-04-07	≤ r26.02
CVE-2026-24173US	—	0.52% (44th)	—	no fix	2026-04-07	≤ r26.02
CVE-2024-53880US	medium6.5	0.50% (43rd)	—	no fix	2025-02-12	≤ 24.11
CVE-2026-24147US	—	0.48% (41st)	—	no fix	2026-04-07	≤ 26.02
CVE-2026-24175US	—	0.47% (41st)	—	no fix	2026-04-07	≤ r26.02
CVE-2025-33202US	—	0.47% (40th)	—	no fix	2025-11-11	≤ 25.09
CVE-2024-0116US	medium6.5	0.47% (40th)	—	no fix	2024-10-01	19.11 → 24.08
CVE-2026-24158US	—	0.41% (35th)	—	no fix	2026-03-24	≤ 26.01
CVE-2025-23328US	—	0.38% (32nd)	—	no fix	2025-09-17	≤ 25.08
CVE-2025-23329US	—	0.35% (29th)	—	no fix	2025-09-17	≤ 25.08
CVE-2025-23336US	high7.5	0.35% (28th)	—	no fix	2025-09-17	≤ 25.08
CVE-2025-33254US	—	0.33% (26th)	—	no fix	2026-03-24	≤ 26.01
CVE-2025-33238US	—	0.33% (26th)	—	no fix	2026-03-24	≤ 26.01
CVE-2024-0103US	medium6.5	0.28% (20th)	—	no fix	2024-06-13	23.10 → 24.05

weaknesses (8)

The flaw types (CWEs) most of these CVEs share.

CWE-190Integer Overflow or Wraparound5 CVEs
CWE-787Out-of-bounds Write4 CVEs
CWE-121Stack-based Buffer Overflow3 CVEs
CWE-125Out-of-bounds Read3 CVEs
CWE-789Memory Allocation with Excessive Size Value3 CVEs
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')2 CVEs
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')2 CVEs
CWE-805Buffer Access with Incorrect Length Value2 CVEs

sources (1)

Which sources assert this record, and when.

RUBDU (FSTEC Data Security Threats Database)37 CVEs

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.

Free scan