CVE-2025-65945

Overview

An improper signature verification vulnerability exists when using auth0/node-jws with the HS256 algorithm under specific conditions.

Am I Affected?

You are affected by this vulnerability if you meet all of the following preconditions:

1. Application uses the auth0/node-jws implementation of JSON Web Signatures, versions <=3.2.2 || 4.0.0
2. Application uses the jws.createVerify() function for HMAC algorithms
3. Application uses user-provided data from the JSON Web Signature Protected Header or Payload in the HMAC secret lookup routines

You are NOT affected by this vulnerability if you meet any of the following preconditions:

1. Application uses the jws.verify() interface (note: auth0/node-jsonwebtoken users fall into this category and are therefore NOT affected by this vulnerability)
2. Application uses only asymmetric algorithms (e.g. RS256)
3. Application doesn’t use user-provided data from the JSON Web Signature Protected Header or Payload in the HMAC secret lookup routines

Acknowledgement

Okta would like to thank Félix Charette for discovering this vulnerability.

CVE-2025-65945 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.3, 4.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade auth0/node-jws version to version 3.2.3 or 4.0.1

1. What is CVE-2025-65945? CVE-2025-65945 is a high-severity security vulnerability in jws (npm), affecting versions < 3.2.3. It is fixed in 3.2.3, 4.0.1.
2. How severe is CVE-2025-65945? CVE-2025-65945 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of jws are affected by CVE-2025-65945? jws (npm) versions < 3.2.3 is affected.
4. Is there a fix for CVE-2025-65945? Yes. CVE-2025-65945 is fixed in 3.2.3, 4.0.1. Upgrade to this version or later.
5. Is CVE-2025-65945 exploitable, and should I be worried? Whether CVE-2025-65945 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-65945 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-65945?
   • Upgrade jws to 3.2.3 or later
   • Upgrade jws to 4.0.1 or later