Quick answers
- Is CVE-2026-118272 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118272 being exploited in the wild.
- How severe is CVE-2026-118272?
- Medium severity, with a CVSS score of 4.3, published 28 October 2026.
- Which products and versions are affected?
- A2ui-Project A2ui up to 0.10.6.
- Is there a fix for CVE-2026-118272?
- Yes: fixed in Fixed in commit 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01 (version not specified in advisory). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118272 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118272?
- Check whether you run A2ui-Project A2ui at an affected version. 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.
How to fix
- Fixed in: Fixed in commit 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01 (version not specified in advisory)
Technical details
The DataContext.dispatchExpressionError function in renderers/web_core/src/v0_9/rendering/data-context.ts fails to sanitize V8 stack traces before broadcasting error events through the surface.onError mechanism (CWE-209: Sensitive Information Disclosure). Attacker-controlled input can trigger runtime errors during expression evaluation, causing the raw stack trace—including filesystem paths and SDK line numbers—to be disclosed to all error subscribers. The vulnerability requires network access to send requests triggering expression evaluation, with no authentication needed.
Affected products
- a2ui-project a2ui up to 0.10.6
Timeline
- 2026-10-28: disclosed