How severe is GHSA-wvqx-v3f6-w8rh?

GHSA-wvqx-v3f6-w8rh has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wvqx-v3f6-w8rh?

GHSA-wvqx-v3f6-w8rh affects the following packages: jsrsasign (npm). Ecosystems affected: npm.

How do I fix GHSA-wvqx-v3f6-w8rh?

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

How do I detect GHSA-wvqx-v3f6-w8rh in my npm dependencies?

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.

How do I mitigate GHSA-wvqx-v3f6-w8rh if there is no patch (or I can't update yet)?

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.

Is GHSA-wvqx-v3f6-w8rh actively exploited in the wild?

No public exploit code has been indexed for GHSA-wvqx-v3f6-w8rh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-wvqx-v3f6-w8rh?

GHSA-wvqx-v3f6-w8rh has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wvqx-v3f6-w8rh?

GHSA-wvqx-v3f6-w8rh is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wvqx-v3f6-w8rh published, and has it been updated?

GHSA-wvqx-v3f6-w8rh was published on March 23, 2026 and was last updated on July 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

jsrsasign: DSA signatures or X.509 certificates can be forged via DSA domain-parameter validation in KJUR.crypto.DSA.setPublicGHSA-wvqx-v3f6-w8rh

HIGHFix: kjur/jsrsasign#646

GHSA-wvqx-v3f6-w8rh is a high-severity (CVSS 7.4) CWE-347 vulnerability in jsrsasign. A fix is available for jsrsasign — see the affected versions and patch details below.

Also known asCVE-2026-4600

Published

Mar 23, 2026

Updated

Jul 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wvqx-v3f6-w8rh.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

2.3Mdownloads / week

Description

Versions of the package jsrsasign before 11.1.1 are vulnerable to Improper Verification of Cryptographic Signature via the DSA domain-parameter validation in KJUR.crypto.DSA.setPublic (and the related DSA/X509 verification flow in src/dsa-2.0.js). An attacker can forge DSA signatures or X.509 certificates that X509.verifySignature() accepts by supplying malicious domain parameters such as g=1, y=1, and a fixed r=1, which make the verification equation true for any hash.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jsrsasign`	all versions	11.1.1`npm install jsrsasign@11.1.1`

Affected Products

1 product · 1 configurations

Application

jsrsasignkjur

< 11.1.1

range

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update jsrsasign to 11.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wvqx-v3f6-w8rh is resolved across your whole dependency graph.
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.

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. The flaw in jsrsasign allows an attacker to forge Digital Signature Algorithm (DSA) signatures or X.509 certificates by providing malicious domain parameters during validation. This could lead to unauthorized access or data manipulation in affected Red Hat products such as Migration Toolkit for…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for GHSA-wvqx-v3f6-w8rh (CC BY 4.0)

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-wvqx-v3f6-w8rh in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works