CVE-2026-10032 Arbitrary JavaScript Execution via openUrl in @a2ui/web_core
A malicious agent can execute arbitrary JavaScript in the victim's browser by supplying a javascript: URI to the openUrl function in @a2ui/web_core.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-10032?
CVE-2026-10032 is a medium-severity cross-site scripting vulnerability in Google @a2ui/web_core, published on 4 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
The openUrl function in @a2ui/web_core passes an agent-controlled URL directly to window.open() without validating the URI scheme. A malicious agent can supply a javascript: URI as the url argument of a Button component's functionCall action. When the user clicks the rendered button, arbitrary JavaScript executes in the victim application's browser origin, constituting a stored/reflected XSS with Critical severity. No non-default configuration is required; the Basic Catalog is enabled by default.
Weakness: CWE-79
Which versions are affected by CVE-2026-10032?
2 open source packages ship an affected version, including @a2ui/web_core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@a2ui/web_core npm | From 0.9.0 | 0.10.2 |
@a2ui/web_core npm | From 0.9.0 | 0.10.2 |
Products include Google A2ui\/Web Core.
How do I fix CVE-2026-10032?
Upgrade @a2ui/web_core to 0.10.2 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-10032 being exploited?
There is no known exploitation of CVE-2026-10032 in the wild and no public exploit code.
Sources
Also known as GHSA-72qq-p3r5-f7wq, MINI-fvvg-6f9m-2qq8.