PULSE
FEED
ransomplay reclama a Minor League Baseball · US · Hospitalityransomn0n reclama a Company #213 · QAransomn0n reclama a Company #212 · ETransomdoommageddon reclama a K**** T**** H**** B****ransomcurious worm reclama a sacheminc.com · CA · Manufacturingransomcurious worm reclama a sbhny.org · USransomcurious worm reclama a shannonhealth.com · IE · Healthcareransomcurious worm reclama a baronandbudd.com · GB · Professional Servicesransomeverstake reclama a ki*****o.comransomcurious worm reclama a raleighortho.com · US · Healthcareransomcurious worm reclama a lifelinescreening.com · US · Healthcareransomcurious worm reclama a safcodental.com · SA · Healthcareransomcurious worm reclama a marquiscompanies.com · US · Professional Servicesransomcurious worm reclama a atlashp.com · Technologyransomplay reclama a Minor League Baseball · US · Hospitalityransomn0n reclama a Company #213 · QAransomn0n reclama a Company #212 · ETransomdoommageddon reclama a K**** T**** H**** B****ransomcurious worm reclama a sacheminc.com · CA · Manufacturingransomcurious worm reclama a sbhny.org · USransomcurious worm reclama a shannonhealth.com · IE · Healthcareransomcurious worm reclama a baronandbudd.com · GB · Professional Servicesransomeverstake reclama a ki*****o.comransomcurious worm reclama a raleighortho.com · US · Healthcareransomcurious worm reclama a lifelinescreening.com · US · Healthcareransomcurious worm reclama a safcodental.com · SA · Healthcareransomcurious worm reclama a marquiscompanies.com · US · Professional Servicesransomcurious worm reclama a atlashp.com · Technology
← Todos os CVEs
CVE Watch11 de nov. de 2026

CVE-2026-123862

An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib

CVSS

2.9

Baixa

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 11 de nov. de 2026 · Última mod.: 11 de nov. de 2026 · CWE-248

EPSS · 30d

Ainda não há histórico EPSS suficiente.

Descrição técnica

An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream's error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1265464.3 MÉD
22.5%
——7Viber for iOS through 29.4.0.24 fails to validate the logical screen width and height in received GIF headers, allowing attackers to crash the app. Attackers can send a crafted GIF with zero dimensions that triggers an uncaught NSInternalInconsistencyException, aborting the app with SIGABRT when opened.1d
CVE-2026-1260744.3 MÉD
43.2%
——13Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, ActiveStorage::Filename#base and #extension_with_delimiter, and therefore #extension, pass the stored filename unmodified to File.basename and File.extname, which raise ArgumentError when the name contains a NUL byte. Active Storage stores the client-supplied filename verbatim, so a user who is permitted to upload an attachment could persist such a filename on databases that accept NUL bytes in string columns, such as SQLite and MySQL/MariaDB. Each subsequent request that builds a variant or preview of the blob, opens it, or renders it as an Action Text attachment then raises, possibly resulting in a persistent DoS vulnerability for the pages that display the blob until it is purged or its filename is corrected. Applications that use PostgreSQL are not affected, because PostgreSQL rejects the row. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.1d
CVE-2026-1253325.9 MÉD
38.1%
——11Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, a forge.tls client accepts a ServerHello compression_method that it did not offer. When the client later handles ServerHelloDone, tls.createConnectionState() rejects the unsupported compression algorithm by throwing an Error that propagates from connection.process(). A malicious server or an on-path attacker can alter the unauthenticated ServerHello compression byte before the server Finished message and terminate a Node.js process when the application does not catch the exception. The affected client paths include direct forge.tls use, forge.tls.wrapSocket, and forge.http; forge.tls servers are not affected, and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.1d
CVE-2026-42966—
1.0%
——0Uncaught exception for some Intel(R) Neural Compressor software before version 3.8 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.1d
CVE-2026-174266.5 MÉD
8.8%
——3IBM Power Systems Firmware FW1060.00 through FW1060.81 could allow a remote attacker to cause a denial of service due to an unhandled exception.2d
CVE-2026-1235627.5 ALT
28.2%
——8devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller catches the returned promise. An attacker able to influence the timing or failure of serialized asynchronous values can terminate the Node.js process.2d