How many CVEs have patched process_inputs?

2 published CVEs changed process_inputs in vllm-project/vllm, in 3 distinct patches totalling 3 changed lines, between 2025 and 2026.

What is the latest CVE that changed process_inputs?

CVE-2026-93989 (vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words), published 2026-09-19, changed lines 328 of vllm/v1/engine/input_processor.py.

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

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

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

2 files

process_inputs

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

Defined in 2 files

Last patched September 19, 2026

2

CVEs

That changed this function

3

Distinct patches

Backports counted once

3

Lines changed

Added plus removed

2025–2026

Years

By CVE publication date

Overview

process_inputs in vllm-project/vllm was changed by 2 published CVE fixes between 2025 and 2026, in 3 distinct patches that added or removed 3 lines in total.

The name occurs in 2 files: vllm/v1/engine/processor.py, vllm/v1/engine/input_processor.py.

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 process_inputs, newest first, with the lines each fix touched.

vLLM through 0.29.0 Cross-Request Logits Corruption via bad_words
CVE-2026-93989 · vllm/v1/engine/input_processor.py · line 328 · +1 −1
Low · CVSS 2.3
EPSS 0.2%2026-09-19
vLLM’s Chunk-Based Prefix Caching Vulnerable to Potential Timing Side-Channel
CVE-2025-46570 · vllm/v1/engine/processor.py · line 320 · +1 −0
Low · CVSS 2.6
EPSS 0.3%2025-05-29

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 files that CVE fixes also changed.

1_validate_structured_outputvllm/v1/engine/processor.py3 CVEs · 2 patches2025

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

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