NVIDIA Triton Inference Server: A malformed request header crashes the server before the body is even parsed

Impact

A malformed request header crashes the server before the body is even parsed. On a shared inference tier this is a noisy-neighbour weapon: one tenant's request kills the server process and takes every co-resident model with it, and the GPU sits idle until the pod restarts.

Who can reach it

Network. Anyone who can reach the Triton HTTP or gRPC endpoint. In most clusters that is anything on the pod network; where ingress is loosely scoped it is the internet. No authentication step exists in Triton itself to stop it.

What to do

Roll to the fixed Triton container image per bulletin 5816. Cost: an ordinary rolling deployment restart - no driver, firmware or node change. Worth pairing with an audit of Triton endpoint exposure, since almost every bug in this component is only interesting because the endpoint is reachable.

References

Related entries

• NVIDIA Triton Inference Server: Allocation of resources without limits lets an unauthenticated caller exhaustCVE-2026-47628 · NVIDIA Triton Inference ServerHigh
• NVIDIA Triton Inference Server: Improper input validation crashes the serverCVE-2026-47629 · NVIDIA Triton Inference ServerHigh
• NVIDIA Triton Inference Server: An absolute path traversal reaches code execution and information disclosureCVE-2026-47606 · NVIDIA Triton Inference ServerMedium
• NVIDIA Triton Inference Server: Manipulating the Python backend's shared memory region produces an out-of-bounds readCVE-2025-23333 · NVIDIA Triton Inference ServerMedium
• NVIDIA Triton Inference Server: A crafted request causes an out-of-bounds read in the Python backend, disclosing memoryCVE-2025-23334 · NVIDIA Triton Inference ServerMedium
• NVIDIA Triton Inference Server: An absolute path traversal reachable from a local low-privileged account reaches codeCVE-2026-47630 · NVIDIA Triton Inference ServerMedium