CVE-2026-73556

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% 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, secondary
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

vLLM is an inference and serving engine for large language models. Prior to 0.26.0, the structured_outputs.regex parameter in vllm/v1/structured_output/backend_lm_format_enforcer.py is passed to lmformatenforcer.RegexParser without compile_regex_with_timeout or validation in validate_structured_output_request_lm_format_enforcer, allowing an unauthenticated /v1/completions request against the lm-format-enforcer backend to consume a CPU core and stall the structured-output engine path with a catastrophic regular expression. This issue is fixed in version 0.26.0.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 13, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

ReDoS via structured_outputs.regex in the lm-format-enforcer backend (no compile timeout) — missed sibling of GHSA-rwxx-mrjm-wc2m · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-48jh-3gj7-fg8v
github_release Patch Available

v0.26.0

Patch available: vllm-project/vllm v0.26.0

https://github.com/vllm-project/vllm/releases/tag/v0.26.0
github_pr

fix(security): guard lm-format-enforcer regex compile with timeout

Fix merged in vllm-project/vllm PR #47595 on 2026-07-14 — awaiting tagged release

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

commit c9a788eedc41 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/c9a788eedc412acceaa5112e0d44624b49841577

Vendor Advisories for CVE-2026-73556(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.0.1 ... 0.9.2 (92 versions)0.26.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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.

  1. 2026-09-19 00:14 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:29 UTCEG score recompute
  4. 2026-09-16 23:59 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 21:55 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 20:28 UTCEG score recompute
  10. 2026-09-12 20:43 UTCEG score recompute
  11. 2026-09-12 15:02 UTCEPSS rescore
  12. 2026-09-11 20:58 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 21:13 UTCEG score recompute
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-09 06:44 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 06:58 UTCEG score recompute
  19. 2026-09-07 07:13 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-06 07:22 UTCEG score recompute
  22. 2026-09-05 07:37 UTCEG score recompute
  23. 2026-09-04 07:52 UTCEG score recompute
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-03 06:58 UTCEG score recompute
Show 44 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-02 07:08 UTCEG score recompute
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 07:18 UTCEG score recompute
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-31 07:31 UTCEG score recompute
  8. 2026-08-30 19:18 UTCEPSS rescore
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 07:25 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 07:37 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 19:32 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 18:43 UTCEG score recompute
  17. 2026-08-26 14:47 UTCEPSS rescore
  18. 2026-08-25 17:12 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 17:14 UTCEG score recompute
  21. 2026-08-23 17:27 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 17:43 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 17:57 UTCEG score recompute
  26. 2026-08-20 22:56 UTCEPSS rescore
  27. 2026-08-19 18:27 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 17:06 UTCEG score recompute
  30. 2026-08-18 13:49 UTCEPSS rescore
  31. 2026-08-18 13:49 UTCEPSS rescore
  32. 2026-08-17 16:47 UTCEG score recompute
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-16 17:03 UTCEG score recompute
  35. 2026-08-16 14:56 UTCEPSS rescore
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 02:15 UTCEPSS rescore
  38. 2026-08-15 17:19 UTCEG score recompute
  39. 2026-08-15 01:31 UTCEPSS rescore
  40. 2026-08-14 17:34 UTCEG score recompute
  41. 2026-08-14 17:08 UTCEG score recompute
  42. 2026-08-13 15:23 UTCEG score recompute
  43. 2026-08-13 15:12 UTCEG score recompute
  44. 2026-08-13 15:11 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73556?
CVE-2026-73556 is a medium vulnerability published on August 13, 2026. vLLM is an inference and serving engine for large language models. Prior to 0.26.0, the structuredoutputs.regex parameter in vllm/v1/structuredoutput/backendlmformatenforcer.py is passed to lmformatenforcer.RegexParser without compileregexwithtimeout or validation in…
When was CVE-2026-73556 disclosed?
CVE-2026-73556 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73556 actively exploited?
CVE-2026-73556 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-73556?
CVE-2026-73556 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-73556?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73556, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-73556?

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

Start Free Scan →Browse All CVEs