# CVE-2026-29110: Cryptomator: Leaking of cleartext paths into log file in non-debug mode

> An attacker with log file access can view cleartext file paths from failed operations, revealing metadata about encrypted vault contents.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-j83j-mwhc-rcgw

## What is CVE-2026-29110?

CVE-2026-29110 is a low-severity vulnerability in cryptomator, published on 6 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cryptomator 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.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Cryptomator Cryptomator.

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

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

## Is CVE-2026-29110 being exploited?

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

## Other vulnerabilities in cryptomator

- [CVE-2026-32309](https://insights.sbomify.com/CVE-2026-32309/): Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes (high 8.7)
- [CVE-2022-25366](https://insights.sbomify.com/CVE-2022-25366/): Code injection in n/a (high 7.8)
- [CVE-2026-32303](https://insights.sbomify.com/CVE-2026-32303/): Cryptomator: Tampered vault configuration allows MITM attack on Hub API (high 7.6)
- [CVE-2026-32317](https://insights.sbomify.com/CVE-2026-32317/): Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API (high 7.6)
- [CVE-2026-32318](https://insights.sbomify.com/CVE-2026-32318/): Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29110 is a low-severity vulnerability in cryptomator, published on 6 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-29110 in the wild and no public exploit code.

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

## Sources

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

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