Quick answers
- Is CVE-2026-92216 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92216 being exploited in the wild.
- How severe is CVE-2026-92216?
- Medium severity, with a CVSS score of 4.3, published 16 September 2026.
- Which products and versions are affected?
- a2ui-project a2ui up to 0.10.7.
- Is there a fix for CVE-2026-92216?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92216 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92216?
- Check whether anything you run is named in the advisory. 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.
Technical details
The vulnerability is a CWE-601 open redirect / URL redirection flaw in the openUrl function of the Binder component (file renderers/web_core/src/v0_9/rendering/generic-binder.ts). The root cause is that dynamic function properties, including openUrl, are evaluated at bind/render time rather than in response to user gestures, allowing unwanted URL navigation to execute automatically. Although a prior fix (CVE-2026-10032) restricts schemes to https:// with noopener and noreferrer flags, the absence of user interaction is the primary security gap. An attacker can craft a malicious agent or UI configuration with a property like {call: "openUrl", args: {url: "https://attacker.com"}} that executes when the surface renders. Mitigation by browser pop-up blockers is inconsistent; the long-term fix requires restricting side-effect functions (navigation, void-return actions) to user-initiated ACTION contexts.
Affected products
- a2ui-project a2ui up to 0.10.7
Timeline
- 2026-09-16: disclosed
- 2026-08-17: advisory: Issue reported on GitHub (#2296)