# CVE-2026-62294: Flameshot: OCTOU symlink attack via predictable /tmp path in Flameshot "Open With"

> A local attacker can exploit a race condition in the Open With feature to overwrite arbitrary files via symlink attacks.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-62294, GHSA-fqqf-4rj8-c392, UBUNTU-CVE-2026-62294

## What is CVE-2026-62294?

CVE-2026-62294 is a medium-severity vulnerability in flameshot-org flameshot, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Flameshot is powerful yet simple to use screenshot software. Prior to 14.0.0, the Open With feature wrote screenshots to a predictable temporary path and followed symlinks, creating a time-of-check to time-of-use race that allowed a local unprivileged attacker on the same machine to pre-plant a symlink and cause Flameshot to write PNG data through it, overwriting any file the victim user could write. This issue is fixed in version 14.0.0.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-62294 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62294 is a medium-severity vulnerability in flameshot-org flameshot, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62294 in the wild and no public exploit code.

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

## Sources

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

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