# CVE-2026-92213: a2ui-project a2ui Angular Renderer server-to-client.ts z.any injection

> Remote attackers can inject code via the primaryColor argument in the Angular Renderer, requiring a patch to mitigate.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-9j57-x538-48q4

## What is CVE-2026-92213?

CVE-2026-92213 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, and only if a user opens a file or follows a link.

### Official description

A vulnerability was detected in a2ui-project a2ui up to 0.10.6. This impacts the function z.any of the file renderers/web_core/src/v0_9/schema/server-to-client.ts of the component Angular Renderer. Performing a manipulation of the argument primaryColor results in injection. The attack is possible to be carried out remotely. The patch is named fb8e85aec78d04e81feb9992a57638ca1ec4dc1b. It is suggested to install a patch to address this issue.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-707 (Improper Neutralization)

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


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

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

## Is CVE-2026-92213 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92213 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92213 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-92213/ (Markdown: https://insights.sbomify.com/CVE-2026-92213/index.md)
```

## Sources

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

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