# CVE-2026-92217: a2ui-project a2ui Message Parsing message-processor.ts processMessages dynamically-determined object attributes

> Remote attackers can exploit dynamic object attribute handling in a2ui message processing to potentially execute arbitrary code.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-5xvv-9qvw-m2ch

## What is CVE-2026-92217?

CVE-2026-92217 is a medium-severity code injection vulnerability in a2ui-project a2ui, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in a2ui-project a2ui up to 0.10.6. This affects the function processMessages of the file renderers/web_core/src/v0_9/processing/message-processor.ts of the component Message Parsing. This manipulation causes dynamically-determined object attributes. The attack can be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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


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

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

## Is CVE-2026-92217 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92217 is a medium-severity code injection vulnerability in a2ui-project a2ui, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92217 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-92217/ (Markdown: https://insights.sbomify.com/CVE-2026-92217/index.md)
```

## Sources

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

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