Quick answers
- Is CVE-2026-10032 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10032 being exploited in the wild.
- How severe is CVE-2026-10032?
- Critical severity, with a CVSS score of 9.3, published 4 August 2026.
- Which products and versions are affected?
- @a2ui/web_core (npm) >= 0.9.0, < 0.10.2, SEMVER:introduced=0.9.0,fixed=0.10.2.
- Is there a fix for CVE-2026-10032?
- Yes. @a2ui/web_core (npm): upgrade to 0.10.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10032 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-10032?
- Check whether you run Google A2ui\, Google Web Core or @a2ui/web_core (npm) 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.
How to fix
- @a2ui/web_core (npm): upgrade to 0.10.2 or later
npm install @a2ui/web_core@0.10.2
Technical details
The vulnerability is a cross-site scripting (XSS) flaw in the openUrl function (basic_functions.ts) which accepts agent-controlled URLs without validating the URI scheme. The Zod schema used to validate the url parameter only checks that it is a string, with no allowlist or blocklist of permitted schemes. An attacker can supply a javascript: URI as the url argument of a Button component's functionCall action. When a user clicks the button, window.open() executes the javascript: URI in the victim's browser origin, allowing arbitrary code execution. The vulnerability affects all three renderers (React, Lit, Angular) that depend on web_core's basic catalog. The issue was patched in version 0.10.2 by implementing strict scheme validation to allow only HTTP and HTTPS URIs.
Affected products
- A2UI Project web_core 0.9.0, 0.9.1, 0.9.2, 0.10.0, 0.10.1
Identifiers
- CVE-2026-10032
- GHSA-72qq-p3r5-f7wq
Timeline
- 2026-08-04: disclosed: CVE-2026-10032 and GHSA-72qq-p3r5-f7wq published
- 2026-08-03: patched: Fixed in web_core version 0.10.2 via PR #1707