CVE-2026-4600Public exploitNetwork attack vector

Signature forgery via unchecked DSA domain parameters

Published Mar 23, 2026 · Updated Mar 23, 2026

Improper DSA signature verification in jsrsasign before 11.1.1 allows remote attackers to forge signatures and X.509 certificates. KJUR.crypto.DSA.setPublic accepts untrusted p, q, g, and y values without enforcing FIPS domain and public-key bounds, so g=1 and y=1 collapse the verification equation. Exploitation requires a consuming application to verify an attacker-supplied DSA key or certificate; accepted forgeries can bypass trust decisions but do not directly interrupt service.

CVSS severity7.4
High
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper DSA signature verification in jsrsasign before 11.1.1 allows remote attackers to forge signatures and X.509 certificates. KJUR.crypto.DSA.setPublic accepts untrusted p, q, g, and y values without enforcing FIPS domain and public-key bounds, so g=1 and y=1 collapse the verification equation. Exploitation requires a consuming application to verify an attacker-supplied DSA key or certificate; accepted forgeries can bypass trust decisions but do not directly interrupt service.

The record

CVE
CVE-2026-4600
Published
Mar 23, 2026
Updated
Mar 23, 2026
Vendor
jsrsasign project
Product
jsrsasign
Classifications
CWE-347, CAPEC-475, T1553
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 23, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <11.1.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

jsrsasign project · jsrsasignversion=0 <11.1.1

Published CVSS scores

9.1NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
7.4SnykCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
8.2Red HatCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
8.1GitHub Advisory DatabaseCVSS: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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
CAPEC-475Signature Spoofing by Improper Validation
T1553Subvert Trust Controls

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo