Vulnerability Database · npm · jsrsasign · Version

jsrsasign 10.1.5

10.1.5 is affected by 10 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 11.1.5.

Critical 2 High 6 Medium 1 Low 1 Unrated 0

Released 17 Jan 2021 Status deprecated release Licence MIT Also known from other sources 10 Newer releases 156 Database updated 23/Oct/2026

Release and licence data published by the npm registry. 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.

Looking for another version, or everything Vulert holds for jsrsasign?

All versions → Full vulnerability list →

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 10.1.5

Is jsrsasign 10.1.5 vulnerable?

Yes. 10 vulnerabilities in the Vulert database cover jsrsasign 10.1.5: 2 critical, 6 high, 1 medium and 1 low. The upgrade Vulert recommends is 11.1.5, and each entry above names the fixed version to move to.

Which version of jsrsasign should I use instead of 10.1.5?

11.1.5 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 10.1.5 the latest release of jsrsasign?

No. 10.1.5 was published 17 Jan 2021, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.