Quick answers
- Is CVE-2026-92214 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92214 being exploited in the wild.
- How severe is CVE-2026-92214?
- Low severity, with a CVSS score of 3.5, 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-92214?
- 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-92214 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92214?
- 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 stored cross-site scripting (XSS) flaw in the sanitizer-markdown-renderer-service.ts component. The vulnerable code calls Angular's bypassSecurityTrustHtml() on unsanitized agent-supplied text and then binds it to the DOM via @HostBinding('innerHTML'), completely bypassing Angular's built-in HTML sanitization. An attacker can craft a chat message containing malicious HTML/JavaScript (e.g., img src with onerror event handler) that executes in the context of the host application. The vulnerability affects the community sample code up to version 0.10.7 and is the default configuration, meaning applications copying the sample inherit the unsafe behavior. Patches or workarounds involve replacing the unsafe renderer with a sanitizing pipeline such as markdown-it with html:false and DOMPurify.
Affected products
- a2ui-project a2ui up to 0.10.7
Timeline
- 2026-08-17: disclosed: Vulnerability disclosed as GitHub issue #2294
- 2026-09-16: advisory: CVE-2026-92214 published