CVE-2026-114054: vLLM before 0.31.0 Cross-Request Cache Aliasing via EXIF ImageID and Prefix-Cache Keys

Q: Which deployments are exposed?

vLLM deployments before 0.31.0 are affected where authenticated users can submit requests that influence shared cache keys, including EXIF ImageID or cache_salt values.

Q: What access and inputs does an attacker need?

The attacker needs authenticated access and must supply caller-controlled key material. They can use a UUID-valued EXIF ImageID or set cache_salt to match a LoRA name.

Q: What can a successful cache collision expose or reuse?

A collision using EXIF ImageID can cause the attacker to receive cached processed media from another request. Matching cache_salt to a LoRA name can reuse first-block KV state.

Q: What version should be used to avoid the affected range?

The affected range is vLLM versions before 0.31.0. Deployments should move out of that version range.

Published Oct 21, 2026

Updated

vLLM before 0.31.0 contains a cache aliasing vulnerability that allows authenticated attackers to collide shared cache keys by supplying caller-controlled values such as EXIF ImageID or cachesalt. Attackers can set a UUID EXIF ImageID to receive another request's cached processed media, or match cachesalt to a LoRA name to reuse first-block KV state.

Affected Software

1 affected component

vllm vllm<0.31.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade vLLM to a version that resolves this vulnerability.
Fixed in 0.31.0

Event History

Oct 21, 2026

CVE Published

via MITRE·12:36 AM

Data Sourced

via MITRE·12:36 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are exposed?

vLLM deployments before 0.31.0 are affected where authenticated users can submit requests that influence shared cache keys, including EXIF ImageID or cache_salt values.

What access and inputs does an attacker need?

The attacker needs authenticated access and must supply caller-controlled key material. They can use a UUID-valued EXIF ImageID or set cache_salt to match a LoRA name.

What can a successful cache collision expose or reuse?

A collision using EXIF ImageID can cause the attacker to receive cached processed media from another request. Matching cache_salt to a LoRA name can reuse first-block KV state.

What version should be used to avoid the affected range?

The affected range is vLLM versions before 0.31.0. Deployments should move out of that version range.

CVE-2026-114054: vLLM before 0.31.0 Cross-Request Cache Aliasing via EXIF ImageID and Prefix-Cache Keys

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed?

What access and inputs does an attacker need?

What can a successful cache collision expose or reuse?

What version should be used to avoid the affected range?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed?

What access and inputs does an attacker need?

What can a successful cache collision expose or reuse?

What version should be used to avoid the affected range?