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

Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse

nodejs · node

6.8MediumCVSS 3.0
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 2 structured product or package states 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.
  • 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 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 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

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-123877 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: nodejs: Certificate validation bypass via TLS session cache reuse
51 known affected

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

  • nodejs22.src as a component of Red Hat Enterprise Linux 10
  • nodejs24.src as a component of Red Hat Enterprise Linux 10
  • nodejs26.src as a component of Red Hat Enterprise Linux 10
  • nodejs-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8
  • nodejs-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8
  • nodejs-docs (nodejs:22) as a component of Red Hat Enterprise Linux 8
  • nodejs-docs (nodejs:24) as a component of Red Hat Enterprise Linux 8
  • nodejs-full-i18n (nodejs:22) as a component of Red Hat Enterprise Linux 8
  • nodejs-full-i18n (nodejs:24) as a component of Red Hat Enterprise Linux 8
  • nodejs-libs (nodejs:22) as a component of Red Hat Enterprise Linux 8
  • nodejs-libs (nodejs:24) as a component of Red Hat Enterprise Linux 8
  • nodejs-nodemon.src (nodejs:22) as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in Node.js. When managing outbound HTTPS connections, the client connection agent generates identical session-cache keys for requests with differing Certificate Authority (CA) trust configurations. Consequently, an existing Transport Layer Security (TLS) session established under a broad trust policy can be improperly reused by a subsequent request requiring stricter validation. An attacker could exploit this certificate validation bypass to receive confidential data that the application inadvertently transmits to an unauthorized server.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
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.

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 2 structured product or package states 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 certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

What

A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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 Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
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-295 ↗

CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.

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

Common Vulnerability Scoring System 3.0: 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.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.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.
NetworkCWE-295
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Daten zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1531Avis du CERT-FR

De multiples vulnérabilités ont été découvertes dans Node.js. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, un contournement de la politique de sécurité et un déni de service.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1539Avis du CERT-FR

864 Référence CVE CVE-2026-123865 https://www.cve.org/CVERecord?id=CVE-2026-123865 Référence CVE CVE-2026-123866 https://www.cve.org/CVERecord?id=CVE-2026-123866 Référence CVE CVE-2026-123867 https://www.cve.org/CVERecord?id=CVE-2026-123867 Référence CVE CVE-2026-123868 https://www.cve.org/CVERecord?id=CVE-2026-123868 Référence CVE CVE-2026-123871 https://www.cve.org/CVERecord?id=CVE-2026-123871 Référence CVE CVE-2026-123872 https://www.cve.org/CVERecord?id=CVE-2026-123872 Référence CVE CVE-2026-123874 https://www.cve.org/CVERecord?id=CVE-2026-123874 Référence CVE CVE-2026-123875 https://www.cve.org/CVERecord?id=CVE-2026-123875 Référence CVE CVE-2026-123877 https://www.cve.org/CVERecord?id=CVE-2026-123877 Référence CVE CVE-2026-126051 https://www.cve.org/CVERecord?id=CVE-2026-126051 Référence CVE CVE-2026-13149 https://www.cve.org/CVERecord?id=CVE-2026-13149 Référence CVE CVE-2026-13697 https://www.cve.org/CVERecord?id=CVE-2026-13697 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14532 https://www.cve.org/CVERecord?id=CVE-2026-14532 Référence CVE CVE-2026-14643 https://www.cve.org/CVERecord?id=CVE-2026-14643 Référence CVE CVE-2026-15157 https://www.cve.org/CVERecord?id=CVE-2026-15157 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?i

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0492Kwetsbaarheden verholpen in Node.js

A certificate validation bypass in Node.js https.Agent causes identical TLS session-cache keys for requests with differing CA trust settings, enabling improper session reuse and potential exposure of confidential data to unauthorized servers.

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 11 Nov 2026 · Last source change 11 Nov 2026, 18:28 UTC · CWE-295 · Improper Certificate Validation

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-11-12
European sourceNo official EUVD mapping
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-123877 to remediation: access.redhat.com/CVE-2026-123877.
    Before
    remediation: access.redhat.com/CVE-2026-123877
    After
    remediation: access.redhat.com/CVE-2026-123877
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    nodejs22.src as a component of Red Hat Enterprise Linux 10; nodejs24.src as a component of Red Hat Enterprise Linux 10; nodejs26.src as a component of Red Hat Enterprise Linux 10; nodejs-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-full-i18n (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-full-i18n (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-libs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-libs (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging-bundler (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging-bundler (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:24) as a component of Red Hat Enterprise Linux 8; npm (nodejs:22) as a component of Red Hat Enterprise Linux 8; npm (nodejs:24) as a component of Red Hat Enterprise Linux 8; v8-12.4-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; v8-12.4-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; v8-13.6-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; and 24 more
    After
    nodejs22.src as a component of Red Hat Enterprise Linux 10; nodejs24.src as a component of Red Hat Enterprise Linux 10; nodejs26.src as a component of Red Hat Enterprise Linux 10; nodejs-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-full-i18n (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-full-i18n (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-libs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-libs (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging-bundler (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging-bundler (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:24) as a component of Red Hat Enterprise Linux 8; npm (nodejs:22) as a component of Red Hat Enterprise Linux 8; npm (nodejs:24) as a component of Red Hat Enterprise Linux 8; v8-12.4-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; v8-12.4-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; v8-13.6-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; and 21 more · Fixed: nodejs22-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-1:22.23.5-2.3.2.3.1.hum1@src as a component of Red Hat Hardened Images; nodejs22-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-devel-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-docs-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-full-i18n-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs22-libs-1:22.23.5-2.3.2.3.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-npm-1:10.9.9-1.22.23.5.2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-s390x-rpms as a component of Red Hat Hardened Images; nodejs22-npm-bin-1:22.23.5-2.3.2.3.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@s390x as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@src as a component of Red Hat Hardened Images; nodejs24-1:24.22.3-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; nodejs24-bin-1:24.22.3-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; and 45 more
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-123877 to remediation: access.redhat.com/CVE-2026-123877.
    Before
    remediation: access.redhat.com/CVE-2026-123877
    After
    remediation: access.redhat.com/CVE-2026-123877
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    nodejs20.src as a component of Red Hat Hardened Images; nodejs22.src as a component of Red Hat Hardened Images; nodejs24.src as a component of Red Hat Hardened Images; nodejs25.src as a component of Red Hat Hardened Images; nodejs26.src as a component of Red Hat Hardened Images
    After
    nodejs22.src as a component of Red Hat Enterprise Linux 10; nodejs24.src as a component of Red Hat Enterprise Linux 10; nodejs26.src as a component of Red Hat Enterprise Linux 10; nodejs-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-full-i18n (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-full-i18n (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-libs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-libs (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-nodemon (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging-bundler (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging-bundler (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-packaging (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs-packaging (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:22) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:24) as a component of Red Hat Enterprise Linux 8; npm (nodejs:22) as a component of Red Hat Enterprise Linux 8; npm (nodejs:24) as a component of Red Hat Enterprise Linux 8; v8-12.4-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; v8-12.4-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; v8-13.6-devel (nodejs:22) as a component of Red Hat Enterprise Linux 8; and 24 more
    Red Hat Product Security ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-123877 · cve.blacktree.nl