# CVE-2026-118271: a2ui-project a2ui data-context Resolver data-context.ts resource consumption


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-42fj-5gr6-hr6m

## What is CVE-2026-118271?

CVE-2026-118271 is a medium-severity vulnerability in a2ui-project a2ui, published on 28 Oct 2026. 

### Official description

A security vulnerability has been detected in a2ui-project a2ui up to 0.10.6. This impacts an unknown function of the file renderers/web_core/src/v0_9/rendering/data-context.ts of the component data-context Resolver. Such manipulation leads to resource consumption. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The name of the patch is eb314e14fabd29cfb4a74e1202afc4fe2081efa2. Applying a patch is advised to resolve this issue.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-118271?


## How do I fix CVE-2026-118271?

No fix has been published for CVE-2026-118271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118271 being exploited?

There is no known exploitation of CVE-2026-118271 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118271 and fix it if it is affected.

What it is: CVE-2026-118271 is a medium-severity vulnerability in a2ui-project a2ui, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118271 in the wild and no public exploit code.

Affected product: a2ui-project a2ui. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118271/ (Markdown: https://insights.sbomify.com/CVE-2026-118271/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118271
- OSV: https://osv.dev/vulnerability/CVE-2026-118271

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118271/
Summaries are generated and may contain mistakes; the official description above is the record.