CVE-2026-92365

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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

A vulnerability was found in vllm-project vllm up to 0.29.0. Affected by this issue is some unknown functionality of the file vllm/v1/sample/thinking_budget_state.py. The manipulation results in inefficient algorithmic complexity. It is possible to launch the attack remotely. The pull request to fix this issue awaits acceptance.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
No patch confirmed yet. Sources: github_pr.
github_pr

fix(security): restore incremental marker search cursors in thinking budget state

Upstream fix in progress (PR #51133 · vllm-project/vllm, state=open)

https://github.com/vllm-project/vllm/pull/51133
generic

GitHub - vllm-project/vllm: A high-throughput and memory-efficient inference and serving engine for LLMs · GitHub

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

Vendor Advisories for CVE-2026-92365(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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-18 22:28 UTCEG score recompute
  2. 2026-09-18 22:28 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 20:16 UTCEG score recompute
  5. 2026-09-17 20:16 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-16 18:04 UTCEG score recompute
  8. 2026-09-16 18:03 UTCGHSA enrichment
  9. 2026-09-16 14:23 UTCEG score recompute
  10. 2026-09-16 14:06 UTCEG score recompute
  11. 2026-09-16 14:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92365?
CVE-2026-92365 is a medium vulnerability published on September 16, 2026. A vulnerability was found in vllm-project vllm up to 0.29.0. Affected by this issue is some unknown functionality of the file vllm/v1/sample/thinkingbudgetstate.py. The manipulation results in inefficient algorithmic complexity. It is possible to launch the attack remotely. The pull request to fix…
When was CVE-2026-92365 disclosed?
CVE-2026-92365 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92365 actively exploited?
CVE-2026-92365 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 67.4% of all scored CVEs.
What is the CVSS score of CVE-2026-92365?
CVE-2026-92365 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-92365?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92365, 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

Explore the affected products and dependency analysis for CVE-2026-92365

Explore →

Is Your Infrastructure Affected by CVE-2026-92365?

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

Start Free Scan →Browse All CVEs