# CVE-2026-92114: a2ui-project a2ui Basic Catalog safe_regex.ts redos

> Remote attackers can cause denial of service in a2ui web core library via inefficient regular expression complexity in the Basic Catalog.

- **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:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-m654-p328-j29m

## What is CVE-2026-92114?

CVE-2026-92114 is a medium-severity denial of service vulnerability in a2ui-project a2ui, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in a2ui-project a2ui up to 0.10.6. Affected is an unknown function of the file renderers/web_core/src/v0_9/basic_catalog/functions/safe_regex.ts of the component Basic Catalog. Such manipulation leads to inefficient regular expression complexity. The attack can be launched remotely.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-1333 (Inefficient Regular Expression Complexity)

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


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

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

## Is CVE-2026-92114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92114 is a medium-severity denial of service vulnerability in a2ui-project a2ui, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92114 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-92114/ (Markdown: https://insights.sbomify.com/CVE-2026-92114/index.md)
```

## Sources

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

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