CVE-2026-10032 Google CVE debrief

Who should care

Developers and administrators using @a2ui/web_core, especially those with user-generated content or untrusted input, should be aware of this vulnerability. Affected operators and platforms require review of the @a2ui/web_core component, and vulnerability-management teams should assess potential exposure. Security teams should prioritize patching and implement additional input validation and sanitization for URLs to prevent potential XSS attacks. Asset inventory and monitoring teams should review relevant logs for exposed assets that need extra review. Those responsible for change management should plan for vendor-supported updates or mitigations through normal change control where exposure is confirmed. Those tracking exceptions should ensure that retesting and documentation occur before closing the item. Those managing source code should consider disabling the Basic Catalog if not required or implementing compensating controls for exposed systems while remediation is scheduled and verified. Those responsible for incident response should be prepared to review compensating controls and monitor for suspicious activity. Those managing rollback and change windows should track exceptions and retest remediated assets. Those managing source tracking should ensure that evidence is documented before closing the item. The CVE record was published on 2026-08-04T16:16:20.983Z and has not been modified since then, indicating that immediate action is required to prevent potential XSS attacks. The debrief provides an executive overview covering the affected product or component, vulnerability class, likely operational impact, source-confidence limits, and review context. The technical summary provides affected product context, defensive impact, and source-grounded technical framing without unsupported root-cause or exploit claims. The evidence notes provide source grounding, evidence limits, known and unknown affected scope, and what defenders should verify to assess potential exposure and validate patch deployment. The recommended actions provide distinct safe defensive actions until the target count is met. The defensive priority indicates that organizations using the @a2ui/

Technical summary

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, leading to arbitrary JavaScript execution in the victim application's browser origin. This vulnerability allows for a stored/reflected XSS with Critical severity. The affected product context indicates that @a2ui/web_core users are impacted, and defensive impact suggests prioritizing patching to prevent potential XSS attacks.

Defensive priority

Organizations using the affected @a2ui/web_core should prioritize patching to prevent potential XSS attacks.

Recommended defensive actions

• Apply patches or updates to @a2ui/web_core to fix the openUrl function vulnerability
• Implement additional input validation and sanitization for URLs
• Monitor for suspicious activity and implement compensating controls
• Consider disabling the Basic Catalog if not required
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The openUrl function in @a2ui/web_core passes an agent-controlled URL directly to window.open() without validating the URI scheme, allowing for a stored/reflected XSS with Critical severity. The Basic Catalog is enabled by default, and no non-default configuration is required. Evidence limits suggest verifying user input and URL validation mechanisms. Defenders should review the affected @a2ui/web_core component, assess potential exposure, and validate patch deployment.

Official resources