Vulnerability in vllm (CVE-2025-71379)
Summary
Vulnerability in vllm (CVE-2025-71379). Risk of unauthorized operations or information disclosure. Exploitable via re.DOTALL. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Summary
A recent review identified several regular expressions in the vllm codebase that are susceptible to Regular Expression Denial of Service (ReDoS) attacks. These patterns, if fed with crafted or malicious input, may cause severe performance degradation due to catastrophic backtracking.
1. vllm/lora/utils.py Line 173
https://github.com/vllm-project/vllm/blob/2858830c39da0ae153bc1328dbba7680f5fbebe1/vllm/lora/utils.py#L173
Risk Description:
- The regex
r"\((.*?)\)\$?$"matches content inside parentheses. If input such as((((a|)+)+)+)is passed in, it can cause catastrophic backtracking, leading to a ReDoS vulnerability. - Using
.*?(non-greedy match) inside group parentheses can be highly sensitive to input length and nesting complexity.
Remediation Suggestions:
- Limit the input string length.
- Use a non-recursive matching approach, or write a regex with stricter content constraints.
- Consider using possessive quantifiers or atomic groups (not supported in Python yet), or split and process before regex matching.
2. vllm/entrypoints/openai/tool_parsers/phi4mini_tool_parser.py Line 52
https://github.com/vllm-project/vllm/blob/2858830c39da0ae153bc1328dbba7680f5fbebe1/vllm/entry…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-71379 has been found in vllm.
Attackers can target a specific entry point like re.DOTALL over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade vllm to 0.9.0 or later.
If unsure, ask your IT team or search "vllm CVE-2025-71379" on the vendor's site.
CVE-2025-71379 (vllm) — CWE-1333 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: re.DOTALL / model_output / current_text / actual
Patched: 0.9.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1333) exists in vllm. Attackers reach the vulnerable code path via re.DOTALL.
Check the vendor advisory for the affected versions of vllm. Attack surface: re.DOTALL / model_output / current_text / actual.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.9.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vllm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vllm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vllmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade vllm to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- exploit disclosure@vulncheck.com
- package github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com