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

cve-program · CVE-2026-4601

Published

jsrsasign

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "jsrsasign",
                    "versions": [
                        {
                            "version": "0",
                            "lessThan": "11.1.1",
                            "status": "affected",
                            "versionType": "semver"
                        }
                    ],
                    "vendor": "n/a"
                }

org.webjars.npm:jsrsasign

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "org.webjars.npm:jsrsasign",
                    "versions": [
                        {
                            "version": "0",
                            "lessThan": "*",
                            "status": "affected",
                            "versionType": "semver"
                        }
                    ],
                    "vendor": "n/a"
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-14377

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 23, 2026, 5:00:13 AM

dateUpdated: Sep 10, 2026, 12:04:55 PM

7 related source bulletins · separate from aliases

RHSA-2026:19375: Red Hat Security Advisory: Red Hat Quay 3.16.4

CVE-2025-61726 · CVE-2025-62718 · CVE-2026-2377 · CVE-2026-4427 · CVE-2026-4598 · CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27459 · CVE-2026-27962 · CVE-2026-28802 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-30922 · CVE-2026-32280 · CVE-2026-32282 · CVE-2026-32286 · CVE-2026-32589 · CVE-2026-32590 · CVE-2026-32597 · CVE-2026-33186 · CVE-2026-33894 · CVE-2026-34986 · CVE-2026-39892 · CVE-2026-40192 · CVE-2026-40895 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42039 · CVE-2026-42041 · CVE-2026-42043 · CVE-2026-42044

RHSA-2026:19409: Red Hat Security Advisory: MTV RHEL9 Images

CVE-2026-4598 · CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-29063

RHSA-2026:19410: Red Hat Security Advisory: MTV RHEL9 Images

CVE-2026-4598 · CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-4800 · CVE-2026-4926 · CVE-2026-29063

RHSA-2026:6568: Red Hat Security Advisory: Red Hat Quay 3.15.4

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-61726 · CVE-2025-61728 · CVE-2025-61729 · CVE-2025-68121 · CVE-2025-68158 · CVE-2025-69873 · CVE-2026-4598 · CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-25639 · CVE-2026-25990 · CVE-2026-26007 · CVE-2026-26996 · CVE-2026-27628 · CVE-2026-27904 · CVE-2026-28498 · CVE-2026-28802 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-30922 · CVE-2026-32597

RHSA-2026:6912: Red Hat Security Advisory: Red Hat Quay 3.10.20

CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-28498 · CVE-2026-30922 · CVE-2026-32597

RHSA-2026:6926: Red Hat Security Advisory: Red Hat Quay 3.9.20

CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-30922 · CVE-2026-32597

RHSA-2026:6720: Red Hat Security Advisory: Red Hat Quay 3.12.16

CVE-2026-4598 · CVE-2026-4599 · CVE-2026-4600 · CVE-2026-4601 · CVE-2026-4602 · CVE-2026-25679 · CVE-2026-28498 · CVE-2026-29063 · CVE-2026-30922 · CVE-2026-32597

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-4601

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-325

Original publisher date fields

published: 2026-03-23T06:16:21.893

lastModified: 2026-09-10T13:20:22.510

1 source CPE criteria · context only
  • cpe:2.3:a:kjur:jsrsasign:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-w8q8-93cx-6h7r

Published

jsrsasign

npm

SEMVER · introduced 0 → fixed 11.1.1

Original source record · Cite this exact observation · Complete original publisher JSON

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