# CVE-2026-118275: a2ui-project a2ui Resolver data-context.ts DataContext.resolveSignal resource consumption


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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-485f-gc3c-ph93

## What is CVE-2026-118275?

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

### Official description

A vulnerability was found in a2ui-project a2ui up to 0.10.6. This affects the function DataContext.resolveSignal of the file renderers/web_core/src/v0_9/rendering/data-context.ts of the component Resolver. The manipulation results in resource consumption. The attack can be launched remotely. The exploit has been made public and could be used. The patch is identified as c76e17272e52c12c6dcf68905b1df978c39e9aa5. It is advisable to implement a patch to correct this issue.

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

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


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

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

## Is CVE-2026-118275 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-118275 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118275 is a medium-severity vulnerability in a2ui-project a2ui, published on 28 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-118275 exists.

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-118275/ (Markdown: https://insights.sbomify.com/CVE-2026-118275/index.md)
```

## Sources

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

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