dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-62294

MEDIUM · 5.1 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Flameshot before version 14.0.0 had a TOCTOU (time-of-check to time-of-use) vulnerability in its 'Open With' feature. The feature wrote screenshots to a predictable temporary path and followed symlinks, allowing a local unprivileged attacker to pre-plant a symlink that would cause Flameshot to overwrite any file the victim user could write with PNG data.

MitigationUpgrade Flameshot to version 14.0.0 or later, which implements non-predictable temporary paths and stops following symlinks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Flameshot is installed
    Run 'flameshot --version' or check package manager (dpkg -l | grep flameshot, rpm -q flameshot)
    Affected if Flameshot is not found on the system - not affected
  2. Check installed Flameshot version
    Execute 'flameshot --version' and compare the version number to 14.0.0
    Affected if Version is lower than 14.0.0 (e.g., 13.x, 12.x, etc.)
  3. Identify Open With feature configuration
    Check for config file at ~/.config/flameshot/flameshot.ini or look for 'openWith' entries in the configuration
    Affected if Configuration file exists with Open With feature settings present
  4. Check for historically predictable temp file behavior
    Review any existing screenshots or temporary directories in /tmp for patterns matching 'flameshot' with predictable naming (note: this may not show current activity)
    Affected if Temp files show predictable naming patterns rather than random UUIDs

The environment is affected if Flameshot version is below 14.0.0 and the Open With feature is configured or used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Flameshot to version 14.0.0 or later, which implements non-predictable temporary paths and stops following symlinks.

Recommended fix Moderate confidence

14.0.0

  1. Upgrade Flameshot to version 14.0.0 or later. For most Linux distributions, this can be done via the package manager (e.g., `sudo apt update && sudo apt install flameshot` on Debian/Ubuntu, or `sudo dnf update flameshot` on Fedora). Verify the installed version with `flameshot --version` after upgrading to confirm the fix is applied.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-62294 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data