BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-21717High confidence

A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable

nodejs · node

5.9MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, 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.27% 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 nodejs node 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: As exposure requiresRemediation target: Within 365 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.24.14.1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.22.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.22.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.20.19.2+dfsg-1+deb13u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenodejsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.22.22.2+dfsg+~cs22.19.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.22.22.2+dfsg+~cs22.19.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenodejsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 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-2026-21717 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: v8: Node.js: Denial of Service via V8 string hashing mechanism due to predictable hash collisions
47 known affected

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

  • nodejs as a component of Red Hat Enterprise Linux 10
  • nodejs-devel as a component of Red Hat Enterprise Linux 10
  • nodejs-docs as a component of Red Hat Enterprise Linux 10
  • nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
  • nodejs-libs as a component of Red Hat Enterprise Linux 10
  • nodejs-npm as a component of Red Hat Enterprise Linux 10
  • nodejs22.src as a component of Red Hat Enterprise Linux 10
  • nodejs-devel (nodejs:20) as a component of Red Hat Enterprise Linux 8
  • nodejs-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8
  • nodejs-docs (nodejs:20) as a component of Red Hat Enterprise Linux 8
  • nodejs-docs (nodejs:22) as a component of Red Hat Enterprise Linux 8
  • nodejs-full-i18n (nodejs:20) as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in V8's string hashing mechanism within Node.js. A remote attacker can exploit this vulnerability by crafting requests containing integer-like strings. These specially crafted strings cause predictable hash collisions in V8's internal string table, particularly when processed by functions like JSON.parse() on attacker-controlled input. This can significantly degrade the performance of the Node.js process, leading to a Denial of Service (DoS) condition.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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-2026-17182

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.

What

A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.

Why

The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).

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

A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table. This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.

Why

The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).

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 → Use of Weak Hash → 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
High: exploitation depends on specific conditions
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-328 ↗

CWE-328: Use of Weak Hash. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).

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:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
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-328
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-0843Node.js: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen und Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260401Security Bulletin 01 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Apr 2026, published on 1 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0796Multiples vulnérabilités dans Tenable Identity Exposure

rd?id=CVE-2026-1965 Référence CVE CVE-2026-21218 https://www.cve.org/CVERecord?id=CVE-2026-21218 Référence CVE CVE-2026-21262 https://www.cve.org/CVERecord?id=CVE-2026-21262 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-21713 https://www.cve.org/CVERecord?id=CVE-2026-21713 Référence CVE CVE-2026-21714 https://www.cve.org/CVERecord?id=CVE-2026-21714 Référence CVE CVE-2026-21715 https://www.cve.org/CVERecord?id=CVE-2026-21715 Référence CVE CVE-2026-21716 https://www.cve.org/CVERecord?id=CVE-2026-21716 Référence CVE CVE-2026-21717 https://www.cve.org/CVERecord?id=CVE-2026-21717 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-26130 https://www.cve.org/CVERecord?id=CVE-2026-26130 Référence CVE CVE-2026-26171 https://www.cve.org/CVERecord?id=CVE-2026-26171 Référence CVE CVE-2026-2673 https://www.cve.org/CVERecord?id=CVE-2026-2673 Référence CVE CVE-2026-28386 https://www.cve.org/CVERecord?id=CVE-2026-28386 Référence CVE CVE-2026-28387 https://www.cve.org/CVERecord?id=CVE-2026-28387 Référence CVE CVE-2026-28388 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2026-20240 Référence CVE CVE-2026-21441 https://www.cve.org/CVERecord?id=CVE-2026-21441 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-21712 https://www.cve.org/CVERecord?id=CVE-2026-21712 Référence CVE CVE-2026-21713 https://www.cve.org/CVERecord?id=CVE-2026-21713 Référence CVE CVE-2026-21714 https://www.cve.org/CVERecord?id=CVE-2026-21714 Référence CVE CVE-2026-21715 https://www.cve.org/CVERecord?id=CVE-2026-21715 Référence CVE CVE-2026-21716 https://www.cve.org/CVERecord?id=CVE-2026-21716 Référence CVE CVE-2026-21717 https://www.cve.org/CVERecord?id=CVE-2026-21717 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-22690 https://www.cve.org/CVERecord?id=CVE-2026-22690 Référence CVE CVE-2026-22691 https://www.cve.org/CVERecord?id=CVE-2026-22691 Référence CVE CVE-2026-22695 https://www.cve.org/CVERecord?id=CVE-2026-22695 Référence CVE CVE-2026-22702 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0483Multiples vulnérabilités dans Stormshield Management Center

De multiples vulnérabilités ont été découvertes dans Stormshield Management Center. 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-0436Multiples vulnérabilités dans Tenable Identity Exposure

rd?id=CVE-2026-1965 Référence CVE CVE-2026-21218 https://www.cve.org/CVERecord?id=CVE-2026-21218 Référence CVE CVE-2026-21262 https://www.cve.org/CVERecord?id=CVE-2026-21262 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-21713 https://www.cve.org/CVERecord?id=CVE-2026-21713 Référence CVE CVE-2026-21714 https://www.cve.org/CVERecord?id=CVE-2026-21714 Référence CVE CVE-2026-21715 https://www.cve.org/CVERecord?id=CVE-2026-21715 Référence CVE CVE-2026-21716 https://www.cve.org/CVERecord?id=CVE-2026-21716 Référence CVE CVE-2026-21717 https://www.cve.org/CVERecord?id=CVE-2026-21717 Référence CVE CVE-2026-23941 https://www.cve.org/CVERecord?id=CVE-2026-23941 Référence CVE CVE-2026-23942 https://www.cve.org/CVERecord?id=CVE-2026-23942 Référence CVE CVE-2026-23943 https://www.cve.org/CVERecord?id=CVE-2026-23943 Référence CVE CVE-2026-26115 https://www.cve.org/CVERecord?id=CVE-2026-26115 Référence CVE CVE-2026-26130 https://www.cve.org/CVERecord?id=CVE-2026-26130 Référence CVE CVE-2026-3783 https://www.cve.org/CVERecord?id=CVE-2026-3783 Référence CVE CVE-2026-3784 https://www.cve.org/CVERecord?id=CVE-2026-3784 Référence CVE CVE-2026-3805 https://www.cve.org/CVERecord?id=CVE-2

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

De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-029191Node.js FoundationのNode.jsにおける弱いハッシュの使用に関する脆弱性

V8の文字列ハッシュ機構における欠陥により、整数のような文字列がそれらの数値としてハッシュされ、ハッシュの衝突が容易に予測可能になります。この問題を突いて、V8の内部文字列テーブルで多数の衝突を引き起こすリクエストを作成することで、攻撃者はNode.jsプロセスのパフォーマンスを著しく低下させることが可能です。最も一般的なトリガーは、攻撃者が制御する入力に対して `JSON.parse()` を呼び出すエンドポイントであり、JSONパースは短い文字列を自動的に影響を受けるハッシュテーブルに内部化するためです。この脆弱性は **20.x、22.x、24.x、および25.x** に影響を及ぼします。

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.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 30 Mar 2026 · Last source change 10 May 2026, 13:16 UTC · CWE-328 · Use of Weak Hash

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-2026-17182
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
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
    20.20.1 ≤ 20.20.1; 22.22.1 ≤ 22.22.1; 24.14.0 ≤ 24.14.0; 25.8.1 ≤ 25.8.1; 4.0 < 4.*; 5.0 < 5.*; 6.0 < 6.*; 7.0 < 7.* · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    20.20.1 ≤ 20.20.1; 22.22.1 ≤ 22.22.1; 24.14.0 ≤ 24.14.0; 25.8.1 ≤ 25.8.1; 4.0 < 4.*; 5.0 < 5.*; 6.0 < 6.*; 7.0 < 7.* · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: nodejs.org/march-2026-security-releases.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: nodejs.org/march-2026-security-releases
    support@hackerone.com ↗
  4. CVSS scoreCVSS version changed from 3.0 to 3.1; the displayed base score remains 5.9.
    Before
    5.9 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)
    After
    5.9 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-17182↗Red Hat Product Security security advisory↗CVE authority or vendor 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-2026-21717 · cve.blacktree.nl