Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

@a2ui/web_core: openUrl permits javascript: URI execution via agent-supplied button actions

CVE-2026-10032GHSA-72qq-p3r5-f7wq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@a2ui/web_core 0.10.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-10032: 0.13% estimated exploitation activity in the next 30 days; percentile 2.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The openUrl function in @a2ui/webcore 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/webcore (commit 23a003248abbf59da6c376ea64ace91d82d209ff). Sink — renderers/webcore/src/v09/basiccatalog/functions/basicfunctions.ts:428-430: window.open is called unconditionally with the agent-supplied args.url value. No scheme allowlist or blocklist is applied. Insufficient schema validation — renderers/webcore/src/v09/basiccatalog/functions/basicfunctionsapi.ts:453-458: The Zod schema only requires…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-72qq-p3r5-f7wq

  2. Revision 2 · amended ·

    Amended from osv record GHSA-72qq-p3r5-f7wq

  3. Revision 1 · created ·

    Published from ghsa record GHSA-72qq-p3r5-f7wq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-10032

Advisory: @a2ui/web_core: `openUrl` permits `javascript:` URI execution via agent-supplied button actions
IDs: CVE-2026-10032, GHSA-72qq-p3r5-f7wq
Record: https://patchnext.com/advisories/cve-2026-10032 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @a2ui/web_core 0.10.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @a2ui/web_core: affected >= 0.9.0, < 0.10.2; fixed in 0.10.2

## Suggested inspection (read-only)
- `npm ls @a2ui/web_core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @a2ui/web_core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-72qq-p3r5-f7wq (GitHub-reviewed advisory GHSA-72qq-p3r5-f7wq lists affected ranges: npm @a2ui/web_core >=0.9.0 <0.10.2)
- Verified: https://osv.dev/vulnerability/GHSA-72qq-p3r5-f7wq (OSV record GHSA-72qq-p3r5-f7wq lists affected ranges: npm @a2ui/web_core >=0.9.0 <0.10.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…