Skip to main content
VulnerabilityPublished

CVE-2026-118274: a2ui-project a2ui · Uncontrolled Resource Consumption

Affects a2uiSource GCVE Database

0
Authoritative record:CVE-2026-118274· Medium 5.3

Public exploit available · CVSS 5.3 Medium : upgrade to 0.10.7 as a priority.

Data as of 28 Oct 2026, 04:15 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Affects
a2ui-project a2ui up to 0.10.6
Patch
Available – fixed in 0.10.7
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

Upgrade a2ui-project/a2ui to 0.10.7.

Affected software

ProductAffectedFixed in
GitHuba2ui-project/a2uipkg:github/a2ui-project/a2uiOther threatsAffected
  • <0.10.7
Fixed in
  • 0.10.7

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

AI-suggested

A patch identified by commit c97f4a02d3fea33ce3e9de5cf3fd0e3b8f3a4f0e is recommended to remediate this vulnerability. Deploying this patch will address the resource consumption issue. No other mitigation or vendor advisory was provided.

Description

CVE-2026-118274 is a medium severity vulnerability in a2ui-project a2ui up to version 0.10.6. It affects an unknown functionality in the Binder component's generic-binder.ts file, leading to resource consumption. The vulnerability can be exploited remotely without user interaction. Public exploit details have been disclosed. A patch identified by commit c97f4a02d3fea33ce3e9de5cf3fd0e3b8f3a4f0e is recommended to fix the issue.

References

Community reviews

Loading reviews…