Patch only the product branches with a verified fix
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Published severityHigh→Operational 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.30% 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
Confirm that the asset runs nodejs node and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Cross-source reconciliation
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Cisco PSIRT: 18 affected or under-investigation product states without a fixed product state in the same current advisory
Debian Security Tracker: 1 affected package state with no published fix
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.
6 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 release
Source package
Vendor state
Fixed version
Evidence
Alpine v3.23v3.23 · main
nodejs
Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
3 current
cisco-sa-oct2026-node-js-Jj3SQ19u · CSAF 2.0 · revision 1.13.0 · interimCisco PSIRTVulnerabilities in Node.js and Brotli Affecting Cisco Products: October 2026
18 known affected
The vendor explicitly identifies these products as affected by this CVE.
Cisco Identity Services Engine Software
Cisco ISE Passive Identity Connector
Cisco Secure Malware Analytics
Cisco Nexus Dashboard Fabric Controller (NDFC), formerly Data Center Network Manager (DCNM)
Cisco has released software updates that address this vulnerability.
CVE-2026-105483 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames
1 known affected
The vendor explicitly identifies these products as affected by this CVE.
nodejs25.src as a component of Red Hat Hardened Images
Summary
A flaw was found in the Node.js TLS stack. Improper normalization of hostnames that use fullwidth Unicode digits to represent an IPv4 address can cause certificate hostname verification to accept a certificate that does not identify the intended peer. This may allow an attacker who can influence the connection target to impersonate a TLS server.
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
The vendor explicitly identifies these products as affected by this CVE.
SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs24
SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs24-devel
SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs24-docs
SUSE Linux Enterprise Module for Web and Scripting 15 SP7:npm24
SUSE Linux Enterprise Server 15 SP7:nodejs24
SUSE Linux Enterprise Server 15 SP7:nodejs24-devel
SUSE Linux Enterprise Server 15 SP7:nodejs24-docs
SUSE Linux Enterprise Server 15 SP7:npm24
SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs24
SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs24-devel
SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs24-docs
SUSE Linux Enterprise Server for SAP Applications 15 SP7:npm24
Summary
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-109100
No EUVD known-exploited evidence
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
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
7.4 · CVSS 3.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 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 flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
What
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
Why
The product does not validate, or incorrectly validates, a certificate.
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 Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
Why
The product does not validate, or incorrectly validates, a certificate.
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 Certificate Validation → 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-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:N/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.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.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.
NetworkUnauthenticatedCWE-295
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um beliebigen Programmcode auszuführen.
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20261028Security Bulletin 28 Oct 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Oct 2026, published on 28 October 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗INCIBE-CERT · Spanish · multiples-vulnerabilidades-en-productos-de-cisco-20Múltiples vulnerabilidades en productos de Cisco
Eric Fernald ha informado sobre una vulnerabilidad en ASA y FTD. Junto con las incidencias de Node.js comunicadas por Khai Tran y Sylvie Mayer, de OpenAI Codex Security, Hasan Flayyih Abdullah y anagnorisis2peripeteia, se reúnen 5 vulnerabilidades: 1 de severidad crítica y 4 altas. Su explotación podría permitir ejecutar código, divulgar información, eludir comprobaciones de seguridad o provocar denegaciones de servicio.
Official advisory ↗INCIBE-CERT · Spanish · actualizacion-30102026-multiples-vulnerabilidades-en-productos-de-cisco[Actualización 30/10/2026] Múltiples vulnerabilidades en productos de Cisco
Eric Fernald ha informado sobre una vulnerabilidad en ASA y FTD. Junto con las incidencias de Node.js comunicadas por Khai Tran y Sylvie Mayer, de OpenAI Codex Security, Hasan Flayyih Abdullah y anagnorisis2peripeteia, se reúnen 5 vulnerabilidades: 1 de severidad crítica y 4 altas. Su explotación podría permitir ejecutar código, divulgar información, eludir comprobaciones de seguridad o provocar denegaciones de servicio.
De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.
De multiples vulnérabilités ont été découvertes dans les produits Cisco. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un contournement de la politique de sécurité et un problème de sécurité non spécifié par l'éditeur.
Official advisory ↗CSIRT Italia · Italian · node.js-risolte-molteplici-vulnerabilita-1Node.js: risolte molteplici vulnerabilità
La vulnerabilità identificata tramite la CVE-2026-111497 - di tipo "Out-of-bounds Write", con CVSS v4.0 pari a 9.2 e già trattata nell'ambito dell' AL03/261026/CSIRT-ITA - interessa Google Brotli e i prodotti che integrano tale componente, tra cui alcune versioni di Node.js, ed è dovuta a una gestione non adeguata del decoder Brotli durante l'elaborazione di flussi di dati compressi. Un attaccante remoto non autenticato potrebbe sfruttare tale vulnerabilità, mediante l'invio di contenuti Brotli opportunamente predisposti, al fine di compromettere la disponibilità del servizio, ottenere l'accesso ad informazioni sensibili e, in determinate circostanze, eseguire codice arbitrario sui sistemi target.
La vulnerabilità identificata tramite la CVE-2026-105482 - di tipo "Improper Access Control" e con CVSS v3.x pari a 7.4 - interessa Node.js ed è dovuta a meccanismi di gestione non adeguati degli hostname contenenti caratteri NUL ( \0 ) nelle funzioni dns.resolve*() e dns.reverse() . In particolare, il nome host validato dall'applicazione può essere troncato silenziosamente dal resolver c-ares al primo carattere NUL , determinando una discrepanza tra il valore verificato dall'applicazione e quello effettivamente risolto. Un attaccante remoto non autenticato potrebbe sfruttare tale vulnerabilità, mediante l'invio di richieste opportunamente predisposte contenenti hostname manipolati, al fine di eludere i meccanismi di sicurezza basati su allowlist di domini e, in specifici scenari, realizzare attacchi di tipo Server-Side Request Forgery (SSRF) verso risorse interne.
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.
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 23 Oct 2026 · Last source change 2 Nov 2026, 15:37 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-10-24
European sourceENISA EUVD · EUVD-2026-109100
Product sourceVendor CSAF · Cisco PSIRT
Remediation sourceVendor CSAF · Cisco PSIRT
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
nodejs24 as a component of Red Hat Enterprise Linux 10; nodejs24-devel as a component of Red Hat Enterprise Linux 10; nodejs24-docs as a component of Red Hat Enterprise Linux 10; nodejs24-full-i18n as a component of Red Hat Enterprise Linux 10; nodejs24-libs as a component of Red Hat Enterprise Linux 10; nodejs24-npm 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-docs (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs-full-i18n (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs-libs (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs.src (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs (nodejs:26) as a component of Red Hat Enterprise Linux 9; npm (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs25.src as a component of Red Hat Hardened Images · Fixed: nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.src (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-docs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.noarch (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); and 125 more
After
nodejs25.src as a component of Red Hat Hardened Images · Fixed: nodejs24-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-1:24.22.1-3.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debuginfo-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debuginfo-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debuginfo-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debuginfo-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debugsource-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debugsource-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debugsource-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-debugsource-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-devel-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-devel-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-devel-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-devel-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-docs-1:24.22.1-3.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-full-i18n-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-full-i18n-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-full-i18n-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-full-i18n-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-debuginfo-1:24.22.1-3.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-debuginfo-1:24.22.1-3.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-debuginfo-1:24.22.1-3.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); nodejs24-libs-debuginfo-1:24.22.1-3.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 227 more
Affected versionsThe structured affected or fixed version information changed.
Before
node: 24.22.0 ≤ 24.22.0, 26.12.0 ≤ 26.12.0 · 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
After
node: 24.22.0 ≤ 24.22.0, 26.12.0 ≤ 26.12.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
Affected versionsThe structured affected or fixed version information changed.
Before
node: 24.22.0 ≤ 24.22.0, 26.12.0 ≤ 26.12.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
node: 24.22.0 ≤ 24.22.0, 26.12.0 ≤ 26.12.0 · 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
Affected versionsThe structured affected or fixed version information changed.
Before
nodejs24 as a component of Red Hat Enterprise Linux 10; nodejs24-devel as a component of Red Hat Enterprise Linux 10; nodejs24-docs as a component of Red Hat Enterprise Linux 10; nodejs24-full-i18n as a component of Red Hat Enterprise Linux 10; nodejs24-libs as a component of Red Hat Enterprise Linux 10; nodejs24-npm 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:24) 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:24) 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:24) 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:24) 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:24) as a component of Red Hat Enterprise Linux 8; nodejs.src (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs (nodejs:24) 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:24) as a component of Red Hat Enterprise Linux 8; v8-13.6-devel (nodejs:24) as a component of Red Hat Enterprise Linux 8; nodejs-docs (nodejs:24) as a component of Red Hat Enterprise Linux 9; nodejs-docs (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs-full-i18n (nodejs:24) as a component of Red Hat Enterprise Linux 9; nodejs-full-i18n (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs-libs (nodejs:24) as a component of Red Hat Enterprise Linux 9; nodejs-libs (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs.src (nodejs:24) as a component of Red Hat Enterprise Linux 9; nodejs.src (nodejs:26) as a component of Red Hat Enterprise Linux 9; and 5 more
After
nodejs24 as a component of Red Hat Enterprise Linux 10; nodejs24-devel as a component of Red Hat Enterprise Linux 10; nodejs24-docs as a component of Red Hat Enterprise Linux 10; nodejs24-full-i18n as a component of Red Hat Enterprise Linux 10; nodejs24-libs as a component of Red Hat Enterprise Linux 10; nodejs24-npm 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-docs (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs-full-i18n (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs-libs (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs.src (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs (nodejs:26) as a component of Red Hat Enterprise Linux 9; npm (nodejs:26) as a component of Red Hat Enterprise Linux 9; nodejs25.src as a component of Red Hat Hardened Images · Fixed: nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.src (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-debugsource-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-devel-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-docs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.noarch (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-full-i18n-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); nodejs-libs-debuginfo-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.x86_64 (nodejs:24) as a component of Red Hat Enterprise Linux AppStream (v. 8); and 125 more
Affected versionsThe structured affected or fixed version information changed.
Before
After
SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs24; SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs24-devel; SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs24-docs; SUSE Linux Enterprise Module for Web and Scripting 15 SP7:npm24; SUSE Linux Enterprise Server 15 SP7:nodejs24; SUSE Linux Enterprise Server 15 SP7:nodejs24-devel; SUSE Linux Enterprise Server 15 SP7:nodejs24-docs; SUSE Linux Enterprise Server 15 SP7:npm24; SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs24; SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs24-devel; SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs24-docs; SUSE Linux Enterprise Server for SAP Applications 15 SP7:npm24
Affected versionsThe structured affected or fixed version information changed.
Before
The authority advisory does not provide a concise affected-product range. · Fixed: The authority publishes remediation guidance. Confirm the exact fixed release in the linked primary advisory.
After
node: 24.22.0 ≤ 24.22.0, 26.12.0 ≤ 26.12.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
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.