A security vulnerability has been detected in ag-ui-protocol ag-ui 1.0. This affects an unknown function of the file sdks/community/go/pkg/client/sse/client.go of the component SSE Client. Such manipulation leads to resource consumption. The attack can be executed remotely. The pull request to fix this issue awaits acceptance.
CVE-2026-92361
Score 4.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 20(Track)EG Risk 20/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 computedSeverity43% × 45%Exploitation1% × 40%Automatability0% × 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(go): bound the SSE frame and line the reader will hold
Upstream fix in progress (PR #2700 · ag-ui-protocol/ag-ui, state=open)
https://github.com/ag-ui-protocol/ag-ui/pull/2700[BUG]: Go community SDK accumulates SSE events without bounds · Issue #2438 · ag-ui-protocol/ag-ui · GitHub
https://github.com/ag-ui-protocol/ag-ui/issues/2438Vendor Advisories for CVE-2026-92361(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 17× in last 7d / 17× 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 20:22 UTCEG score recompute
- 2026-09-19 20:22 UTCGHSA enrichment
- 2026-09-18 20:38 UTCEG score recompute
- 2026-09-18 20:38 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:46 UTCEG score recompute
- 2026-09-17 20:46 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 21:01 UTCEG score recompute
- 2026-09-16 21:01 UTCGHSA enrichment
- 2026-09-16 19:29 UTCEG score recompute
- 2026-09-16 19:29 UTCGHSA enrichment
- 2026-09-16 18:04 UTCEG score recompute
- 2026-09-16 18:03 UTCGHSA enrichment
- 2026-09-16 13:26 UTCEG score recompute
- 2026-09-16 13:06 UTCEG score recompute
- 2026-09-16 13:05 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-92361?
When was CVE-2026-92361 disclosed?
Is CVE-2026-92361 actively exploited?
What is the CVSS score of CVE-2026-92361?
How do I remediate CVE-2026-92361?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92361
Is Your Infrastructure Affected by CVE-2026-92361?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.