JS
Product
Jsrsasign
12
CVEs
0
On KEV
9.8
Max CVSS
0
New 30D
Severity mix
Critical 7High 3Medium 2Low 0
Watch
Add Jsrsasign to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2022-25898 | 9.8 | Jul 1 | 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… Affected: 4.8.0 before 10.5.25 |
| CVE-2020-14968 | 9.8 | Jun 22 | An issue was discovered in the jsrsasign package before 8.0.17 for Node.js Affected: before 8.0.17 |
| CVE-2020-14967 | 9.8 | Jun 22 | An issue was discovered in the jsrsasign package before 8.0.18 for Node.js Affected: before 8.0.18 |
| CVE-2026-4601 | 9.1 | Mar 23 | 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 Affected: before 11.1.1 |
| CVE-2026-4599 | 9.1 | Mar 23 | 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… Affected: 7.0.0 before 11.1.1 |
| CVE-2026-4600 | 9.1 | Mar 23 | Versions of the package jsrsasign before 11.1.1 are vulnerable to Improper Verification of Cryptographic Signature via the DSA domain-parameter validation in… Affected: before 11.1.1 |
| CVE-2021-30246 | 9.1 | Apr 7 | In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid Affected: through 10.1.13 |
Showing 7