CVE-2026-55574

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Prior to 0.24.0, the structured_outputs.regex API parameter passes a user-supplied regular expression string directly to the grammar compiler backends with no compilation timeout; in the xgrammar backend the string reaches the regex compiler with no guard, and in the outlines backend the validation step blocks structural issues such as lookarounds and backreferences but performs no complexity analysis, so a pattern with nested quantifiers passes all checks and causes exponential state-space expansion, allowing a single request containing an adversarial regex to hang an inference worker indefinitely and deny service. This issue is fixed in version 0.24.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 6, 2026
Patch available. Sources: github_commit, github_pr, github.
githubMentions a patch (unverified)

ReDoS via structured_outputs.regex compiled without timeout in xgrammar and outlines backends · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-rwxx-mrjm-wc2m
github_pr

[Security] Add timeout guard for regex compilation in structured outp…

Fix merged in vllm-project/vllm PR #45118 on 2026-06-13 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/45118
github_commit

commit 2b3006076c5e (vllm-project/vllm)

Fix landed in vllm-project/vllm commit 2b3006076c5e — awaiting tagged release

https://github.com/vllm-project/vllm/commit/2b3006076c5e9bc4cda9e03e3641388de3c5c286

Vendor Advisories for CVE-2026-55574(14)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatrhaii/vllm-spyre-rhel9:17896812012026-09-21redhat
redhatrhaii/vllm-cuda-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-rocm-rhel9:17896811262026-09-21redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhaiis/vllm-spyre-rhel9:17871617762026-08-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
vllm0.0.1 ... 0.9.2 (89 versions)
  • every version up to 0.24.0: fixed in 0.24.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 06:23 UTCEG score recompute
  18. 2026-09-23 06:23 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 05:59 UTCEG score recompute
  22. 2026-09-18 05:59 UTCVendor advisory
  23. 2026-09-17 19:31 UTCEPSS rescore
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-14 11:39 UTCVendor advisory
  3. 2026-09-13 23:56 UTCEG score recompute
  4. 2026-09-13 23:56 UTCVendor advisory
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 08:43 UTCEG score recompute
  7. 2026-09-13 08:43 UTCVendor advisory
  8. 2026-09-12 13:36 UTCEG score recompute
  9. 2026-09-12 13:36 UTCVendor advisory
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 14:10 UTCEG score recompute
  15. 2026-09-06 14:10 UTCVendor advisory
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-05 23:07 UTCEG score recompute
  18. 2026-09-05 23:07 UTCVendor advisory
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-30 19:48 UTCEG score recompute
  24. 2026-08-30 19:48 UTCVendor advisory
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 08:01 UTCEG score recompute
  27. 2026-08-30 08:01 UTCVendor advisory
  28. 2026-08-30 01:22 UTCEPSS rescore
  29. 2026-08-28 21:41 UTCEPSS rescore
  30. 2026-08-27 21:58 UTCEG score recompute
  31. 2026-08-27 21:58 UTCVendor advisory
  32. 2026-08-27 14:25 UTCEPSS rescore
  33. 2026-08-27 02:12 UTCEG score recompute
  34. 2026-08-27 02:12 UTCVendor advisory
  35. 2026-08-26 14:46 UTCEPSS rescore
  36. 2026-08-26 13:55 UTCEG score recompute
  37. 2026-08-25 13:49 UTCEPSS rescore
  38. 2026-08-24 20:48 UTCEG score recompute
  39. 2026-08-23 05:44 UTCEG score recompute
  40. 2026-08-23 00:19 UTCEPSS rescore
  41. 2026-08-22 04:48 UTCEG score recompute
  42. 2026-08-21 23:49 UTCEPSS rescore
  43. 2026-08-21 04:17 UTCEG score recompute
  44. 2026-08-20 22:55 UTCEPSS rescore
  45. 2026-08-20 02:27 UTCEG score recompute
  46. 2026-08-19 17:04 UTCEPSS rescore
  47. 2026-08-18 20:49 UTCEG score recompute
  48. 2026-08-18 13:48 UTCEPSS rescore
  49. 2026-08-17 15:08 UTCEG score recompute
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-16 15:43 UTCEG score recompute
  52. 2026-08-16 14:56 UTCEPSS rescore
  53. 2026-08-16 04:01 UTCEG score recompute
  54. 2026-08-16 02:14 UTCEPSS rescore
  55. 2026-08-15 04:37 UTCEG score recompute
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-14 05:07 UTCEG score recompute
  58. 2026-08-13 22:00 UTCEPSS rescore
  59. 2026-08-12 17:54 UTCEG score recompute
  60. 2026-08-12 13:51 UTCEPSS rescore
  61. 2026-08-11 18:24 UTCEG score recompute
  62. 2026-08-11 06:31 UTCEG score recompute
  63. 2026-08-11 00:00 UTCEPSS rescore
  64. 2026-08-09 19:25 UTCEG score recompute
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-08 20:01 UTCEG score recompute
  67. 2026-08-08 16:37 UTCEPSS rescore
  68. 2026-08-07 20:36 UTCEG score recompute
  69. 2026-08-06 21:12 UTCEG score recompute
  70. 2026-08-06 13:47 UTCEPSS rescore
  71. 2026-08-05 21:48 UTCEG score recompute
  72. 2026-08-05 19:17 UTCEPSS rescore
  73. 2026-08-04 21:57 UTCEG score recompute
  74. 2026-08-04 15:10 UTCEPSS rescore
  75. 2026-08-04 10:39 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55574?
CVE-2026-55574 is a high vulnerability published on July 6, 2026. vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Prior to 0.24.0, the structured_outputs.regex API parameter passes a user-supplied regular expression string directly to the grammar compiler backends with no compilation timeout; in the xgrammar backend the…
When was CVE-2026-55574 disclosed?
CVE-2026-55574 was first published on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55574 actively exploited?
CVE-2026-55574 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55574?
CVE-2026-55574 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55574?
A fix for CVE-2026-55574 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55574 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55574

Explore →

Is Your Infrastructure Affected by CVE-2026-55574?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs