a2ui-project a2ui up to 0.10.6 data-context Resolver data-context.ts resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 1.30 |
Summary
A vulnerability identified as problematic has been detected in a2ui-project a2ui up to 0.10.6. Affected is an unknown function of the file renderers/web_core/src/v0_9/rendering/data-context.ts of the component data-context Resolver. Performing a manipulation results in resource consumption. This vulnerability is cataloged as CVE-2026-118271. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in a2ui-project a2ui up to 0.10.6. It has been classified as problematic. This affects some unknown functionality of the file renderers/web_core/src/v0_9/rendering/data-context.ts of the component data-context Resolver. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-118271. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
Applying the patch eb314e14fabd29cfb4a74e1202afc4fe2081efa2 is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-111537). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: eb314e14fabd29cfb4a74e1202afc4fe2081efa2
Timeline
10/27/2026 Advisory disclosed10/27/2026 VulDB entry created
10/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 2384
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-118271 (🔒)
GCVE (CVE): GCVE-0-2026-118271
GCVE (VulDB): GCVE-100-427569
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/27/2026 22:01Updated: 10/28/2026 03:45
Changes: 10/27/2026 22:01 (61), 10/28/2026 03:45 (1)
Complete: 🔍
Submitter: ez-lbz
Cache ID: 216::103
Submit
Accepted
- Submit #1015115: a2ui-project a2ui <=0.10.6 CWE-400 (by ez-lbz)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.