Cyber Resilience

CVE-2025-23326

Nvidia Triton Inference Server ≤ 25.05

Published
06 August 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0047 39th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-23326 is a high-severity Integer Overflow to Buffer Overflow (CWE-680) vulnerability in Nvidia Triton Inference Server. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

NVIDIA Triton Inference Server for Windows and Linux contains a vulnerability where an attacker could cause an integer overflow through a specially crafted input. A successful exploit of this vulnerability might lead to denial of service.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-23310Same product: Linux Linux Kernel
CVE-2025-23335Same product: Linux Linux Kernel
CVE-2025-33202Same product: Linux Linux Kernel
CVE-2025-23317Same product: Linux Linux Kernel
CVE-2025-23311Same product: Linux Linux Kernel
CVE-2025-23333Same product: Linux Linux Kernel
CVE-2025-23334Same product: Linux Linux Kernel
CVE-2025-23327Same product: Linux Linux Kernel
CVE-2024-53880Same product: Linux Linux Kernel
CVE-2025-23324Same product: Linux Linux Kernel

Affected Assets

nvidia
triton inference server
≤ 25.05

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and analysis (static, dynamic, fuzzing) finds integer-overflow-to-allocation defects before deployment.

Mandates documented development standards and tools that enforce secure coding rules against unsafe integer arithmetic.

Requires engineering principles such as safe arithmetic and bounds-checked allocation that directly stop integer overflow during memory-size computation.

Validates untrusted size/offset inputs before they reach allocation calculations, structurally blocking the integer overflow path.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent integer-overflow flaws during development, but eliminating only this CWE covers only part of the broad control intent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect integer-overflow-to-buffer-overflow conditions during development.

prevents

Secure development life cycle mandates practices that can catch integer overflows before deployment.

prevents

Application security requirements can specify safe integer handling and bounds checking.

prevents

Secure architecture principles encourage use of safe arithmetic libraries and overflow detection.

prevents

Secure coding standards directly require prevention of integer overflows that lead to buffer overflows.

References