CVE-2025-23327 is a high severity (CVSS 7.5) integer overflow in NVIDIA Triton Inference Server for Windows and Linux that specially crafted inputs can trigger. The impact is denial of service and data tampering. NVIDIA lists versions prior to 25.05 as affected, so upgrade to 25.05 or later.
What's affected
NVIDIA's August 2025 security bulletin for Triton Inference Server, released on 6 August 2025, lists Windows and Linux with a different fixed release depending on the CVE. For this one, all versions prior to 25.05 are affected and 25.05 is the updated version. This CVE is one of six fixed in release 25.05, together with CVE-2025-23323, CVE-2025-23324, CVE-2025-23325, CVE-2025-23326 and CVE-2025-23335. The vector needs low privileges and high attack complexity.
The same bulletin lists many other Triton CVEs fixed in releases 25.05, 25.06 and 25.07, so a server older than 25.07 is exposed to several issues at once. The bulletin's notes advise production users to follow the Secure Deployment Considerations Guide.
How to check if you're exposed
Find the Triton release you run. Most deployments use NVIDIA's container images, which carry a YY.MM tag.
docker images | grep -i tritonserver
tritonserver --version
Compare the result with the fixed release for your CVE. Then look at how the server is exposed. The bulletin's notes say production users should follow the Secure Deployment Considerations Guide and make sure logging and shared memory APIs are protected for use by authorized users. Check which networks can reach the HTTP and gRPC ports, and whether those management style APIs are open to anyone.
Reading an inventory is faster than checking host by host. Safeguard has a free in-browser dependency scan at gold.safeguard.sh/scan and a Gold directory you can search for any CVE. Reachability analysis helps you see whether a vulnerable component is actually used in your code, so you can fix the exposed ones first.
What to do now
- Upgrade Triton Inference Server to 25.05 or later, using the release on the Triton GitHub releases page.
- Rebuild and redeploy any container image that pins an older tag.
- Follow NVIDIA's Secure Deployment Considerations Guide, and make sure logging and shared memory APIs are limited to authorized users.
- Keep the inference ports on a private network or behind an authenticated gateway.
- Review other Triton CVEs in the same bulletin so one upgrade covers them all.
Why it matters
CWE-190 is integer overflow or wraparound. A calculation, often a size or a count, exceeds the range of its type and wraps to a small value. Later code then trusts that value, which can lead to undersized buffers or wrong bounds.
NVIDIA's description says the outcome might be denial of service and data tampering, and gives no technical trigger. Because 25.05 is older than the newest release, anyone on 25.05 still needs 25.06 and 25.07 for other issues in the same bulletin. The practical advice is to move to the latest Triton release rather than the minimum for one CVE. The KEV flag is false.
Quick check
What fixes CVE-2025-23327?
NVIDIA lists Triton 25.05 as the updated version for this CVE. Versions prior to 25.05 are affected.
Is 25.05 enough?
Not for the whole bulletin. Other issues are fixed in 25.06 and 25.07, so a current release is better.
Sources
Last reviewed: 19 October 2026.
