Cleartext path disclosure via failed-request logging
Published Mar 6, 2026 · Updated Mar 6, 2026
Information disclosure in Cryptomator before 1.19.0 allows local users to read cleartext vault paths from application logs. In non-debug mode, failed filesystem requests write some cleartext file or directory paths to the persistent log instead of keeping those names opaque. Exploitation requires access to the affected account's log files and a request failure, and the exposed metadata remains available after the vault is closed.
Summary
What happened
Information disclosure in Cryptomator before 1.19.0 allows local users to read cleartext vault paths from application logs. In non-debug mode, failed filesystem requests write some cleartext file or directory paths to the persistent log instead of keeping those names opaque. Exploitation requires access to the affected account's log files and a request failure, and the exposed metadata remains available after the vault is closed.
The record
- CVE
- CVE-2026-29110
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- Cryptomator
- Product
- Cryptomator
- Classifications
- CWE-209, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.19.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo