Nixpkgs security tracker

Login with GitHub

Details of issue NIXPKGS-2026-0728

NIXPKGS-2026-0728
published 3 months ago
updated 3 months ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored package cryptomator-cli
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes

Cryptomator encrypts data being stored on cloud infrastructure. Prior to version 1.19.1, the Hub-based unlock flow explicitly supports hub+http and consumes Hub endpoints from vault metadata without enforcing HTTPS. As a result, a vault configuration can drive OAuth and key-loading traffic over plaintext HTTP or other insecure endpoint combinations. An active network attacker can tamper with or observe this traffic. Even when the vault key is encrypted for the device, bearer tokens and endpoint-level trust decisions are still exposed to downgrade and interception. This issue has been patched in version 1.19.1.

Affected products

cryptomator
  • ==< 1.19.1

Matching in nixpkgs

Ignored packages (1)

pkgs.cryptomator-cli

Command line program to access encrypted Cryptomator vaults

Package maintainers

Upstream advisory: https://github.com/cryptomator/cryptomator/security/advisories/GHSA-vv33-h7qx-c264