# CVE-2026-118272: a2ui-project a2ui Error data-context.ts DataContext.dispatchExpressionError information exposure


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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-hxwv-qhw4-49vx

## What is CVE-2026-118272?

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

### Official description

A vulnerability was detected in a2ui-project a2ui up to 0.10.6. Affected is the function DataContext.dispatchExpressionError of the file renderers/web_core/src/v0_9/rendering/data-context.ts of the component Error Handler. Performing a manipulation results in information exposure through error message. It is possible to initiate the attack remotely. The exploit is now public and may be used. The patch is named 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01. It is suggested to install a patch to address this issue.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-118272 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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