Vulnerability Database · npm · jsrsasign · Version
jsrsasign 7.1.2
7.1.2 is affected by 14 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 4 High 7 Medium 2 Low 1 Unrated 0
-
Released 20 Mar 2017
Status deprecated release
Licence MIT
Also known from other sources 0
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.
01 Vulnerabilities affecting this version
jsrsasign 7.1.2 vulnerabilities
14 vulnerabilities cover jsrsasign 7.1.2. Scroll the table for all of them, or open the full list in the database.
Looking for another version, or everything Vulert holds for jsrsasign?
Questions
About jsrsasign 7.1.2
Is jsrsasign 7.1.2 vulnerable?
Yes. 14 vulnerabilities in the Vulert database cover jsrsasign 7.1.2: 4 critical, 7 high, 2 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 7.1.2?
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 7.1.2 the latest release of jsrsasign?
No. 7.1.2 was published 20 Mar 2017, 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.