ag-ui-protocol ag-ui HttpAgent http.ts information disclosure
Affects the @ag-ui/client HttpAgent (verified against npm release 0.0.58), which follows redirects by default. No vendor rating is published, and no fixed version is listed.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The ag-ui-protocol TypeScript client SDK, specifically its HttpAgent component, contains a flaw that can let a remote attacker access information they should not be able to see.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A security flaw has been discovered in ag-ui-protocol ag-ui up to 0.0.58. This affects an unknown function of the file sdks/typescript/packages/client/src/agent/http.ts of the component HttpAgent. Performing a manipulation results in information disclosure. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The pull request to fix this issue awaits acceptance.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ag-ui-protocol ag-ui
0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, and 28 more
References 7
GitHub · ag-ui-protocol/ag-ui
Questions about CVE-2026-120233
What does this mean?
HttpAgent follows HTTP redirects by default, so the run request and its credentials can be sent on to a different origin. A compromised or malicious agent endpoint can use this to obtain the tenant's credentials and request body, or to make the client POST to internal URLs (client-side SSRF).Source: github.com, github.com
Am I affected, and how do I check?
The affected package is @ag-ui/client, verified against npm release 0.0.58, where HttpAgent sets no redirect option. To check, look at the installed @ag-ui/client version in your lockfile or package.json and confirm whether your code uses HttpAgent.Source: github.com, github.com
What should I do about it?
The facts do not list a fixed version. Check the advisory for a release that surfaces redirects as errors instead of following them with the run request attached, and update to that release when it is available.Source: github.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Is the fix complete?
The fix is partial: redirects now surface as errors instead of being followed with the run request attached. The facts do not say what remains unfixed.Source: github.com, github.com