# CVE-2026-116229: ffxiv-teamcraft FFXIV Teamcraft Renderer-Process IPC Bridge preload.ts clipboard.readText cross site scripting


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-3vm6-pg69-9wgh

## What is CVE-2026-116229?

CVE-2026-116229 is a medium-severity vulnerability in ffxiv-teamcraft FFXIV Teamcraft, published on 26 Oct 2026. 

### Official description

A vulnerability was determined in ffxiv-teamcraft FFXIV Teamcraft up to 11.4.31. Impacted is the function clipboard.readText of the file apps/electron/src/preload.ts of the component Renderer-Process IPC Bridge. This manipulation causes cross site scripting. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 11.4.32 is recommended to address this issue. Patch name: def118fdf36f8f3b615966893a132dd81d9cc3dc. Upgrading the affected component is recommended.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-116229 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116229 is a medium-severity vulnerability in ffxiv-teamcraft FFXIV Teamcraft, published on 26 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116229 exists.

Affected product: ffxiv-teamcraft FFXIV Teamcraft. 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-116229/ (Markdown: https://insights.sbomify.com/CVE-2026-116229/index.md)
```

## Sources

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

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