CVE-2026-65629 potatosalad CVE debrief

Who should care

Defenders who use the jose library, specifically those who manage private keys, should prioritize verifying and upgrading to a fixed version of the library and review and update their private key management practices.

Why it matters

CVE-2026-65629 is a high-severity vulnerability in the jose library that allows an attacker to recover a private key through an offline password-cracking attack if they obtain a password-encrypted private-key export. Defenders should prioritize verifying and upgrading to a fixed version of the library and review and update their private key management practices.

• Private key recovery through offline password-cracking attacks
• Potential unauthorized access to encrypted data
• Need for verification and upgrade to a fixed library version
• Review and update of private key management practices

Technical summary

The jose library uses a password hash with insufficient computational effort, allowing an attacker to recover a private key through an offline password-cracking attack if they obtain a password-encrypted private-key export. This is due to hardcoded key-derivation parameters: PBKDF2-HMAC-SHA256 with an iteration count of 2048 and an 8-byte random salt, which are significantly below current security guidance. An attacker who obtains one of these exported blobs can mount a cheap offline dictionary or brute-force attack against the export password, and success yields the full private key. The symmetric encryption (AES-256-CBC with a 16-byte random IV) is not affected; the weakness is entirely in the derivation

Defensive priority

Defenders should prioritize verifying and upgrading to a fixed version of the jose library, specifically version 1.11.13 or later, and review and update their private key management practices.

Recommended defensive actions

• Verify and upgrade to a fixed version of the jose library
• Review and update private key management practices
• Monitor for and respond to potential password-cracking attacks
• Implement compensating controls for exposed systems
• Conduct an exposure review for affected assets
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is caused by the use of a password hash with insufficient computational effort in the jose library, specifically with hardcoded key-derivation parameters: PBKDF2-HMAC-SHA256 with an iteration count of 2048 and an 8-byte random salt.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.