Summary
@a2ui/web_core: openUrl permits javascript: URI execution via agent-supplied button actions
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. No non-default configuration is required; the Basic Catalog is enabled by default.
Details
The vulnerability exists in the openUrl function implementation within the Basic Catalog of @a2ui/web_core (commit 23a003248abbf59da6c376ea64ace91d82d209ff).
Sink, renderers/web_core/src/v0_9/basic_catalog/functions/basic_functions.ts:428-430:
export const OpenUrlImplementation = createFunctionImplementation(OpenUrlApi, args => {
if (args.url && typeof window !== 'undefined' && window.open) {
window.open(args.url, '_blank');
}
});
window.open is called unconditionally with the agent-supplied args.url value. No scheme allowlist or blocklist is applied.
Insufficient schema validation, renderers/web_core/src/v0_9/basic_catalog/functions/basic_functions_api.ts:453-458:
export const OpenUrlApi = {
name: 'openUrl' as const,
returnType: 'void' as const,
schema: z.object({
url: z.preprocess(v => (v === undefined ? undefined : String(v)), z.string()),
}),
};
The Zod schema only requires a string; javascript: URIs pass validation without any rejection.
Full source-to-sink data flow:
renderers/web_core/src/v0_9/basic_catalog/components/basic_components.ts:356,ButtonApiacceptsaction: ActionSchema(entry point).renderers/web_core/src/v0_9/schema/common-types.ts:126-130,ActionSchemapermits{ functionCall: FunctionCallSchema }.renderers/web_core/src/v0_9/rendering/generic-binder.ts:243-255, on click, bound action callsresolveDeepSyncthendispatchAction.renderers/web_core/src/v0_9/rendering/data-context.ts:93-105,resolveDynamicValuedetects thecallkey and invokes the named function.renderers/web_core/src/v0_9/catalog/types.ts:177-186, catalog invoker runsfn.schema.parse(rawArgs)thenfn.execute().renderers/web_core/src/v0_9/basic_catalog/functions/basic_functions_api.ts:453-458,OpenUrlApivalidatesurlasz.string()only (no scheme check).renderers/web_core/src/v0_9/basic_catalog/functions/basic_functions.ts:428-430, sink:window.open(args.url, '_blank')executes thejavascript:URI.
All three renderers implemented in the A2UI repository are affected:
- React:
renderers/react/src/v0_9/catalog/basic/components/Button.tsx:33,onClick={props.action} - Lit:
renderers/lit/src/v0_9/catalogs/basic/components/Button.ts:112,@click=${() => props.action()} - Angular:
renderers/angular/src/v0_9/catalog/basic/button.component.ts:103-110,handleClick()→dataContext.resolveAction→dispatchAction
Any other A2UI renderer which depends on web_core and uses its basic catalog implementation is also affected.
Impact
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2026-10032 has a CVSS score of 9.3 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.10.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue was fixed in https://github.com/a2ui-project/a2ui/pull/1707 and released in web_core version 0.10.2, by blocking URLs that do not use the HTTP or HTTPS schemes, or those that are invalid.
Please fix this issue in your project by depending on a @a2ui/web_core version equal or greater than 0.10.2.
Frequently Asked Questions
- What is CVE-2026-10032? CVE-2026-10032 is a critical-severity cross-site scripting (XSS) vulnerability in @a2ui/web_core (npm), affecting versions >= 0.9.0, < 0.10.2. It is fixed in 0.10.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2026-10032? CVE-2026-10032 has a CVSS score of 9.3 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @a2ui/web_core are affected by CVE-2026-10032? @a2ui/web_core (npm) versions >= 0.9.0, < 0.10.2 is affected.
- Is there a fix for CVE-2026-10032? Yes. CVE-2026-10032 is fixed in 0.10.2. Upgrade to this version or later.
- Is CVE-2026-10032 exploitable, and should I be worried? Whether CVE-2026-10032 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-10032 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-10032? Upgrade
@a2ui/web_coreto 0.10.2 or later.