security: bump vllm 0.20.0 → 0.24.0 and GitPython for CVE remediation - #2353
Merged
Conversation
- vllm 0.20.0 → 0.24.0 (security fix; also updates flashinfer-python 0.6.8.post1 → 0.6.12) - GitPython ≥3.1.50 → ≥3.1.57 (security fix; lock resolves to 3.1.58) - pyarrow already at 25.0.0 in lock (constraint >=23.0.1 unchanged, CVE addressed) - diskcache excluded via exclude-dependencies (no fix available; no longer pulled in by vllm 0.24.0) vllm 0.24.0 does not import NamespaceTool from openai.types.responses so the existing openai<=2.7.2 constraint is preserved — no openai SDK bump needed. Signed-off-by: Kajal Jain <kajalj@nvidia.com>
bxyu-nvidia
previously approved these changes
Aug 5, 2026
2 tasks
thomasdhc
previously approved these changes
Aug 5, 2026
…llm 0.24.0 The append call was missed in the initial commit; only the comment was updated. vllm 0.24.0 requires flashinfer-python==0.6.12. Signed-off-by: Kajal Jain <kajalj@nvidia.com>
kajalj22
enabled auto-merge (squash)
August 5, 2026 21:30
kajalj22
disabled auto-merge
August 5, 2026 21:31
kajalj22
added a commit
that referenced
this pull request
Aug 5, 2026
…ation (2353)` into `r0.5.0` (#2367) beep boop [🤖]: Hi @kajalj22 👋, we've cherry picked #2353 into for you! 🚀 Please review and approve this cherry pick by your convenience! Signed-off-by: Kajal Jain <kajalj@nvidia.com> Signed-off-by: NeMo Bot <nemo-bot@nvidia.com> Co-authored-by: kajalj22 <kajalj@nvidia.com>
OlegSudakov
pushed a commit
to OlegSudakov/Gym
that referenced
this pull request
Aug 7, 2026
…NVIDIA-NeMo#2353) ## Summary - **vllm** 0.20.0 → 0.24.0 (addresses security vulnerabilities; also updates flashinfer-python 0.6.8.post1 → 0.6.12) - **GitPython** ≥3.1.50 → ≥3.1.57 (addresses security vulnerability; lock resolves to 3.1.58) - **pyarrow** already at 25.0.0 in lock (existing `>=23.0.1` constraint sufficient; no change needed) - **diskcache** added to `exclude-dependencies` (no fix available; no longer pulled in by vllm 0.24.0 — blocked explicitly to prevent re-introduction) vllm 0.24.0 does not import `NamespaceTool` from `openai.types.responses`, so the existing `openai<=2.7.2` constraint is preserved and no openai SDK bump is required. ## Test plan - [x] CI passes (lint, unit tests, pre-commit hooks, server suite, build) - [x] `uv lock` resolves cleanly with no conflicts 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Kajal Jain <kajalj@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
>=23.0.1constraint sufficient; no change needed)exclude-dependencies(no fix available; no longer pulled in by vllm 0.24.0 — blocked explicitly to prevent re-introduction)vllm 0.24.0 does not import
NamespaceToolfromopenai.types.responses, so the existingopenai<=2.7.2constraint is preserved and no openai SDK bump is required.Test plan
uv lockresolves cleanly with no conflicts🤖 Generated with Claude Code