Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

GHSA-w8q8-93cx-6h7r jsrsasign

HIGHFix: kjur/jsrsasign#645

GHSA-w8q8-93cx-6h7r is a high-severity (CVSS 8.7) CWE-325 vulnerability in jsrsasign. A fix is available for jsrsasign — see the affected versions and patch details below.

jsrsasign: Missing cryptographic validation during DSA signing enables private key extraction

Also known asCVE-2026-4601
Published
Mar 23, 2026
Updated
Mar 29, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w8q8-93cx-6h7r.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-w8q8-93cx-6h7r plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

jsrsasignnpm
991Kdownloads / week

Description

Versions of the package jsrsasign before 11.1.1 are vulnerable to Missing Cryptographic Step via the KJUR.crypto.DSA.signWithMessageHash process in the DSA signing implementation. An attacker can recover the private key by forcing r or s to be zero, so the library emits an invalid signature without retrying, and then solves for x from the resulting signature.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjsrsasignall versions11.1.1npm install jsrsasign@11.1.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jsrsasign, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update jsrsasign to 11.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8q8-93cx-6h7r is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w8q8-93cx-6h7r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w8q8-93cx-6h7r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

IMPORTANT: A flaw in the jsrsasign library allows for private key recovery due to a missing cryptographic step in the Digital Signature Algorithm (DSA) signing process. An attacker can manipulate signature generation within the KJUR.crypto.DSA.signWithMessageHash function to force specific values, enabling the…

ProductFixed inAdvisory
Migration Toolkit for Virtualization 2.1migration-toolkit-virtualization/mtv-console-plugin-rhel9:1779139872RHSA-2026:19409
Migration Toolkit for Virtualization 2.9migration-toolkit-virtualization/mtv-console-plugin-rhel9:1778927462RHSA-2026:19410
Red Hat Quay 3.10quay/quay-rhel8:1775169155RHSA-2026:6912
Red Hat Quay 3.12quay/quay-rhel8:1775253092RHSA-2026:6720
Red Hat Quay 3.15quay/quay-rhel8:1775169219RHSA-2026:6568
Red Hat Quay 3.16quay/quay-rhel9:1779204086RHSA-2026:19375
Red Hat Quay 3.9quay/quay-rhel8:1775169218RHSA-2026:6926

Frequently Asked Questions

Versions of the package jsrsasign before 11.1.1 are vulnerable to Missing Cryptographic Step via the KJUR.crypto.DSA.signWithMessageHash process in the DSA signing implementation. An attacker can recover the private key by forcing r or s to be zero, so the library emits an invalid signature without retrying, and then solves for x from the resulting signature.
O3 Security · Impact-Aware SCA

Is GHSA-w8q8-93cx-6h7r in your dependencies?

O3 Security finds GHSA-w8q8-93cx-6h7r across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-w8q8-93cx-6h7r: jsrsasign (High 8.7) | O3 Security