vllm-project vLLM up to 29.x Flash Late-Interaction Scoring X-Request-Id race condition

Summaryinfo

A vulnerability classified as problematic has been found in vllm-project vLLM up to 29.x. Affected by this vulnerability is an unknown functionality of the component Flash Late-Interaction Scoring. Performing a manipulation of the argument X-Request-Id results in race condition. This vulnerability was named CVE-2026-105755. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in vllm-project vLLM up to 29.x. It has been classified as problematic. This affects some unknown processing of the component Flash Late-Interaction Scoring. The manipulation of the argument X-Request-Id with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on integrity, and availability. The summary by CVE is:

vLLM is an inference and serving engine for large language models. Prior to 0.30.0, flash late-interaction scoring at the /score and /rerank endpoints derives each worker's query_key value from the caller-controlled X-Request-Id header. A concurrent request that reuses a victim's identifier can overwrite the cached query embedding so the victim's documents are scored against the attacker's query, and shared use counters can also cause a late-interaction cache-miss error. This issue is fixed in version 0.30.0.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-105755 since 10/05/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 0.30.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Project Management Software

Vendor

• vllm-project

Name

• vLLM

Version

• 29.x

Website

• Product: https://github.com/vllm-project/vllm/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion