# CVE-2026-118273: a2ui-project a2ui data-model.ts DataModel.set 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-m23g-ww56-48rc

## What is CVE-2026-118273?

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

### Official description

A flaw has been found in a2ui-project a2ui up to 0.10.6. Affected by this vulnerability is the function DataModel.set of the file renderers/web_core/src/v0_9/state/data-model.ts. Executing a manipulation can lead to resource consumption. It is possible to launch the attack remotely. The exploit has been published and may be used. This patch is called 82789191ce551f4d7a095d273773fb24bd764c9d. A patch should be applied to remediate this issue.

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

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


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

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

## Is CVE-2026-118273 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118273 is a medium-severity vulnerability in a2ui-project a2ui, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118273 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-118273/ (Markdown: https://insights.sbomify.com/CVE-2026-118273/index.md)
```

## Sources

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

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