Is CVE-2026-92217 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92217 being exploited in the wild.

How severe is CVE-2026-92217?

Medium severity, with a CVSS score of 6.3, published 16 September 2026.

Which products and versions are affected?

a2ui-project a2ui up to 0.10.6.

Is there a fix for CVE-2026-92217?

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-92217 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-92217?

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.

CVE-2026-92217: a2ui message processor improper input validation

CVE-2026-92217 · Severity: medium · CVSS 6.3 · Published 2026-09-16

The a2ui web framework's message processor fails to validate incoming message envelopes and component types before storing them in the components model. This allows an attacker to inject arbitrary, unvalidated properties into the application's component state, creating a defense-in-depth gap that could be exploited by future consumers of the components model or in combination with other vulnerabilities.

Quick answers

Is CVE-2026-92217 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92217 being exploited in the wild.
How severe is CVE-2026-92217?: Medium severity, with a CVSS score of 6.3, published 16 September 2026.
Which products and versions are affected?: a2ui-project a2ui up to 0.10.6.
Is there a fix for CVE-2026-92217?: 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-92217 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-92217?: 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 an improper input validation issue (CWE-20) in the message-processor.ts file of a2ui's v0.9 processing logic. The processMessages function skips envelope schema validation that was present in the v0.8 model and accepts component types not defined in any catalog without validation, yet still commits them to the components model and triggers onCreated events. An attacker can remotely send crafted message payloads with arbitrary properties to inject unvalidated data. While current renderers do not directly exploit this, the unvalidated properties persist in the component model and are available to any downstream consumer, creating a significant attack surface for privilege escalation or data injection attacks.

Affected products

a2ui-project a2ui up to 0.10.6

Timeline

2026-08-17: disclosed: Issue reported to a2ui-project as bug #2297
2026-09-16: advisory: CVE-2026-92217 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.