How many CVEs have patched update_from_tokenizer?

1 published CVEs changed update_from_tokenizer in vllm-project/vllm, in 1 distinct patches totalling 23 changed lines, between 2026 and 2026.

What is the latest CVE that changed update_from_tokenizer?

CVE-2026-93989 (vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words), published 2026-09-19, changed lines 659 to 710 of vllm/sampling_params.py.

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

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

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

update_from_tokenizer

Name: update_from_tokenizer 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 19, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

23

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

update_from_tokenizer in vllm-project/vllm was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 23 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 update_from_tokenizer, newest first, with the lines each fix touched.

vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words
CVE-2026-93989 · lines 659–710 · +19 −4 in 2 hunks
Low · CVSS 2.3
EPSS 0.2%2026-09-19

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

How many CVEs have patched update_from_tokenizer?: 1 published CVEs changed update_from_tokenizer in vllm-project/vllm, in 1 distinct patches totalling 23 changed lines, between 2026 and 2026.
What is the latest CVE that changed update_from_tokenizer?: CVE-2026-93989 (vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words), published 2026-09-19, changed lines 659 to 710 of vllm/sampling_params.py.
How does update_from_tokenizer compare to the rest of vllm-project/vllm?: vllm-project/vllm has 83 CVEs with a located fix in total; 1 of them changed update_from_tokenizer.
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