Skip to content
Fencer Vulns
high 7.5

CVE-2025-65945 json

auth0/node-jws improper HMAC signature verification vulnerability

published 2025-12-04 11 mo ago modified 2026-10-18 21 d ago also GHSA-869p-cjfg-cm3x , EUVD-2025-201250

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

auth0/node-jws is a JSON Web Signature implementation for Node.js. In versions 3.2.2 and earlier and version 4.0.0, auth0/node-jws has an improper signature verification vulnerability when using the HS256 algorithm under specific conditions. Applications are affected when they use the jws.createVerify() function for HMAC algorithms and use user-provided data from the JSON Web Signature protected header or payload in HMAC secret lookup routines, which can allow attackers to bypass signature verification. This issue has been patched in versions 3.2.3 and 4.0.1.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-65945 updated cvss 7.5

node-jws: auth0/node-jws: Improper signature verification in HS256 algorithm

  • Red Hat build of Apicurio Registry 2 io.apicurio-apicurio-registry
    affected: workaround, no fix available
  • Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/disk-image-cuda-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-console-rhel9
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Openshift Data Foundation 4 odf4/mcg-core-rhel9
    affected: workaround, no fix available
  • Red Hat Developer Hub 1.7 rhdh 1.7.4-1767715042
    fixed: vendor fix RHSA-2026:0261
  • Red Hat Developer Hub 1.8 rhdh 1768247401
    fixed: vendor fix RHSA-2026:0531
  • Red Hat OpenShift Dev Spaces (RHOSDS) 3.26 devspaces 1769691754, devspaces 1769804221
    fixed: vendor fix RHSA-2026:2456
  • Red Hat Quay 3.9 quay 1770856103
    fixed: vendor fix RHSA-2026:2754
  • Red Hat Quay 3.10 quay 1770249183
    fixed: vendor fix RHSA-2026:2762
show 12 more
  • Red Hat Quay 3.12 quay 1769852013
    fixed: vendor fix RHSA-2026:1730
  • Red Hat Quay 3.13 quay 1773088862
    fixed: vendor fix RHSA-2026:4185
  • Red Hat Quay 3.14 quay 1773097621
    fixed: vendor fix RHSA-2026:4215
  • Red Hat Quay 3.15 quay 1770146565
    fixed: vendor fix RHSA-2026:1942
  • Red Hat Quay 3.16 quay 1770836901
    fixed: vendor fix RHSA-2026:2681
  • Red Hat Trusted Artifact Signer 1.2 rhtas 1770734118
    fixed: vendor fix RHSA-2026:2921
  • Red Hat OpenShift Service Mesh 2 openshift-service-mesh/pilot-rhel8, openshift-service-mesh/grafana-rhel8, openshift-service-mesh/proxyv2-rhel9, openshift-service-mesh/istio-cni-rhel8, openshift-service-mesh/ratelimit-rhel8, openshift-service-mesh/istio-rhel8-operator, +2 more Red Hat OpenShift Service Mesh 3 openshift-service-mesh/istio-cni-rhel9, openshift-service-mesh/istio-pilot-rhel9, openshift-service-mesh/istio-proxyv2-rhel9, openshift-service-mesh/istio-ztunnel-rhel9, openshift-service-mesh/istio-rhel9-operator, openshift-service-mesh/istio-must-gather-rhel9, +3 more
    not affected: component not present
  • Red Hat Advanced Cluster Security 4 advanced-cluster-security/rhacs-collector-rhel8 Red Hat Developer Hub 1.7 rhdh 1.7.4-1767620808, rhdh 1.7.4-1767730186 Red Hat Developer Hub 1.8 rhdh 1768247048, rhdh 1768250779
    not affected: vulnerable code not present
  • Red Hat OpenShift AI (RHOAI) rhoai/odh-notebook-controller-rhel8, rhoai/odh-kf-notebook-controller-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-azure-workload-identity-webhook-rhel9
    not affected: vulnerable code not in execute path
  • Red Hat OpenShift Dev Spaces devspaces/code-sshd-rhel9 Red Hat OpenShift Dev Spaces (RHOSDS) 3.26 devspaces 1769466457, devspaces 1769539518, devspaces 1769595755, devspaces 1769638073, devspaces 1769680738, devspaces 1769685154, +8 more Red Hat Quay 3.9 quay 1770133364, quay 1770133825, quay 1770223960, quay 1770230842, quay 1770249993, quay 1770249996, +3 more Red Hat Quay 3.10 quay 1770133631, quay 1770133646, quay 1770133671, quay 1770224116, quay 1770249881, quay 1770249889, +3 more Red Hat Quay 3.12 quay 1769000026, quay 1769466677, quay 1769718571, quay 1769802588, quay 1769810112, quay 1769810760, +3 more Red Hat Quay 3.13 quay 1770071468, quay 1771539915, quay 1771539959, quay 1771540384, quay 1771540464, quay 1771860977, +3 more
    +3 more products
    Red Hat Quay 3.14 quay 1771008628, quay 1771265622, quay 1773097298, quay 1773097302, quay 1773097311, quay 1773097327, +3 more Red Hat Quay 3.15 quay 1770134320, quay 1770134351, quay 1770134397, quay 1770134436, quay 1770135404, quay 1770135436, +3 more Red Hat Quay 3.16 quay 1770230686, quay 1770762347, quay 1770816239, quay 1770816381, quay 1770816399, quay 1770816415, +3 more
    not affected: vulnerable code not present
  • Red Hat Satellite 6 satellite/iop-advisor-frontend-rhel9, satellite/iop-vulnerability-frontend-rhel9, satellite/iop-host-inventory-frontend-rhel9
    not affected: vulnerable code not in execute path
  • Red Hat Trusted Artifact Signer 1.2 rhtas 1770733887, rhtas 1770734283, rhtas 1770734418, rhtas 1770737394, rhtas 1770738094, rhtas 1770738273, +2 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
11 mo ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm jws
<3.2.3
>=4.0.0, <4.0.1
3.2.3
4.0.1

Affected products

  • auth0 node-jws

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.