Quick answers
- Is CVE-2026-92356 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92356 being exploited in the wild.
- How severe is CVE-2026-92356?
- Medium severity, with a CVSS score of 4.3, published 16 September 2026.
- Which products and versions are affected?
- a2ui-project a2ui 0.9, 0.9.1.
- Is there a fix for CVE-2026-92356?
- 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-92356 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92356?
- 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 uncontrolled resource consumption flaw (CWE-400) in the updateComponents function of basic_functions.ts in the @a2ui/web_core module. The root cause involves three issues: component arrays lack maximum size validation despite minimum validation, Intl.NumberFormat instances are cached indefinitely based on untrusted agent-supplied parameters without eviction, and descendant notifications incur quadratic complexity in bound paths. An unauthenticated remote attacker can exploit this by sending maliciously large component arrays or many unique formatter configurations to gradually exhaust memory and degrade CPU performance over a session lifetime. The vendor was informed early but has not yet provided a patch; remediation requires implementing caps on components, using an LRU cache for formatters, and optimizing notification indexing.
Affected products
- a2ui-project a2ui 0.9, 0.9.1
Timeline
- 2026-09-16: disclosed