BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-65945High confidence

auth0/node-jws improper HMAC signature verification vulnerability

auth0 · node-jws

Official source article: GitHub GHSA-869P-CJFG-CM3X ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.21% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs auth0 node-jws and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmjws< 3.2.33.2.3GitHub advisory ↗upstream repository advisory · 4 Dec 2025
npmjws= 4.0.04.0.1GitHub advisory ↗upstream repository advisory · 4 Dec 2025
npmjwsSEMVER: introduced 0; fixed 3.2.33.2.3OSV record ↗aggregator derived · 10 Sep 2026
npmjwsSEMVER: introduced 4.0.0; fixed 4.0.14.0.1OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-65945 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynode-jws: auth0/node-jws: Improper signature verification in HS256 algorithm
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • io.apicurio-apicurio-registry as a component of Red Hat build of Apicurio Registry 2
  • rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
  • rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
  • openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4
  • odf4/mcg-core-rhel9 as a component of Red Hat Openshift Data Foundation 4
Summary
A flaw was found in auth0/node-jws. This vulnerability allows improper signature verification via using the HS256 (Hash-based Message Authentication Code using SHA-256) algorithm under specific conditions, where applications use the jws.createVerify() function for HMAC (Keyed-Hash Message Authentication Code) algorithms and user-provided data from the JSON (JavaScript Object Notation) Web Signature protected header or payload in HMAC secret lookup routines.
Remediation
For more about Red Hat Developer Hub, see References links
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-201250

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Verification of Cryptographic Signature → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-347 ↗

CWE-347: Improper Verification of Cryptographic Signature. The product does not verify, or incorrectly verifies, the cryptographic signature for data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-347
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0105Red Hat Developer Hub: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Red Hat Developer Hub ausnutzen, um einen Denial of Service Angriff durchzuführen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen und Daten zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2025-2909IBM App Connect Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um beliebigen Programmcode auszuführen, um Dateien zu manipulieren, um einen Denial of Service Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251210Security Bulletin 10 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Dec 2025, published on 10 December 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0667Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2025-58754 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CVE-2025-59471 Référence CVE CVE-2025-59472 https://www.cve.org/CVERecord?id=CVE-2025-59472 Référence CVE CVE-2025-6176 https://www.cve.org/CVERecord?id=CVE-2025-6176 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-6545 https://www.cve.org/CVERecord?id=CVE-2025-6545 Référence CVE CVE-2025-6547 https://www.cve.org/CVERecord?id=CVE-2025-6547 Référence CVE CVE-2025-65945 https://www.cve.org/CVERecord?id=CVE-2025-65945 Référence CVE CVE-2025-66030 https://www.cve.org/CVERecord?id=CVE-2025-66030 Référence CVE CVE-2025-66031 https://www.cve.org/CVERecord?id=CVE-2025-66031 Référence CVE CVE-2025-66221 https://www.cve.org/CVERecord?id=CVE-2025-66221 Référence CVE CVE-2025-66418 https://www.cve.org/CVERecord?id=CVE-2025-66418 Référence CVE CVE-2025-66471 https://www.cve.org/CVERecord?id=CVE-2025-66471 Référence CVE CVE-2025-67221 https://www.cve.org/CVERecord?id=CVE-2025-67221 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0171Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-61795 Référence CVE CVE-2025-61921 https://www.cve.org/CVERecord?id=CVE-2025-61921 Référence CVE CVE-2025-6442 https://www.cve.org/CVERecord?id=CVE-2025-6442 Référence CVE CVE-2025-64505 https://www.cve.org/CVERecord?id=CVE-2025-64505 Référence CVE CVE-2025-64506 https://www.cve.org/CVERecord?id=CVE-2025-64506 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64720 https://www.cve.org/CVERecord?id=CVE-2025-64720 Référence CVE CVE-2025-65018 https://www.cve.org/CVERecord?id=CVE-2025-65018 Référence CVE CVE-2025-65637 https://www.cve.org/CVERecord?id=CVE-2025-65637 Référence CVE CVE-2025-65945 https://www.cve.org/CVERecord?id=CVE-2025-65945 Référence CVE CVE-2025-66418 https://www.cve.org/CVERecord?id=CVE-2025-66418 Référence CVE CVE-2025-66471 https://www.cve.org/CVERecord?id=CVE-2025-66471 Référence CVE CVE-2025-67499 https://www.cve.org/CVERecord?id=CVE-2025-67499 Référence CVE CVE-2025-68973 https://www.cve.org/CVERecord?id=CVE-2025-68973 Référence CVE CVE-2025-6966 https://www.cve.org/CVERecord?id=CVE-2025-6966 Référence CVE CVE-2025-7039 https://www.cve.org/CVERecord?id=CVE-2025-7039 Référence CVE CVE-2025-7339 https://www.cve.org/CVERecord?id=CVE-2025-7339 Référence CVE CVE-2025-7424 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-026210Auth0 Inc.のnode-jwsにおけるデジタル署名の検証に関する脆弱性

auth0/node-jwsはNode.js向けのJSON Web Signature実装です。バージョン3.2.2以前およびバージョン4.0.0において、特定の条件下でHS256アルゴリズムを使用する際に不適切な署名検証の脆弱性が存在します。jws.createVerify()関数をHMACアルゴリズムで使用し、JSON Web Signatureで保護されたヘッダーやペイロードからのユーザ提供データをHMAC秘密鍵の検索ルーチンに使用しているアプリケーションが対象であり、攻撃者が署名検証を回避できる可能性があります。この問題はバージョン3.2.3および4.0.1で修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For more about Red Hat Developer Hub, see References links
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 4 Dec 2025 · Last source change 5 Dec 2025, 18:31 UTC · CWE-347 · Improper Verification of Cryptographic Signature

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-201250
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.2.3; >= 4.0.0, <= 4.0.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 3.2.3; >= 4.0.0, <= 4.0.1 · Fixed: For more about Red Hat Developer Hub, see References links
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    io.apicurio-apicurio-registry as a component of Red Hat build of Apicurio Registry 2; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; odf4/mcg-core-rhel9 as a component of Red Hat Openshift Data Foundation 4 · Fixed: registry.redhat.io/rhdh/rhdh-hub-rhel9@sha256:29ada5e84c6b204cf518191a21bbd22de5cb53a61bc1812b1072ce5c28a235b2_amd64 as a component of Red Hat Developer Hub 1.7; registry.redhat.io/rhdh/rhdh-hub-rhel9@sha256:7185a8f744022307c7a178d35e7ae32d7797eed4f9379b2dba8954e2856f2ed1_amd64 as a component of Red Hat Developer Hub 1.8; registry.redhat.io/devspaces/code-rhel9@sha256:60a1c1cf2a755e24203ae76e37c3e1c08f97ae8a1905df3538b31f7d9b543f0f_s390x as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/code-rhel9@sha256:772af8d40b674ce306850d3ecf2b70b39bdceaf9e045a2db9299c0dd8bd5e6b5_amd64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/code-rhel9@sha256:a85afca6643f11c1e0d3976d5e679cea06d85675a5859e7e08611139f2450520_arm64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/code-rhel9@sha256:aa1d96a9c1d9dbf2fe077748807de1e047a17a942a87688c269aa60537b5c6d4_ppc64le as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:024f64869d4813d8b0938f8cad9a0bf4e4e924a5082ac2ee3ea0bc6ba51edfe5_arm64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:b709ca92a102d77f8a090e1503877e12dc24bbd6e91c0205d8402ad3a9c365e9_amd64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:de30783c5550d7dc3ebd71507ce41e4a6f6209663299453aaf35b73f17d161d8_ppc64le as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:ffe5740d684ac4a1b6c440bb4d2ca3ec20d71c008e65fa73f5143c43a7bda339_s390x as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/quay/quay-rhel8@sha256:03a485b1c02f5155f22c7820c166889b3f7d7b479892bb4d106432fa2dbf217b_arm64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:117876c6c6a12beb25983da60c8c1628f350a1797888b9f03c44b9dd737844fa_amd64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:e82aac09336b0a36d5bc896826891ec41714ea1e05aac345a49abc4915b255ee_ppc64le as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:f58b0c52270707e15747b431520150641019c9b215e864c8dfe8dec1f6e94caf_s390x as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:1403699a49e9fa2e04fab27f28de244b6e3e631877eb6eddb55b676d3ec44587_arm64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:39cadc6e19d0ea7e86a6b11aa15093d4e7d24bc69be260abed90396f92b4126c_amd64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:8b52456a5391e1e5179ccdc6ac3ec3737a9a33481128a86dd055813881ebc900_s390x as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:d1fa7495f6dfad0e41f81ca8bf02689f6241973af27e2b98165878d3fc602d12_ppc64le as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:05cc4b4410de27e32897492effb21362d8c1bc8cc56e9408fc9a19f9f3149899_arm64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:225e2bed98b80e753ba2eca6b121a7295b20633b25b8098b7dce66efc2bc1b70_amd64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:51881be0039c3a7df9ad588060955dc3f0ea6eef28a35ebc4fe146e73316e2a4_s390x as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:e2a2347a1ed65e94a13fd0330e7922339096d725733071a1f9eb4c413be5eb90_ppc64le as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:08a827d542790820a10a61bacdc8ab7c05a6fdd476f1224ed76f20d65e93673f_s390x as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:7bfb851938e312f47598891ba9f0d7b17e6657090e0204d37d5676313b33f134_ppc64le as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:a8daa359ab7a0bc9722b25fb87aa6fd253506632640bfe7f31c9c92868421ecb_amd64 as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel9@sha256:35e3dc29e64bae8c0b35d7884281397c58165a5b145676919452a02b9f56ee4c_amd64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:45de5fc478cb2734b672630c67ffee4e6b98954848b97ea9a1cc9903a53dbf8e_s390x as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:96588daff01f27db2ee335dcd957e9dec7f38a2c573e2968d9bc5835edc2957b_arm64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:9f58fc80db29fa44684c6e39bb2eda06e86ba34801d5e04468941ac8d0b754eb_ppc64le as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel8@sha256:5cf58b1f54219b67c725f4a5066d9e757e7b5ece39d5de1a474a8be6a3490401_ppc64le as a component of Red Hat Quay 3.1; and 11 more
    After
    io.apicurio-apicurio-registry as a component of Red Hat build of Apicurio Registry 2; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; odf4/mcg-core-rhel9 as a component of Red Hat Openshift Data Foundation 4 · Fixed: registry.redhat.io/rhdh/rhdh-hub-rhel9@sha256:29ada5e84c6b204cf518191a21bbd22de5cb53a61bc1812b1072ce5c28a235b2_amd64 as a component of Red Hat Developer Hub 1.7; registry.redhat.io/rhdh/rhdh-hub-rhel9@sha256:7185a8f744022307c7a178d35e7ae32d7797eed4f9379b2dba8954e2856f2ed1_amd64 as a component of Red Hat Developer Hub 1.8; registry.redhat.io/devspaces/code-rhel9@sha256:60a1c1cf2a755e24203ae76e37c3e1c08f97ae8a1905df3538b31f7d9b543f0f_s390x as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/code-rhel9@sha256:772af8d40b674ce306850d3ecf2b70b39bdceaf9e045a2db9299c0dd8bd5e6b5_amd64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/code-rhel9@sha256:a85afca6643f11c1e0d3976d5e679cea06d85675a5859e7e08611139f2450520_arm64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/code-rhel9@sha256:aa1d96a9c1d9dbf2fe077748807de1e047a17a942a87688c269aa60537b5c6d4_ppc64le as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:024f64869d4813d8b0938f8cad9a0bf4e4e924a5082ac2ee3ea0bc6ba51edfe5_arm64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:b709ca92a102d77f8a090e1503877e12dc24bbd6e91c0205d8402ad3a9c365e9_amd64 as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:de30783c5550d7dc3ebd71507ce41e4a6f6209663299453aaf35b73f17d161d8_ppc64le as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/devspaces/openvsx-rhel9@sha256:ffe5740d684ac4a1b6c440bb4d2ca3ec20d71c008e65fa73f5143c43a7bda339_s390x as a component of Red Hat OpenShift Dev Spaces (RHOSDS) 3.26; registry.redhat.io/quay/quay-rhel8@sha256:5cf58b1f54219b67c725f4a5066d9e757e7b5ece39d5de1a474a8be6a3490401_ppc64le as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:b46b24ca0902be8f03b1ffa1b593ef55a4d92a9660adb4b8b4d0f44692431b93_s390x as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:b54b571ac2f245f1a2eb1c7cf0dff6bc24ca6b9706ab8ee2dca323d561238255_amd64 as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:03a485b1c02f5155f22c7820c166889b3f7d7b479892bb4d106432fa2dbf217b_arm64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:117876c6c6a12beb25983da60c8c1628f350a1797888b9f03c44b9dd737844fa_amd64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:e82aac09336b0a36d5bc896826891ec41714ea1e05aac345a49abc4915b255ee_ppc64le as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:f58b0c52270707e15747b431520150641019c9b215e864c8dfe8dec1f6e94caf_s390x as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:1403699a49e9fa2e04fab27f28de244b6e3e631877eb6eddb55b676d3ec44587_arm64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:39cadc6e19d0ea7e86a6b11aa15093d4e7d24bc69be260abed90396f92b4126c_amd64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:8b52456a5391e1e5179ccdc6ac3ec3737a9a33481128a86dd055813881ebc900_s390x as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:d1fa7495f6dfad0e41f81ca8bf02689f6241973af27e2b98165878d3fc602d12_ppc64le as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:05cc4b4410de27e32897492effb21362d8c1bc8cc56e9408fc9a19f9f3149899_arm64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:225e2bed98b80e753ba2eca6b121a7295b20633b25b8098b7dce66efc2bc1b70_amd64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:51881be0039c3a7df9ad588060955dc3f0ea6eef28a35ebc4fe146e73316e2a4_s390x as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:e2a2347a1ed65e94a13fd0330e7922339096d725733071a1f9eb4c413be5eb90_ppc64le as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:08a827d542790820a10a61bacdc8ab7c05a6fdd476f1224ed76f20d65e93673f_s390x as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:7bfb851938e312f47598891ba9f0d7b17e6657090e0204d37d5676313b33f134_ppc64le as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:a8daa359ab7a0bc9722b25fb87aa6fd253506632640bfe7f31c9c92868421ecb_amd64 as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel9@sha256:35e3dc29e64bae8c0b35d7884281397c58165a5b145676919452a02b9f56ee4c_amd64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:45de5fc478cb2734b672630c67ffee4e6b98954848b97ea9a1cc9903a53dbf8e_s390x as a component of Red Hat Quay 3.16; and 11 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-201250↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-869P-CJFG-CM3X↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-65945 · cve.blacktree.nl