# Remediation Handoff: CVE-2026-105752

## Summary

NVD: vLLM is an inference and serving engine for large language models. NVD: Prior to 0.30.0, Harmony tool continuations submitted through "POST /v1/responses" requests rebuild the next-turn engine input without preserving the cache_salt value, placing the continuation prefix in the global unsalted cache namespace even when the caller... NVD: On deployments with prefix caching enabled, which is the default, an authenticated tenant who can reconstruct a victim's low-entropy post-tool history can submit the same continuation and use the cached_tokens_per_turn count to determine whether the prefix...

## Why it matters

CVSS severity is LOW with score 3.1. EPSS percentile is 0.11127. KEV status is not listed in KEV. Use this as a defensive priority handoff, not as an execution instruction.

## Affected context

* Vendor: vllm
* Product: vllm
* Component: unknown
* Version / CPE / PURL: unknown

## Remediation context

* Recommended route: vendor_patch_or_mitigation
* Vendor/advisory reference: official_reference_present
* Patch status: confirmed
* Fixed version: 0.30.0
* References: https://github.com/vllm-project/vllm/commit/6a2a2bb02b563b83f946012959fd3927984d072a, https://github.com/vllm-project/vllm/pull/50195, https://github.com/vllm-project/vllm/pull/51818, https://github.com/vllm-project/vllm/releases/tag/v0.30.0, https://github.com/vllm-project/vllm/security/advisories/GHSA-935w-9g4m-p28p

## Human checklist

* Confirm whether the listed product or package is present.
* Confirm affected version.
* Review vendor advisory or official source.
* Confirm patch, fixed version, mitigation, workaround, or monitor-only decision.
* Confirm exposure.
* Document remediation status.

## Safe AI / Codex handoff

* Goal: Prepare a defensive remediation plan for CVE-2026-105752 using only provided public-safe source context and any separate repo context supplied by the user.
* Allowed actions: summarize vendor guidance, prepare a defensive remediation plan, identify affected dependencies only when repo context is separately provided by the user, suggest tests and validation steps, document human verification questions
* Disallowed actions: generate offensive code, provide payloads, scan external targets, change production systems, merge or deploy changes, create GitHub issues or pull requests without explicit separate approval
* Acceptance criteria: Affected product or dependency presence is confirmed by a human., Affected version is confirmed or marked not applicable., Official advisory or source reference is reviewed., Patch, fixed version, mitigation, workaround, or monitor-only decision is documented., Validation steps are proposed without external scanning or production mutation.
* Human approval required: true

## Safety note

This handoff is for defensive triage and remediation planning only. It excludes offensive procedure, payload material, external target scan guidance, and auto-remediation.