# CVE-2026-105220: Twine 2 Desktop through 2.12.0 Arbitrary Code Execution via Imported Story Files

> Attackers can execute arbitrary code by tricking users into importing malicious story files containing XSS payloads in Twine 2 Desktop.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-qx8m-f384-xrj3

## What is CVE-2026-105220?

CVE-2026-105220 is a high-severity cross-site scripting vulnerability in klembot twinejs, published on 4 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Twine 2 desktop through 2.12.0 contains a cross-site scripting vulnerability in importStories() that executes markup from imported story files in the editor window. Attackers can craft a story file whose script calls the twineElectron openWithScratchFile IPC bridge to write and open a .bat file, executing code as the user.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-105220 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105220 is a high-severity cross-site scripting vulnerability in klembot twinejs, published on 4 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105220 exists.

Affected product: klembot twinejs. 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-105220/ (Markdown: https://insights.sbomify.com/CVE-2026-105220/index.md)
```

## Sources

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

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