LiveActive security incident?Get immediate response
CVE Record

CVE-2026-4600: Versions of the package jsrsasign before 11.1.1 are vulnerable to Improper Verification of Cryptographic Si...

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-4600 affects jsrsasign before 11.1.1. A flaw in DSA signature verification can let forged signatures or certificates be accepted. Business risk is highest where applications use this library to decide identity, trust, authorization, or document integrity.

Executive priority

Treat as urgent for applications using jsrsasign in trust decisions. The vulnerability can undermine signature and certificate validation, which may break authentication or integrity assumptions. Prioritize internet-facing and identity-related systems first.

Technical view

The issue is improper cryptographic signature verification in DSA domain-parameter validation, including KJUR.crypto.DSA.setPublic and related DSA/X.509 verification flow. Invalid DSA parameters can make verification succeed for arbitrary data. Snyk rates affected jsrsasign and org.webjars.npm:jsrsasign versions before 11.1.1 as vulnerable.

Likely exposure

Exposure is likely in JavaScript or Java WebJars applications bundling jsrsasign before 11.1.1 and using DSA or X.509 verification. Risk depends on whether attackers can provide certificates, public keys, or signatures that influence security decisions.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public technical details and a fix are referenced. Exploitation requires reaching a vulnerable verification path with attacker-controlled cryptographic material; no authentication or user interaction is indicated by the CVSS vector.

Researcher notes

Focus triage on DSA and X.509 verification usage, not mere package presence. The disclosed root cause is missing DSA domain-parameter validation. Avoid assuming RSA/ECDSA impact unless vendor sources state it. Red Hat references indicate downstream product tracking and errata.

Mitigation direction

  • Upgrade jsrsasign to 11.1.1 or later where applicable.
  • Upgrade org.webjars.npm:jsrsasign to a fixed version where applicable.
  • Apply relevant Red Hat advisories for affected packaged products.
  • Review vendor guidance if the library is embedded or transitive.
  • Prioritize systems using jsrsasign for authentication, certificate validation, or integrity checks.

Validation and detection

  • Search SBOMs and lockfiles for jsrsasign versions before 11.1.1.
  • Search Maven dependencies for org.webjars.npm:jsrsasign before the fixed release.
  • Confirm built assets and containers no longer bundle vulnerable jsrsasign code.
  • Identify code paths calling jsrsasign DSA or X.509 verification functions.
  • Check Red Hat CVE and CSAF VEX status for deployed Red Hat products.
Prepared
Confidence
high
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-347: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-4600 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

3CVSS vectors
5Timeline events
2ADP providers
16Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

3 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 4.0CriticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P——snyk
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N3.94.2redhat-SADP
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:P2.25.2snyk

Vulnerability scoring details

Base CVSS 4.0 score

9.1Critical
CVSS 4.0 vector shape for CVE-2026-4600Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPjsrsasign: jsrsasign: Cryptographic signature forgery via malicious DSA domain parameters
other:Red Hat severity ratingcvssV3_1
  • 2026-03-23T06:01:39.334Z: Reported to Red Hat.
  • 2026-03-23T05:00:08.475Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ajsrsasign0Listed
n/aorg.webjars.npm:jsrsasign0Listed
Weakness

CWE details

CWE-347

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs