jsrsasign Known Vulnerabilities & Fixes
jsrsasign has 2 known security vulnerabilities in npm (Node.js). Upgrade to version 11.1.1 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 11.1.1
Upgrading to 11.1.1 or later resolves all 2 known vulnerabilities in jsrsasign. Run: npm install jsrsasign@11.1.1
Is jsrsasign in your project?
Check if you're affected and upgrade to 11.1.1 to stay secure.
Security Summary
- 2 affected version ranges have been identified across these 2 advisories.
- 100% of known issues have a published fixed version.
- Remediation: npm update jsrsasign
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-4599 jsrsasign: Incomplete Comparison Allows DSA Private Key Recovery via Biased Nonce Generation | CRITICAL | All versions | 11.1.1 |
| CVE-2026-4601 jsrsasign: Missing cryptographic validation during DSA signing enables private key extraction | HIGH | All versions | 11.1.1 |
About This Data
Vulnerability data for jsrsasign is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related npm (Node.js) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of jsrsasign.