{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-29110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-29110 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-29110 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-29110 in the wild and no public exploit code.\n\nAffected product: cryptomator. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-29110/ (Markdown: https://insights.sbomify.com/CVE-2026-29110/index.md)","id":"CVE-2026-29110","markdown":"https://insights.sbomify.com/CVE-2026-29110/index.md","name":"CVE-2026-29110","record":{"aliases":["GHSA-j83j-mwhc-rcgw"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Cryptomator encryption tool","requires_auth":"low_privilege","summary":"An attacker with log file access can view cleartext file paths from failed operations, revealing metadata about encrypted vault contents.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cryptomator","vendor":"cryptomator"}],"cvss":{"score":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cryptomator: Leaking of cleartext paths into log file in non-debug mode","id":"CVE-2026-29110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"systemd: Local unprivileged user can trigger an assert","id":"CVE-2026-29111"},"packages":[],"prev":{"headline":"SuiteCRM Authenticated Remote Code Execution via Unsafe Deserialization in SavedSearch Filter Processing","id":"CVE-2026-29109"},"products":["cryptomator"],"published":"2026-03-06","related":[{"cvss_score":8.7,"headline":"Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes","id":"CVE-2026-32309","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2022-25366","kev_date_added":null,"published":"2022-02-19"},{"cvss_score":7.6,"headline":"Cryptomator: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32303","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.6,"headline":"Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32317","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.6,"headline":"Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32318","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7,"headline":"Cryptomator's MSI installer allows local privilege escalation","id":"CVE-2023-37907","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":5.5,"headline":"Cryptomator vulnerable to Local Elevation of Privileges","id":"CVE-2023-39520","kev_date_added":null,"published":"2023-08-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-06","vendors":["cryptomator"]},"summary":"An attacker with log file access can view cleartext file paths from failed operations, revealing metadata about encrypted vault contents.","url":"https://insights.sbomify.com/CVE-2026-29110/"}