Jsrsasign vulnerabilities
We track 6 vulnerabilities in Jsrsasign products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on March 23, 2026.
Latest Jsrsasign vulnerabilities
- 7.5 High severity
jsrsasign: Incorrect Conversion between Numeric Types
Versions of the package jsrsasign before 11.1.1 are vulnerable to Incorrect Conversion between Numeric Types due to handling negative exponents in ext/jsbn2.js. An attacker can force the computation of incorrect modular inverses and break signature verificatio
- 9.1 Critical severity
jsrsasign: Missing Cryptographic Step
Versions of the package jsrsasign before 11.1.1 are vulnerable to Missing Cryptographic Step via the KJUR.crypto.DSA.signWithMessageHash process in the DSA signing implementation. An attacker can recover the private key by forcing r or s to be zero, so the lib
- 9.1 Critical severity
jsrsasign: Improper Verification of Cryptographic Signature
Versions of the package jsrsasign before 11.1.1 are vulnerable to Improper Verification of Cryptographic Signature via the DSA domain-parameter validation in KJUR.crypto.DSA.setPublic (and the related DSA/X509 verification flow in src/dsa-2.0.js). An attacker
- 9.1 Critical severity
jsrsasign: Incomplete Comparison with Missing Factors
Versions of the package jsrsasign from 7.0.0 and before 11.1.1 are vulnerable to Incomplete Comparison with Missing Factors via the getRandomBigIntegerZeroToMax and getRandomBigIntegerMinToMax functions in src/crypto-1.1.js; an attacker can recover the private
- 7.5 High severity
jsrsasign: Loop with Unreachable Exit Condition
Versions of the package jsrsasign before 11.1.1 are vulnerable to Infinite loop via the bnModInverse function in ext/jsbn2.js when the BigInteger.modInverse implementation receives zero or negative inputs, allowing an attacker to hang the process permanently b
- 9.8 Critical severity
jsrsasign: Improper Verification of Cryptographic Signature
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT signature with non Base64URL encoding special characters or number escaped characters may be validated as valid by mistake. Workaround: Vali