Is CVE-2026-65629 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-65629 being exploited in the wild.

How severe is CVE-2026-65629?

Informational severity, published 26 October 2026.

Is there a fix for CVE-2026-65629?

Yes: fixed in 1.11.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-65629 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-65629?

Check whether you run JOSE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-65629: JOSE library weak password hashing in encrypted key export

CVE-2026-65629 · Severity: info · Published 2026-10-26

JOSE is a library that handles cryptographic keys and digital signatures. When exporting password-protected private keys, JOSE uses weak password-stretching settings that are roughly 300 times below current security standards. An attacker who gains access to an exported key file from backups, configuration repositories, or logs can easily crack the password offline and steal the private key.

Technologies: JOSE. Vendors: Jose.

Quick answers

Is CVE-2026-65629 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-65629 being exploited in the wild.
How severe is CVE-2026-65629?: Informational severity, published 26 October 2026.
Which products and versions are affected?: JOSE 1.10.0 to before 1.11.13.
Is there a fix for CVE-2026-65629?: Yes: fixed in 1.11.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65629 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-65629?: Check whether you run JOSE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.11.13

Technical details

The jose_jwk_der:to_binary/3 function in JOSE uses PBKDF2-HMAC-SHA256 with only 2048 iterations (vs. 600000+ recommended) and an 8-byte salt (vs. 128-bit recommended) when exporting password-encrypted PKCS#8 keys. An unauthenticated attacker with access to an exported key blob can perform a dictionary or brute-force attack against the password; successful cracking yields the full private key. A fix is available in version 1.11.13.

Affected products

jose JOSE 1.10.0 to before 1.11.13

Timeline

2026-10-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.