Skip to main content
VulnerabilityPublished

CVE-2026-118272: a2ui · Information Exposure Through Error Message

Affects a2uiSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 28 Oct 2026, 02:27 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
a2ui-projecta2uiAffected
  • 0.10.0 – 0.10.6
7 affected builds
Fixed in–
GitHuba2ui-project/a2uipkg:github/a2ui-project/a2uiOther threatsAffected
  • 0.10.0 – 0.10.6
7 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:a2ui-project:a2ui:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the patch identified by commit 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01 to versions 0.10.0 through 0.10.6 of a2ui. Installing this update will remediate the information exposure vulnerability. No additional mitigation steps are indicated.

Description

CVE-2026-118272 is a medium severity vulnerability in a2ui-project's a2ui component up to version 0.10.6. It involves the DataContext.dispatchExpressionError function in the Error Handler component, where manipulation can cause information exposure through error messages. The vulnerability can be exploited remotely. A patch identified by commit 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01 is available to address this issue.

References

Community reviews

Loading reviews…