p PatchFirst

CVE-2026-65629

CVE-2026-65629 · Weak PBKDF2 parameters for password-encrypted private-key export in jose

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Use of Password Hash With Insufficient Computational Effort in the jose library allows an attacker who obtains a password-encrypted private-key export to recover the private key through an offline password-cracking attack. When jose exports a password-encrypted private key with jose_jwk:to_der/2 (JOSE.JWK.to_der/2), the jose_jwk_der:to_binary/3 function in src/jwk/jose_jwk_der.erl serializes the key as a PKCS#8 EncryptedPrivateKeyInfo using the PBES2 scheme with hardcoded key-derivation parameters: PBKDF2-HMAC-SHA256 with an iteration count of 2048 and an 8-byte (64-bit) random salt. Neither value can be overridden by the caller. Both values are far below current guidance (OWASP recommends on the order of 600,000 iterations for PBKDF2-HMAC-SHA256, and NIST recommends salts of at least 128 bits), so the key-stretching work factor is roughly 300 times lower than intended and the short salt reduces the cost of precomputation across keys. The symmetric encryption (AES-256-CBC with a 16-byte random IV) is not affected; the weakness is entirely in the derivation strength. An attacker who obtains one of these exported blobs (for example from a backup, configuration repository, object storage, or logs) can mount a cheap offline dictionary or brute-force attack against the export password, and success yields the full private key. This issue affects jose: from 1.10.0 before 1.11.13.

CVSS 7.4 · High · EPSS 0.1% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • jose

    Versions
    • ≥ 1.10.0, < 1.11.13: Affected (semver)

    Update to 1.11.13

  • jose

    Versions
    • ≥ 85fddd89ee56b6f9c19eff7d9cfffeef62c330b9, < 461b261902531ca016190e780bb70862d561a7e0: Affected (git)

    No fix published

  • erlang-jose Debian:12

    Versions
    • 1.11.10-1
    • 1.11.10-1~bpo12+1
    • 1.11.12-1
    • 1.11.12-1.1
    • 1.11.12-2
    • 1.11.12-2~bpo13+1
    • 1.11.12-3
    • 1.11.12-3~bpo13+1
    • 1.11.5-1
    • 1.11.6-1
    • 1.11.6-1~bpo12+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • erlang-jose Debian:13

    Versions
    • 1.11.10-1
    • 1.11.12-1
    • 1.11.12-1.1
    • 1.11.12-2
    • 1.11.12-2~bpo13+1
    • 1.11.12-3
    • 1.11.12-3~bpo13+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • erlang-jose Debian:14

    Versions
    • 1.11.10-1
    • 1.11.12-1
    • 1.11.12-1.1
    • 1.11.12-2
    • 1.11.12-2~bpo13+1
    • 1.11.12-3
    • 1.11.12-3~bpo13+1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:18.04:LTS

    Versions
    • 10-2
    • 10-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:20.04:LTS

    Versions
    • 10-2build2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:22.04:LTS

    Versions
    • 10-3
    • 11-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:24.04:LTS

    Versions
    • 11-2
    • 11-3
    • 11-3build1
    • 11-3build2
    • 13-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:26.10

    Versions
    • 14-2build1
    • 14-2build2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • jose Ubuntu:26.04:LTS

    Versions
    • 14-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →