Skip to main content
VulnerabilityPublished

CVE-2026-118271: a2ui · Resource Consumption

Affects a2uiSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 28 Oct 2026, 01:57 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:N/VI:N/VA:L/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 official patch identified by commit eb314e14fabd29cfb4a74e1202afc4fe2081efa2 to remediate this vulnerability. Updating a2ui-project a2ui to a version that includes this patch will resolve the issue. No other mitigation or workaround is specified.

Description

CVE-2026-118271 is a medium severity vulnerability in a2ui-project a2ui versions 0.10.0 through 0.10.6. It involves resource consumption caused by manipulation of an unknown function in the data-context Resolver component. The vulnerability can be exploited remotely without user interaction or privileges. Public exploit code has been disclosed. A patch identified by commit eb314e14fabd29cfb4a74e1202afc4fe2081efa2 is available to remediate the issue.

References

Community reviews

Loading reviews…