Loading vulnerability…
CVE-2026-4600 is an improper cryptographic signature verification vulnerability in jsrsasign affecting versions before 11.1.1. The flaw is in DSA domain-parameter validation within KJUR.crypto.DSA.setPublic and the related DSA/X.509 verification flow in src/dsa-2.0.js. By supplying malicious DSA domain parameters, including degenerate values that cause the verification equation to trivially succeed, an attacker can craft forged DSA signatures or X.509 certificates that are incorrectly accepted as valid by verification routines such as X509.verifySignature(). This breaks the trust assumptions of DSA-based signature validation and can allow unauthenticated acceptance of attacker-controlled signed material.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.