● Low · CVSS 2.2

How to Fix CVE-2026-29110: Information disclosure via error message in cryptomator

Q: What is the CVSS score for CVE-2026-29110?

2.2 (Low). Vector: `CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`.

Q: Where is the official advisory for CVE-2026-29110?

The vendor advisory is at [https://github.com/cryptomator/cryptomator/security/advisories/GHSA-j83j-mwhc-rcgw](https://github.com/cryptomator/cryptomator/security/advisories/GHSA-j83j-mwhc-rcgw). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29110.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-29110 is a information disclosure via error message in cryptomator cryptomator. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	2.2 (Low)
Actively exploited?	No public listing in CISA KEV
Affected	cryptomator < 1.19.0
Fixed in	See vendor advisory
Type (CWE)	CWE-209: Generation of Error Message Containing Sensitive Information

What is CVE-2026-29110?

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. The CVSS base score is 2.2 (Low). The official advisory is at https://github.com/cryptomator/cryptomator/security/advisories/GHSA-j83j-mwhc-rcgw.

Am I affected?

Check the version of cryptomator you are running and compare it against the Affected row above (cryptomator < 1.19.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s cryptomator 2>/dev/null | grep -i ^Version
rpm -q cryptomator 2>/dev/null
command -v cryptomator >/dev/null && cryptomator --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*cryptomator*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "cryptomator" 2>$null

How to fix CVE-2026-29110

Upgrade cryptomator to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade cryptomator
dpkg -s cryptomator | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh cryptomator -y
# or for older releases:
sudo yum update cryptomator -y
rpm -q cryptomator

SUSE / openSUSE


sudo zypper refresh
sudo zypper update cryptomator
rpm -q cryptomator

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-29110 affecting cryptomator
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-29110-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*cryptomator*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\cryptomator-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\cryptomator" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "cryptomator" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "cryptomator"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-29110 affecting cryptomator
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-29110-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s cryptomator 2>/dev/null | grep -i ^Version || echo "cryptomator not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q cryptomator || echo "cryptomator not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-29110-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/cryptomator /etc/cryptomator.d /etc/cryptomator.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y cryptomator
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y cryptomator
elif command -v yum >/dev/null; then
    yum update -y cryptomator
elif command -v zypper >/dev/null; then
    zypper --non-interactive update cryptomator
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s cryptomator 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q cryptomator
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-29110" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-29110"

Disable the affected service (Linux)


sudo systemctl stop cryptomator 2>/dev/null || true
sudo systemctl disable cryptomator 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s cryptomator 2>/dev/null | grep -i ^Version
rpm -q cryptomator 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*cryptomator*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-28342: Resource exhaustion in OliveTin — Resource exhaustion in OliveTin
How to Fix CVE-2026-44198: Improper Handling of Insufficient Permissions or Privileges in wagtail — Improper Handling of Insufficient Permissions or Privileges in wagtail
How to Fix CVE-2026-24904: Access Control Bypass in TrustTunnel , Access Control Bypass in TrustTunnel
How to Fix CVE-2026-0546: SQL Injection in Content Management System , SQL Injection in Content Management System
How to Fix CVE-2026-33633: Path Traversal in kitty , Path Traversal in kitty

Is CVE-2026-29110 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-29110?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

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

2.2 (Low). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N.

Where is the official advisory for CVE-2026-29110?

The vendor advisory is at https://github.com/cryptomator/cryptomator/security/advisories/GHSA-j83j-mwhc-rcgw. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29110.

References

Official vendor advisory: https://github.com/cryptomator/cryptomator/security/advisories/GHSA-j83j-mwhc-rcgw
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29110
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*