CVE-2026-118538 a2ui-project a2ui Renderer root.js Root.renderComponentTree dynamically-determined object attributes
Medium 5.1
Published
Updated
Check this codebase for CVE-2026-118538 and fix it if it is affected.
What it is: CVE-2026-118538 is a medium-severity vulnerability in a2ui-project a2ui, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-118538 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-118538/ (Markdown: https://insights.sbomify.com/CVE-2026-118538/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-118538?
CVE-2026-118538 is a medium-severity vulnerability in a2ui-project a2ui, published on 28 Oct 2026.
Official description
A vulnerability was determined in a2ui-project a2ui up to 0.12.0. This issue affects the function Root.renderComponentTree of the file src/0.8/ui/root.js of the component Renderer. Executing a manipulation can lead to dynamically-determined object attributes. The attack may be launched remotely. The pull request to fix this issue awaits acceptance.
Which versions are affected by CVE-2026-118538?
How do I fix CVE-2026-118538?
No fix has been published for CVE-2026-118538 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-118538 being exploited?
There is no known exploitation of CVE-2026-118538 in the wild and no public exploit code.
Sources
Also known as GHSA-4c8v-q557-73fw.