Quick answers
- Is CVE-2026-92357 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92357 being exploited in the wild.
- How severe is CVE-2026-92357?
- Medium severity, with a CVSS score of 4.3, published 16 September 2026.
- Which products and versions are affected?
- a2ui-project a2ui 0.8, 0.9, 1.0.
- Is there a fix for CVE-2026-92357?
- A patch was published on 2026-09-14: Patch commit 1b3bff234661ce922cbc3771be642b23ec9fd0fa Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92357 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92357?
- 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 prototype chain traversal flaw in the getDataByPath function of model-processor.ts in a2ui versions 0.8, 0.9, and 1.0. The vulnerable code accessed object properties directly via current[segment] without checking if the property was an own property, allowing attackers to traverse inherited prototype chain properties. An attacker can craft a JSON pointer path to access and read inherited properties such as toString, valueOf, constructor, and __proto__ instead of legitimate data values. The attack is remotely initiated and requires network access, but does not require authentication. The fix (commit 1b3bff234661ce922cbc3771be642b23ec9fd0fa) adds an Object.prototype.hasOwnProperty.call() check to ensure only own properties are accessible, with a safe fallback to null for invalid paths.
Affected products
- a2ui-project a2ui 0.8, 0.9, 1.0
Timeline
- 2026-09-16: disclosed: CVE-2026-92357 published
- 2026-09-14: patched: Patch commit 1b3bff234661ce922cbc3771be642b23ec9fd0fa