Secuno
ENNL
Book demo

CVE-2026-4601

Kjur Jsrsasign vulnerability

8.7 HIGHPublic exploitEPSS 0.47%
  1. Published23 Mar 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected products

Kjur Jsrsasign< 11.1.1

Remediation

Fixed in
Kjur Jsrsasign≥ 11.1.1

References

and 5 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1007988.1
Cryptography misuse in Storage: Quota Manager component. This vulnerability was fixed…
CVE-2026-812358.0
Dell Wyse Management Suite, versions prior to 2605.0.3.683, contain a Missing…
CVE-2026-176669.1
Cryptographic Flaw in Enterprise in Google Chrome prior to 151.0.7922.72 allowed an…

Frequently asked

Is CVE-2026-4601 being actively exploited?

CVE-2026-4601 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.47%.

How severe is CVE-2026-4601?

CVE-2026-4601 has a CVSS 3.1 base score of 8.7, rated high. EPSS estimates a 0.47% probability of exploitation.

Which products are affected by CVE-2026-4601?

Affected products include Kjur Jsrsasign.

How do I fix CVE-2026-4601?

Upgrade affected software to a fixed version, for example Kjur Jsrsasign 11.1.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-4601 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.