CVE-2026-4599 Kjur CVE debrief

Who should care

Developers and security teams using the jsrsasign package in their applications, especially those relying on DSA signatures for cryptographic operations, should be aware of this vulnerability. The exposure of private keys can lead to severe security breaches, including unauthorized access and data tampering. Immediate action is required to update vulnerable versions and limit potential exposure.

Technical summary

The vulnerability in jsrsasign arises from flawed compareTo checks in the getRandomBigIntegerZeroToMax and getRandomBigIntegerMinToMax functions. These functions are used in DSA signature generation, and the bias introduced by the incorrect comparisons can be exploited to recover the private key. The issue is particularly severe as it directly impacts the cryptographic integrity of the package, allowing for potential private key recovery and subsequent impersonation or decryption of sensitive data.

Defensive priority

High priority due to potential for private key recovery and severe security breaches

Recommended defensive actions

• Update jsrsasign to version 11.1.1 or later
• Review and replace any instances of vulnerable jsrsasign versions in applications
• Monitor for any suspicious DSA signature generation activities
• Implement compensating controls to limit exposure until patching can be completed
• Inventory applications and services using jsrsasign for immediate remediation

Evidence notes

The CVE-2026-4599 vulnerability is confirmed in jsrsasign versions from 7.0.0 to before 11.1.1. Evidence from the NVD and Snyk indicates that the flaw is due to incorrect compareTo checks in specific functions, leading to biased DSA nonces. Users should verify their package versions and update to a secure version to prevent potential private key recovery attacks.

Official resources