Homepage

Protection Mechanism Failure Affecting tritonserver-backend-vllm-cuda-13.0 package, versions <25.11-r7

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
1.35% (69th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-TRITONSERVERBACKENDVLLMCUDA130-17117974
  • published2 Jun 2026
  • disclosed27 Mar 2026
Report a new vulnerability Found a mistake?

Introduced: 27 Mar 2026

CVE-2026-27893  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

Upgrade Chainguard tritonserver-backend-vllm-cuda-13.0 to version 25.11-r7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tritonserver-backend-vllm-cuda-13.0 package and not the tritonserver-backend-vllm-cuda-13.0 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

vLLM is an inference and serving engine for large language models (LLMs). Starting in version 0.10.1 and prior to version 0.18.0, two model implementation files hardcode trust_remote_code=True when loading sub-components, bypassing the user's explicit --trust-remote-code=False security opt-out. This enables remote code execution via malicious model repositories even when the user has explicitly disabled remote code trust. Version 0.18.0 patches the issue.

References