Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 7/9 advisories · checked 06:36 UTC Customize Public modeDiscuss ChangeIntel on Discord

auth0/node-jws improper HMAC signature verification vulnerability

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

cve-program · CVE-2025-65945

Published

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.

Source published
4 Dec 2025 18:45:37 UTC
Source modified
5 Dec 2025 18:31:52 UTC
Observed here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

euvd · EUVD-2025-201250

Published

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.

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Dec 4, 2025, 6:45:37 PM

dateUpdated: Dec 5, 2025, 6:31:52 PM

15 related source bulletins · separate from aliases

WID-SEC-W-2025-2909: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2025-13466 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-65945

RHSA-2026:2754: Red Hat Security Advisory: Red Hat Quay 3.9.18

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-52881 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66506 · CVE-2026-24049

RHSA-2026:2762: Red Hat Security Advisory: Red Hat Quay 3.10.18

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

WID-SEC-W-2026-0105: Red Hat Developer Hub: Mehrere Schwachstellen

CVE-2025-15284 · CVE-2025-64756 · CVE-2025-65945

RHSA-2026:1730: Red Hat Security Advisory: Red Hat Quay 3.12.13

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441

RHSA-2026:0261: Red Hat Security Advisory: Red Hat Developer Hub 1.7.4 release.

CVE-2025-12816 · CVE-2025-15284 · CVE-2025-64756 · CVE-2025-65945 · CVE-2025-66031

RHSA-2026:0531: Red Hat Security Advisory: Red Hat Developer Hub 1.8.2 release.

CVE-2025-15284 · CVE-2025-64756 · CVE-2025-65945

RHSA-2026:2681: Red Hat Security Advisory: Red Hat Quay 3.16.2

CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-15284 · CVE-2025-31133 · CVE-2025-52881 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441 · CVE-2026-24049

RHSA-2026:2922: Red Hat Security Advisory: RHTAS 1.2.2 - Red Hat Trusted Artifact Signer Release

CVE-2025-47913 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66506 · CVE-2026-22772

RHSA-2026:1942: Red Hat Security Advisory: Red Hat Quay 3.15.3

CVE-2024-34156 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-47907 · CVE-2025-47913 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-59420 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

RHSA-2026:2456: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.26.0 Release.

CVE-2024-25621 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-61729 · CVE-2025-64756 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66490 · CVE-2026-21441 · CVE-2026-22029

RHSA-2026:2926: Red Hat Security Advisory: RHTAS 1.2.2 - Red Hat Trusted Artifact Signer Release

CVE-2025-13465 · CVE-2025-61729 · CVE-2025-64756 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441 · CVE-2026-22774 · CVE-2026-22775 · CVE-2026-23745 · CVE-2026-23950

RHSA-2026:4185: Red Hat Security Advisory: Red Hat Quay 3.13.11

CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

RHSA-2026:2921: Red Hat Security Advisory: RHTAS 1.2.2 - Red Hat Trusted Artifact Signer Release

CVE-2025-61729 · CVE-2025-65945

RHSA-2026:4215: Red Hat Security Advisory: Red Hat Quay 3.14.6

CVE-2022-30187 · CVE-2024-34156 · CVE-2024-47081 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-45768 · CVE-2025-47273 · CVE-2025-47913 · CVE-2025-50181 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-59420 · CVE-2025-61729 · CVE-2025-61920 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049

Source published
Dec 4, 2025, 6:45:37 PM (timezone not stated)
Source modified
Dec 5, 2025, 6:31:52 PM (timezone not stated)
Observed here
9 Nov 2026 04:08:28 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.

EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd · CVE-2025-65945

Published

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.

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-347

Original publisher date fields

published: 2025-12-04T19:16:05.550

lastModified: 2026-10-18T15:10:00.097

2 source CPE criteria · context only
  • cpe:2.3:a:auth0:node-jws:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:auth0:node-jws:4.0.0:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
4 Dec 2025 19:16:05 UTC
Source modified
18 Oct 2026 15:10:00 UTC
Observed here
25 Oct 2026 03:17:36 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

osv · GHSA-869p-cjfg-cm3x

Published

### 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 ### Fix Upgrade auth0/node-jws version to version 3.2.3 or 4.0.1 ### Acknowledgement Okta would like to thank Félix Charette for discovering this vulnerability.

Source published
4 Dec 2025 16:54:15 UTC
Source modified
10 Sep 2026 03:50:31 UTC
Observed here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 9 Nov 06:36 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current