How many CVEs have patched _resolve_rust_cli_path?

2 published CVEs changed _resolve_rust_cli_path in vllm-project/vllm, in 2 distinct patches totalling 21 changed lines, between 2026 and 2026.

What is the latest CVE that changed _resolve_rust_cli_path?

CVE-2026-94625 (vLLM through 0.29.0 Resource Exhaustion via Ownerless Mooncake Transfer Placeholders), published 2026-09-21, changed lines 1736 to 1741 of vllm/envs.py.

How does _resolve_rust_cli_path compare to the rest of vllm-project/vllm?

vllm-project/vllm has 83 CVEs with a located fix in total; 2 of them changed _resolve_rust_cli_path.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

vllm-project/vllm

Function

_resolve_rust_cli_path

Name: _resolve_rust_cli_path in vllm-project/vllm: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

vllm/envs.py

Last patched September 21, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

21

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_resolve_rust_cli_path in vllm-project/vllm was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 21 lines in total.

vllm-project/vllm has 83 CVEs with a located fix in total, so 2% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _resolve_rust_cli_path, newest first, with the lines each fix touched.

vLLM through 0.29.0 Resource Exhaustion via Ownerless Mooncake Transfer Placeholders
CVE-2026-94625 · lines 1736–1741 · +6 −0
Medium · CVSS 6.9
EPSS 0.5%2026-09-21
vLLM through 0.29.0 Denial of Service via Unbounded P2P KV Offloading Sessions
CVE-2026-94624 · lines 1677–1691 · +15 −0
High · CVSS 8.7
EPSS 0.6%2026-09-21

Get an alert when the next CVE fix lands in vllm-project/vllm, with the patched functions.

Monitor vllm CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in vllm-project/vllm changed by the most CVE fixes.

validate_xgrammar_grammar4 CVEs · vllm/v1/structured_output/backend_xgrammar.py load_bytes3 CVEs · vllm/multimodal/media/audio.py _resolve_rust_frontend_path3 CVEs · vllm/envs.py load_file3 CVEs · vllm/multimodal/media/audio.py __init__3 CVEs · vllm/model_executor/models/kimi_k25.py _try_resolve_transformers3 CVEs · vllm/model_executor/models/registry.py

All patched functions in vllm-project/vllm

Frequently asked questions

Common questions about CVE fixes to _resolve_rust_cli_path.

How many CVEs have patched _resolve_rust_cli_path?: 2 published CVEs changed _resolve_rust_cli_path in vllm-project/vllm, in 2 distinct patches totalling 21 changed lines, between 2026 and 2026.
What is the latest CVE that changed _resolve_rust_cli_path?: CVE-2026-94625 (vLLM through 0.29.0 Resource Exhaustion via Ownerless Mooncake Transfer Placeholders), published 2026-09-21, changed lines 1736 to 1741 of vllm/envs.py.
How does _resolve_rust_cli_path compare to the rest of vllm-project/vllm?: vllm-project/vllm has 83 CVEs with a located fix in total; 2 of them changed _resolve_rust_cli_path.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track vllm-project/vllm CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing