How many CVEs have patched _update_seq_hashes?

1 published CVEs changed _update_seq_hashes in vllm-project/vllm, in 2 distinct patches totalling 4 changed lines, between 2025 and 2025.

What is the latest CVE that changed _update_seq_hashes?

CVE-2025-25183 (vLLM using built-in hash() from Python 3.12 leads to predictable hash collisions in vLLM prefix cache), published 2025-02-07, changed lines 1023 to 1038 of vllm/core/block/prefix_caching_block.py.

How does _update_seq_hashes 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_seq_hashes.

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_seq_hashes

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

vllm/core/block/prefix_caching_block.py

Last patched February 7, 2025

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

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

vLLM using built-in hash() from Python 3.12 leads to predictable hash collisions in vLLM prefix cache
CVE-2025-25183 · lines 1023–1038 · +2 −2 in 2 hunks
Low · CVSS 2.6
EPSS 0.2%2025-02-07

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

How many CVEs have patched _update_seq_hashes?: 1 published CVEs changed _update_seq_hashes in vllm-project/vllm, in 2 distinct patches totalling 4 changed lines, between 2025 and 2025.
What is the latest CVE that changed _update_seq_hashes?: CVE-2025-25183 (vLLM using built-in hash() from Python 3.12 leads to predictable hash collisions in vLLM prefix cache), published 2025-02-07, changed lines 1023 to 1038 of vllm/core/block/prefix_caching_block.py.
How does _update_seq_hashes 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_seq_hashes.
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