A vulnerability was detected in ag-ui-protocol ag-ui 1.0. This impacts an unknown function of the file crates/ag-ui-client/src/sse.rs of the component SSE Frame Parser. Performing a manipulation results in resource consumption. The attack is possible to be carried out remotely. The pull request to fix this issue awaits acceptance.
CVE-2026-92362
Score 7.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 48(Track)EG Risk 48/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 computedSeverity73% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026GitHub - ag-ui-protocol/ag-ui: AG-UI: the Agent-User Interaction Protocol. Bring Agents into Frontend Applications. · GitHub
https://github.com/ag-ui-protocol/ag-ui/fix(rust): dispatch CRLF-delimited SSE frames and cap the read buffer
Upstream fix in progress (PR #2500 · ag-ui-protocol/ag-ui, state=open)
https://github.com/ag-ui-protocol/ag-ui/pull/2500[BUG]: Rust community SDK buffers without bounds and never dispatches CRLF-terminated frames · Issue #2439 · ag-ui-protocol/ag-ui · GitHub
https://github.com/ag-ui-protocol/ag-ui/issues/2439Vendor Advisories for CVE-2026-92362(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 20× in last 7d / 20× 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.
- 2026-09-19 23:23 UTCEG score recompute
- 2026-09-19 23:23 UTCGHSA enrichment
- 2026-09-19 12:20 UTCGHSA enrichment
- 2026-09-19 01:18 UTCEG score recompute
- 2026-09-19 01:17 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 14:15 UTCGHSA enrichment
- 2026-09-18 03:12 UTCEG score recompute
- 2026-09-18 03:12 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 16:09 UTCGHSA enrichment
- 2026-09-17 05:06 UTCGHSA enrichment
- 2026-09-16 18:03 UTCGHSA enrichment
- 2026-09-16 16:34 UTCEG score recompute
- 2026-09-16 16:34 UTCGHSA enrichment
- 2026-09-16 15:55 UTCEG score recompute
- 2026-09-16 15:55 UTCGHSA enrichment
- 2026-09-16 14:24 UTCEG score recompute
- 2026-09-16 13:27 UTCEG score recompute
- 2026-09-16 13:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-92362?
When was CVE-2026-92362 disclosed?
Is CVE-2026-92362 actively exploited?
What is the CVSS score of CVE-2026-92362?
How do I remediate CVE-2026-92362?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92362
Is Your Infrastructure Affected by CVE-2026-92362?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.