Quick answers
- Is CVE-2026-92362 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92362 being exploited in the wild.
- How severe is CVE-2026-92362?
- High severity, with a CVSS score of 7.3, published 16 September 2026.
- Which products and versions are affected?
- Ag-Ui-Protocol Ag-Ui 1.0.
- Is there a fix for CVE-2026-92362?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- Am I affected by CVE-2026-92362?
- Check whether you run Ag-Ui-Protocol Ag-Ui at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in crates/ag-ui-client/src/sse.rs, where the SSE frame parser implements unbounded buffering without per-frame or total-size limits (CWE-400). The parser only recognizes LF-style line termination and fails to handle CRLF or lone CR characters as line endings, which are permitted by the SSE specification. When a remote endpoint sends frames with CRLF terminators or oversized payloads, the parser accumulates bytes indefinitely in its buffer, exhausting available memory. The attack requires only network connectivity to a server controlled by the attacker or a compromised endpoint; no authentication or user interaction is needed. A fix is pending acceptance in a pull request.
Affected products
- ag-ui-protocol ag-ui 1.0
Timeline
- 2026-09-16: disclosed
- other: Issue reported 2026-08-18