Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

jsrsasign · Vulnerability

CVSS 3.1 8.7 HIGHCVSS 4.0 9.4 CRITICALEUVD CVSS 4.0 9.4 CVSS 4.0 · [email protected] · Secondary 8.8 HIGHCVSS 3.1 · [email protected] · Secondary 8.7 HIGHCVSS 3.1 · [email protected] · Primary 9.1 CRITICALCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 8.7 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by jsrsasign 11.1.1KEV status unknown

cve-program · CVE-2026-4601

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-14377

Published

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.

Read the publisher's advisory

nvd · CVE-2026-4601

Published

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.

Read the publisher's advisory

osv · GHSA-w8q8-93cx-6h7r

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-4601 · CVE overview and exploitation status

EUVD-2026-14377

GHSA-w8q8-93cx-6h7r

cve-program · CVE-2026-4601

euvd · EUVD-2026-14377

nvd · CVE-2026-4601

osv · GHSA-w8q8-93cx-6h7r

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 04:44 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current