VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jsrsasign: vulnerability history, versions and safety

jsrsasign is a package in the npm ecosystem. Vulert records 14 vulnerabilities for it across 115 releases, from Jun 2020 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C4 H7 M2 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 23 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jsrsasign vulnerabilities

Vulert verdict on jsrsasign 11.1.5 i

Updated on 22 Oct 2026

Good news: 11.1.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 14.

Package health score 42/100
  • Security Unfixed issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

What to do: Stay on 11.1.5 or newer. This can change: a vulnerability disclosed tomorrow can affect 11.1.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 11.1.5 — unaffected i
  • Vulnerabilities on record 14 over 5 years · 6 in the last year i
  • Latest disclosure 23 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 516 packages i
  • Stars 3,370 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for jsrsasign, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
11.1.5 14 Aug 2026 none MIT — Details →
11.1.4 14 Aug 2026 none MIT — Details →
11.1.3 17 Apr 2026 none MIT — Details →
11.1.2 12 Apr 2026 none MIT — Details →
11.1.1 20 Feb 2026 none MIT — Details →
11.1.0 01 Feb 2024 C1 H4 L1 MIT Yes Details →
11.0.0 16 Jan 2024 C1 H4 L1 MIT Yes Details →
10.9.0 27 Nov 2023 C1 H5 L1 MIT Yes Details →
10.8.6 26 Apr 2023 C1 H5 L1 MIT Yes Details →
10.8.5 26 Apr 2023 C1 H5 L1 MIT Yes Details →
10.8.4 26 Apr 2023 C1 H5 L1 MIT Yes Details →
10.8.3 19 Apr 2023 C1 H5 L1 MIT Yes Details →
10.8.2 15 Apr 2023 C1 H5 L1 MIT Yes Details →
10.8.1 09 Apr 2023 C1 H5 L1 MIT Yes Details →
10.8.0 08 Apr 2023 C1 H5 L1 MIT Yes Details →
10.7.0 12 Mar 2023 C1 H5 L1 MIT Yes Details →
10.6.1 20 Nov 2022 C1 H5 L1 MIT Yes Details →
10.6.0 04 Nov 2022 C1 H5 L1 MIT Yes Details →
10.5.27 19 Aug 2022 C1 H5 L1 MIT Yes Details →
10.5.26 14 Jul 2022 C1 H5 L1 MIT Yes Details →
10.5.25 23 Jun 2022 C1 H5 L1 MIT Yes Details →
10.5.24 04 Jun 2022 C1 H6 L1 MIT Yes Details →
10.5.23 27 May 2022 C1 H6 L1 MIT Yes Details →
10.5.22 23 May 2022 C1 H6 L1 MIT Yes Details →
10.5.21 23 May 2022 C1 H6 L1 MIT Yes Details →
10.5.20 25 Apr 2022 C1 H6 L1 MIT Yes Details →
10.5.19 23 Apr 2022 C1 H6 L1 MIT Yes Details →
10.5.18 22 Apr 2022 C1 H6 L1 MIT Yes Details →
10.5.17 14 Apr 2022 C1 H6 L1 MIT Yes Details →
10.5.16 08 Apr 2022 C1 H6 L1 MIT Yes Details →
10.5.15 06 Apr 2022 C1 H6 L1 MIT Yes Details →
10.5.14 28 Mar 2022 C1 H6 L1 MIT Yes Details →
10.5.13 18 Mar 2022 C1 H6 L1 MIT Yes Details →
10.5.12 13 Mar 2022 C1 H6 L1 MIT Yes Details →
10.5.11 12 Mar 2022 C1 H6 L1 MIT Yes Details →
10.5.10 10 Mar 2022 C1 H6 L1 MIT Yes Details →
10.5.9 09 Mar 2022 C1 H6 L1 MIT Yes Details →
10.5.8 24 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.7 18 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.6 16 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.5 16 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.4 15 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.3 10 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.2 08 Feb 2022 C1 H6 L1 MIT Yes Details →
10.5.1 01 Dec 2021 C1 H6 L1 MIT Yes Details →
10.5.0 21 Nov 2021 C1 H6 L1 MIT Yes Details →
10.4.1 30 Sep 2021 C1 H6 L1 MIT Yes Details →
10.4.0 17 Aug 2021 C1 H6 L1 MIT Yes Details →
10.3.2 15 Aug 2021 C1 H6 L1 MIT Yes Details →
10.3.0 01 Jun 2021 C1 H6 L1 MIT Yes Details →
10.2.0 13 Apr 2021 C1 H6 L1 MIT Yes Details →
10.1.13 07 Mar 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.12 25 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.11 19 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.10 14 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.9 12 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.8 08 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.7 08 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.6 08 Feb 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.5 17 Jan 2021 C2 H6 M1 L1 MIT Yes Details →
10.1.4 23 Nov 2020 C2 H6 M1 L1 MIT Yes Details →
10.1.3 22 Nov 2020 C2 H6 M1 L1 MIT Yes Details →
10.1.2 20 Nov 2020 C2 H6 M1 L1 MIT Yes Details →
10.1.1 20 Nov 2020 C2 H6 M1 L1 MIT Yes Details →
10.1.0 19 Nov 2020 C2 H6 M1 L1 MIT Yes Details →
10.0.5 04 Nov 2020 C2 H6 M1 L1 MIT Yes Details →
10.0.4 23 Oct 2020 C2 H6 M1 L1 MIT Yes Details →
10.0.3 20 Oct 2020 C2 H6 M1 L1 MIT Yes Details →
10.0.2 14 Oct 2020 C2 H6 M1 L1 MIT Yes Details →
10.0.1 13 Oct 2020 C2 H6 M1 L1 MIT Yes Details →
10.0.0 24 Sep 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.9 08 Sep 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.8 08 Sep 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.7 08 Sep 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.6 05 Sep 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.5 29 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.4 28 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.3 27 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.2 27 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.1 26 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.1.0 24 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.0.3 22 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.0.2 21 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.0.1 21 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
9.0.0 19 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.24 18 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.23 06 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.22 04 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.21 01 Aug 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.20 24 Jun 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.19 22 Jun 2020 C2 H6 M1 L1 MIT Yes Details →
8.0.18 20 Jun 2020 C2 H7 M1 L1 MIT Yes Details →
8.0.17 19 Jun 2020 C3 H7 M1 L1 MIT Yes Details →
8.0.16 31 May 2020 C4 H7 M1 L1 MIT Yes Details →
8.0.15 13 Apr 2020 C4 H7 M1 L1 MIT Yes Details →
8.0.14 11 Apr 2020 C4 H7 M1 L1 MIT Yes Details →
8.0.13 31 Mar 2020 C4 H7 M1 L1 MIT Yes Details →
8.0.12 22 Apr 2018 C4 H7 M2 L1 MIT Yes Details →
8.0.11 17 Apr 2018 C4 H7 M2 L1 MIT Yes Details →
8.0.10 10 Apr 2018 C4 H7 M2 L1 MIT Yes Details →
8.0.9 04 Apr 2018 C4 H7 M2 L1 — Yes Details →
8.0.8 01 Apr 2018 C4 H7 M2 L1 — Yes Details →
8.0.7 25 Mar 2018 C4 H7 M2 L1 — Yes Details →
8.0.6 09 Feb 2018 C4 H7 M2 L1 — Yes Details →
8.0.5 27 Jan 2018 C4 H7 M2 L1 — Yes Details →
8.0.4 14 Sep 2017 C4 H7 M2 L1 — Yes Details →
8.0.3 10 Jul 2017 C4 H7 M2 L1 — Yes Details →
8.0.2 08 Jul 2017 C4 H7 M2 L1 — Yes Details →
8.0.1 30 Jun 2017 C4 H7 M2 L1 — Yes Details →
8.0.0 29 Jun 2017 C4 H7 M2 L1 — Yes Details →
7.2.2 25 Jun 2017 C4 H7 M2 L1 — Yes Details →
7.2.1 04 Jun 2017 C4 H7 M2 L1 — Yes Details →
7.2.0 21 May 2017 C4 H7 M2 L1 — Yes Details →
7.1.5 07 May 2017 C4 H7 M2 L1 — Yes Details →
7.1.3 16 Apr 2017 C4 H7 M2 L1 — Yes Details →
7.1.2 20 Mar 2017 C4 H7 M2 L1 — Yes Details →
7.1.1 13 Mar 2017 C4 H7 M2 L1 — Yes Details →
7.1.0 22 Jan 2017 C4 H7 M2 L1 — Yes Details →
7.0.0 25 Dec 2016 C4 H7 M2 L1 — Yes Details →
6.2.3 29 Nov 2016 C3 H7 M2 L1 — Yes Details →

The newest 120 of 156 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4
  • 2021 1
  • 2022 2
  • 2024 1
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for jsrsasign

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-14967: RSA PKCS#1 decryption vulnerability in jsrsasign 9.8 critical 8.0.18 26 Jun 2020
CVE-2020-14968: RSA-PSS signature validation vulnerability in jsrsasign 9.8 critical 8.0.17 26 Jun 2020
CVE-2026-4599: jsrsasign Critical Vulnerability in DSA Nonce Generation 9.1 critical 11.1.1 23 Mar 2026
CVE-2021-30246: RSA signature validation vulnerability in jsrsasign 9.1 critical 10.2.0 16 Apr 2021
CVE-2026-4601: jsrsasign Vulnerability Allows Private Key Extraction via DSA Signing 8.7 high 11.1.1 23 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About jsrsasign

Is jsrsasign safe to use?

Vulert records 14 vulnerabilities for jsrsasign in npm: 4 critical, 7 high, 2 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is jsrsasign's Vulert package health score?

Vulert scores jsrsasign 42/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of jsrsasign affected?

No. 11.1.5, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of jsrsasign should I use?

11.1.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does jsrsasign have?

14 vulnerabilities are recorded for jsrsasign in the npm ecosystem: 4 critical, 7 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jsrsasign vulnerabilities disclosed?

6 vulnerabilities were recorded for jsrsasign in the last 12 months, and the oldest entry in this database dates to 26 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of jsrsasign are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor jsrsasign for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jsrsasign version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.