CVE-2026-29110
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 · uneditedCryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.0, in non-debug mode Cryptomator might leak cleartext paths into the log file. This can reveal meta information about the files stored inside a vault at a time, where the actual vault is closed. Not every cleartext path is logged. Only if a filesystem request fails for some reason (e.g. damaged encrypted file, not existing file), a log message is created. This issue has been patched in version 1.19.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 confidenceCryptomator versions before 1.19.0 leak cleartext file paths into log files when filesystem operations fail (e.g., damaged encrypted files or missing files), revealing metadata about vault contents even when the vault is closed. This occurs only in non-debug mode.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.19.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Cryptomator versionOpen Cryptomator and go to About (Help > About on Windows, Cryptomator > About on macOS) to see the installed version numberAffected if Version is below 1.19.0
-
Verify logging is enabled in non-debug modeCheck if debug mode is disabled in Cryptomator settings (Settings > General > Debug mode should be unchecked)Affected if Debug mode is disabled (this is the default and required for the vulnerability)
-
Locate Cryptomator log filesFind log files in the default location: Windows: %APPDATA%/Cryptomator/logs/, macOS: ~/Library/Application Support/Cryptomator/logs/, Linux: ~/.config/Cryptomator/logs/Affected if Log files exist in these directories
-
Inspect log files for cleartext file pathsOpen the most recent log files and search for paths that appear to be cleartext (unencrypted) filenames, especially entries containing 'failed to read' or 'file not found' error messagesAffected if Log files contain any readable file paths that correspond to files inside your vault
You are affected if Cryptomator version is below 1.19.0, debug mode is disabled, and log files contain cleartext file paths from vault operations
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.19.0
Upgrade Cryptomator to version 1.19.0 or later to patch the vulnerability. Review existing log files for any exposed cleartext paths.
1.19.0
- Check current Cryptomator version (Help > About or application settings)
- Download Cryptomator version 1.19.0 or later from the official GitHub repository (github.com/cryptomator/cryptomator)
- Install the downloaded version, overwriting the existing installation
- Verify the upgrade was successful by checking the version number in About/Help section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29110 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29110 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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