# CVE-2026-26993: Flare has XSS vulnerability in Raw File Preview

> Attackers can execute arbitrary scripts via malicious SVG files in raw preview mode, potentially stealing user data from the Flare file sharing platform.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-q8fp-w6m5-4gjm

## What is CVE-2026-26993?

CVE-2026-26993 is a medium-severity cross-site scripting vulnerability in FlintSH Flare, published on 20 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Flare is a Next.js-based, self-hostable file sharing platform that integrates with screenshot tools. Versions 1.7.0 and below allow users to upload files without proper content validation or sanitization. By embedding malicious JavaScript within an SVG (or other active content formats such as HTML or XML), an attacker can achieve script execution in the context of the application's origin when a victim views the file in “raw” mode. This results in a stored Cross-Site Scripting (XSS) vulnerability that can be exploited to exfiltrate user data. This issue has been fixed in version 1.7.1.

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

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

It affects 1 product.


Products: Flintsh Flare.

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

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

## Is CVE-2026-26993 being exploited?

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

## Other vulnerabilities in FlintSH Flare

- [CVE-2026-30942](https://insights.sbomify.com/CVE-2026-30942/): Flare has a Path Traversal in /api/avatars/[filename] (high 8.3)
- [CVE-2026-30230](https://insights.sbomify.com/CVE-2026-30230/): Flare: Password‑Protected Thumbnail Bypass (high 8.2)
- [CVE-2026-30231](https://insights.sbomify.com/CVE-2026-30231/): Flare: Private File IDOR via raw/direct endpoints (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26993 is a medium-severity cross-site scripting vulnerability in FlintSH Flare, published on 20 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-26993 in the wild and no public exploit code.

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

## Sources

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

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