# CVE-2026-69116: FlyEnv < 4.18.0 Cross-Site Scripting via v-html

> Attackers can execute arbitrary code and access the filesystem by injecting malicious scripts via unsanitized markdown or AI chat content in FlyEnv.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-w92g-j683-fhvq

## What is CVE-2026-69116?

CVE-2026-69116 is a medium-severity cross-site scripting vulnerability in xpf0000 FlyEnv, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FlyEnv before 4.18.0 fails to sanitize HTML from markdown rendering and AI chat content passed to Vue v-html directives. Attackers can inject malicious scripts through markdown sources or chat messages that execute in the Electron renderer process with access to Node.js APIs and the filesystem.

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

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


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

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

## Is CVE-2026-69116 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69116 is a medium-severity cross-site scripting vulnerability in xpf0000 FlyEnv, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, 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-69116 exists.

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

## Sources

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

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