vllm - ✅(Solved) Fix [Bug]: `vllm` depends on `xgrammar` version `0.1.29` exactly which is vulnerable to CVE-2026-25048 [1 pull requests, 1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#36886Fetched 2026-04-08 00:43:48
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
1
Author
Participants
Timeline (top)
cross-referenced ×2closed ×1commented ×1labeled ×1

Fix Action

Fixed

PR fix notes

PR #1: Fix xgrammar being locked to a version which has high vulnerabilities

Description (problem / solution / changelog)

Fixes #36886

<summary> Essential Elements of an Effective PR Description Checklist </summary>
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
</details>

BEFORE SUBMITTING, PLEASE READ https://docs.vllm.ai/en/latest/contributing (anything written below this line will be removed by GitHub Actions)

Changed files

  • requirements/common.txt (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

Your current environment

https://github.com/vllm-project/vllm/blob/7f1f36bf91860aed64aea58e61b23c01cf85d551/requirements/common.txt#L27 https://github.com/advisories/GHSA-7rgv-gqhr-fxg3

🐛 Describe the bug

https://github.com/advisories/GHSA-7rgv-gqhr-fxg3 The required xgrammar version has a high vulnerability

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

extent analysis

Fix Plan

To address the high vulnerability in the required xgrammar version, we need to update to a secure version.

Steps to Update xgrammar Version

# Replace the existing xgrammar line with the following
xgrammar==<secure_version>
  • Run pip install -r requirements/common.txt to update the xgrammar package
  • Verify that the update was successful by checking the xgrammar version:
import pkg_resources
print(pkg_resources.get_distribution('xgrammar').version)

This should print the secure version of xgrammar.

Verification

To verify that the fix worked, check the xgrammar version and ensure it matches the secure version. You can also use tools like pip audit or safety to scan for vulnerabilities in your dependencies.

Extra Tips

  • Regularly review your dependencies for vulnerabilities using tools like pip audit or safety.
  • Keep your dependencies up-to-date to ensure you have the latest security patches.
  • Consider using a dependency management tool like pip-compile to manage your dependencies and ensure consistency across environments.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING