Invalid RSA PKCS#1 v1.5 Signatures Vulnerability in jsrsasign

jsrsasign Updated 02 Oct 2025

Summary

09/02/2022
MODERATE
Yes i
Moderate
Not published

GHSA-h87q-g2wp-47pj: Signatures are mistakenly recognized to be valid in jsrsasign. Affects jsrsasign versions < 10.2.0. Fixed in 10.2.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

jsrsasign is a Node.js package that provides a JavaScript implementation of various cryptographic functions and standards. It is commonly used for generating and verifying digital signatures, encrypting and decrypting data, and working with X.509 certificates. The package is widely adopted in applications that require secure communication and authentication. However, a vulnerability has been discovered in versions prior to 10.2.0 that mistakenly recognizes some invalid RSA PKCS#1 v1.5 signatures as valid.

Vulnerability Detail

The vulnerability in jsrsasign allows for the acceptance of invalid RSA PKCS#1 v1.5 signatures as valid. This means that an attacker could potentially create a malicious signature that is incorrectly recognized as authentic, leading to various security issues. While there are no known practical attacks exploiting this vulnerability, it still poses a risk to the integrity and authenticity of cryptographic operations relying on RSA PKCS#1 v1.5 signatures.

How To Fix

Latest published version: 11.1.5 as of 23 Oct 2026

npm install jsrsasign@11.1.5

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

10.2.0

This is the first release that contains the fix.

npm install jsrsasign@10.2.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of the package to mitigate the risk.

Conclusion

The vulnerability in jsrsasign that allows for the acceptance of invalid RSA PKCS#1 v1.5 signatures as valid poses a risk to the integrity and authenticity of cryptographic operations. It is crucial to update the package to version 10.2.0 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for jsrsasign →

Share this vulnerability

FAQ

jsrsasign is a Node.js package that provides a JavaScript implementation of various cryptographic functions and standards. It is commonly used for generating and verifying digital signatures, encrypting and decrypting data, and working with X.509 certificates.

The vulnerability allows for the acceptance of invalid RSA PKCS#1 v1.5 signatures as valid, potentially compromising the integrity and authenticity of cryptographic operations relying on such signatures.

No, there are no known practical attacks exploiting this vulnerability at the moment.

To fix this vulnerability, update the jsrsasign package to version 10.2.0 or later.

No, there is no known workaround. Updating to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for jsrsasign.

How To Fix

Latest published version: 11.1.5 as of 23 Oct 2026

npm install jsrsasign@11.1.5

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

10.2.0

This is the first release that contains the fix.

npm install jsrsasign@10.2.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback