Loading vulnerability…
CVE-2025-65945 is an improper signature verification vulnerability in auth0/node-jws, a JSON Web Signature implementation for Node.js. The issue affects versions 3.2.2 and earlier, and version 4.0.0, when applications use jws.createVerify() with HMAC-based algorithms such as HS256 and incorporate user-controlled data from the JWS protected header or payload into HMAC secret lookup logic. Under these conditions, signature verification can be bypassed, causing the application to accept a forged or otherwise invalid JSON Web Signature as authentic.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2025-65945, a signature verification bypass in the node-jws library (versions 3.2.2 and earlier, and 4.0.0). The exploit demonstrates how an attacker can forge valid JWTs by exploiting applications that derive HMAC secrets from user-controlled data (such as the JWT 'kid' header) and fail to validate the presence of a secret. The repository contains four files: a .gitignore, a README.md with detailed vulnerability and usage information, a package.json specifying the vulnerable jws dependency, and exploit.js, which implements the exploit logic. The exploit script forges a JWT with a non-existent 'kid' and signs it with an empty secret, which is then accepted as valid by the vulnerable verification logic. This allows attackers to impersonate users or escalate privileges. The PoC is intended for demonstration and testing purposes, and the README provides instructions for reproducing the issue and verifying the fix.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.