How many CVEs have patched _validate_allowed_token_ids?

1 published CVEs changed _validate_allowed_token_ids in vllm-project/vllm, in 2 distinct patches totalling 33 changed lines, between 2026 and 2026.

What is the latest CVE that changed _validate_allowed_token_ids?

CVE-2026-93840 (vLLM before 0.29.0 Cross-Request Logits Corruption via allowed_token_ids), published 2026-09-18, changed lines 970 to 999 of vllm/sampling_params.py.

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

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

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

_validate_allowed_token_ids

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

vllm/sampling_params.py

Last patched September 18, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

33

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

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

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

CVEs that patched it

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

vLLM before 0.29.0 Cross-Request Logits Corruption via allowed_token_ids
CVE-2026-93840 · lines 970–999 · +19 −14 in 2 hunks
Medium · CVSS 6.3
EPSS 0.2%2026-09-18

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 _validate_allowed_token_ids.

How many CVEs have patched _validate_allowed_token_ids?: 1 published CVEs changed _validate_allowed_token_ids in vllm-project/vllm, in 2 distinct patches totalling 33 changed lines, between 2026 and 2026.
What is the latest CVE that changed _validate_allowed_token_ids?: CVE-2026-93840 (vLLM before 0.29.0 Cross-Request Logits Corruption via allowed_token_ids), published 2026-09-18, changed lines 970 to 999 of vllm/sampling_params.py.
How does _validate_allowed_token_ids compare to the rest of vllm-project/vllm?: vllm-project/vllm has 83 CVEs with a located fix in total; 1 of them changed _validate_allowed_token_ids.
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