What is the CVSS score of CVE-2026-29110?

CVE-2026-29110 has a CVSS 3.1 base score of 2.2 (Low). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Cryptomator are affected by CVE-2026-29110?

CVE-2026-29110 is a low-severity vulnerability (CVSS 2.2). The limited severity suggests constrained impact, typically requiring specific conditions or local access for exploitation.

How to fix or mitigate CVE-2026-29110?

During next maintenance window: Apply vendor patches when convenient. Monitor vendor channels for updates.

Cryptomator CVE-2026-29110

LOW

Error Message Information Leak (CWE-209)

2026-03-06 security-advisories@github.com

Information Disclosure Cryptomator

2.2

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

2.2 LOW

AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 22:06 vuln.today

CVE Published

Mar 06, 2026 - 18:16 nvd

LOW 2.2

DescriptionGitHub Advisory

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.

AnalysisAI

Technical ContextAI

This vulnerability (CWE-209: Error Message Information Leak) affects Cryptomator encrypts data being stored on cloud infrastructure.. 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.