Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to AG-UI transport (PR:L)
-
DeliverySend malformed event content
-
ExploitBypass transport decoder validation
-
ExecutionTrigger improper parsing in middleware
-
ImpactCause limited information disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | The vulnerable component is the AG-UI transport decode/middleware path that parses inbound event content (the patch wraps resultEvent.content through contentToText() before tryParseA2UIOperations and tryParseRecoveryFailure in the a2ui-middleware, indicating non-text or structured content was parsed without proper validation). Exploitation requires network reach to an AG-UI endpoint and low-level privileges (PR:L) - i.e., the attacker must be an authorized participant able to submit events over the transport, not an anonymous internet attacker. Affected versions are ag-ui up to and including 0.0.58; the dependency bump to @ag-ui/core>=0.0.59 and the 2026-10-30 release indicate the fix lands in 0.0.59, so running a patched build removes the exposure. No user interaction is required (UI:N), but the exact content shape needed to trigger the flaw is not described in the available sources. |
| Impact | This is a medium-severity issue (CVSS 4.0 base 5.3) whose signals are internally consistent and point to moderate, not urgent, priority. The vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N shows a remotely reachable, low-complexity flaw that nonetheless requires some privilege level (PR:L), so it is not an unauthenticated internet-wide bug; the impact metrics VC:L/VI:L/VA:L with no subsequent-system impact (SC:N/SI:N/SA:N) indicate limited, bounded consequences consistent with the 'Information Disclosure' tag. The input carries an exploit-maturity of E:P (proof-of-concept) and a PoC reference, but no EPSS score is provided and the CVE is NOT on CISA KEV, so there is no evidence of active or widespread exploitation. The vuln.today decision label is 'this_month', which aligns with a real-but-non-emergency fix cadence rather than act_now. Net: a legitimate issue to patch in routine cycles, not a drop-everything priority; the main caveat is that it is a very early-version (0.0.x) component and the exact trigger is not described in the sources, so impact bounds rest on the CVSS vector rather than a detailed root-cause analysis. |
| Exploit ScenarioDerived | An attacker with low-level access to an AG-UI transport channel sends crafted or malformed event content to the Transport Decoder/middleware, which fails to validate it properly during parsing (CWE-20). The low-complexity network vector (AV:N/AC:L) with required privileges (PR:L) suggests the result is limited information disclosure or minor integrity/availability effects rather than code execution. A public PoC reference exists (GitHub issue #2524); it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 01, 2026
Improper input validation in the AG-UI protocol SDK transport decoder path affects ag-ui versions up to and including 0.0.58, allowing crafted event content to be parsed without proper text handling and producing limited confidentiality, integrity and availability impact. The attack is remote and requires low-level privileges (PR:L with no user interaction), meaning the attacker must be an authorized participant able to submit events over an AG-UI transport rather than an anonymous internet user. A public PoC reference exists (GitHub issue 2524) but it is not verified as working exploit code, and the vendor fix is available in 0.0.59 via commit 660182b973a44b8eda5484b14b88eb9cc251edc4.
RemediationAI
Upgrade ag-ui to 0.0.59 or later; the vendor fix is commit 660182b973a44b8eda5484b14b88eb9cc251edc4, published in https://github.com/ag-ui-protocol/ag-ui/pull/2774 and shipped in the release at https://github.com/ag-ui-protocol/ag-ui/releases/tag/release/2026-10-30, which bumps @ag-ui/core to >= 0.0.59 and zod to ^3.25.18/^3.25.76 and wraps resultEvent.content through contentToText() ahead of tryParseA2UIOperations and tryParseRecoveryFailure. Vendor guidance in the references is to upgrade the affected component, and no separate workaround is documented in the available sources. Because exploitation requires an authorized participant able to submit events over the transport, limiting event-submission rights on exposed AG-UI endpoints to trusted clients reduces exposure, but this is a deployment-level control derived from the assessed prerequisite rather than a vendor-stated fix, and it does not remove the flaw in unpatched builds. Detection details and the reporting record are at https://vuldb.com/vuln/429595.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
AG-UI is an open agent-user interaction protocol shipped as TypeScript SDK packages, with middlewares that decode inbound transport events and deserialize their content. The flaw is classified CWE-20 (improper input validation): in the a2ui-middleware the handlers called tryParseA2UIOperations() and tryParseRecoveryFailure() directly on resultEvent.content, so non-text or structured content reached the operation parser without being normalized or validated. The fix routes both call sites through contentToText(resultEvent.content) before parsing, moves schema imports to @ag-ui/core/schemas (schemas generated from the protocol spec and now committed on purpose), and bumps the zod dependency from ^3.22.4 to ^3.25.18/^3.25.76 so event payloads are validated against stricter schemas. The same change set pins @ag-ui/core >= 0.0.59 for the middleware package. Per the CPE cpe:2.3:a:ag-ui-protocol:ag-ui the affected package line is ag-ui through 0.0.58; the trigger shape required to reach the vulnerable parse path is not described in the available sources.
Know when Ag Ui gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Remotely reachable transport with low attack complexity but requiring an authorized low-privilege participant (PR:L); improper input validation yields limited, bounded impact across C/I/A with no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was detected in ag-ui-protocol ag-ui up to 0.0.58. Affected by this vulnerability is an unknown functionality of the component Transport Decoder Handler. The manipulation results in improper input validation. The attack may be launched remotely. The exploit is now public and may be used. The patch is identified as 660182b973a44b8eda5484b14b88eb9cc251edc4. It is suggested to upgrade the affected component.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Cross-origin information disclosure in the ag-ui TypeScript client: HttpAgent builds the POST run request with the conve
Unbounded memory growth in the AG-UI Rust client's SSE frame parser (crates/ag-ui-client/src/sse.rs, shipped in the ag-u
Denial of service in the ag-ui TypeScript client SDK (versions up to and including 0.0.58) allows a party that controls
Denial of service in the ag-ui TypeScript client SDK (versions up to 0.0.58) where the SSE/protobuf stream parser fails
Resource exhaustion in the ag-ui Protocol TypeScript client SDK (versions up to and including 0.0.58) allows a hostile o
Unbounded buffering in the Server-Sent Events parser of the AG-UI Community SDK (Kotlin/Java) lets a malicious or man-in
Memory exhaustion in the AG-UI Go community SDK's SSE client allows a remote attacker who controls or can intercept an S
Origin validation errors in the AG-UI TypeScript client SDK (ag-ui 1.0) allow remote, low-privileged attackers who can i
Uncaught exception handling in the A2A middleware of ag-ui-protocol ag-ui (all versions up to 2026-09-07) allows an atta
Incomplete cleanup of per-run state in the ag-ui TypeScript client SDK's FilterToolCallsMiddleware allows disallowed too
Unbounded request-body reads in the ag-ui Java community server SDK (JdkAgentHttpHandler, used by applications that inst
Unbounded memory growth in the ag-ui (AG-UI protocol) C++ community SDK's Server-Sent Events parser lets an attacker who
EUVD-2026-114875
GHSA-42cj-2xxr-4gv8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB