vLLM 0.32.0 raises the Python floor and tightens serving defaults
The release drops Python 3.10, restricts browser origins by default and bundles three named security fixes alongside serving and hardware updates.
vLLM 0.32.0 is out with operationally significant defaults, three named security fixes and a broad serving-engine update. The upstream project published the release on October 18.
What changed
The release drops Python 3.10 and now supports Python 3.11 through 3.14. It also changes the API server’s default cross-origin resource-sharing behavior: browser origins are no longer allowed by default, and deployments that need them must set --allowed-origins explicitly.
The project lists fixes for three GitHub Security Advisories covering chat-template resource exhaustion, tokenizer max_token_id handling and peer-to-peer ZeroMQ socket exhaustion. Additional hardening limits untrusted images to raster formats, signs shared-memory multimodal cache handles and rejects JSON schemas nested beyond 64 levels.
Beyond security, 0.32.0 expands Model Runner V2, makes it the default on ROCm, adds low-precision KV-cache paths across more hardware, introduces a generic Hugging Face tool and reasoning parser, and changes API-worker connection selection to favor the least-loaded worker. The release notes also call out new model support and multiple removed or renamed interfaces.
Who it affects
Operators upgrading from an earlier vLLM release need to check their Python runtime and browser-client configuration before rollout. Python 3.10 environments will not meet the new minimum, while browser applications that relied on permissive default CORS behavior will require an explicit origin list.
Applications consuming Responses API reasoning streams or removed configuration options also need compatibility testing. The upstream notes identify renamed reasoning events, removal of cascade attention and removal of several previously deprecated APIs.
What to do
Before upgrading, teams should inventory Python 3.10 images, declare required browser origins, and run API-contract tests against the 0.32.0 image. Security-sensitive deployments should prioritize the release review because the upstream changelog names three advisory fixes and several additional input-validation changes.
The full compatibility list, artifacts and hardware-specific changes are in the v0.32.0 release notes.
sources
- vLLM v0.32.0 release notesgithub.com
comments · 0