PULSE
FEED
ransomqilin reclama a Strategic Properties · USransomqilin reclama a The Ashland Water Group · US · Energy & Utilitiesransomqilin reclama a The National Commission on Indigenous Peoples · PH · Government & Defenseransomchaos reclama a radienzliving.com · DE · Retail & E-Commerceransomchaos reclama a amarok.com · Technologyransomvortex reclama a APELLIS · US · Healthcareransomglobal secret group reclama a Johnson Bros. Bakery Supply, Inc. · US · Agriculture and Food Productionransomcurious worm reclama a t**l**kw*****p.com · Technologyransomqilin reclama a Airways Aviation · AE · Transportationransomqilin reclama a Ayala Property Management · PH · Otherransomqilin reclama a California Cross Dock · US · Transportationransomqilin reclama a Fahrenheit DDB · PE · Professional Servicesransomqilin reclama a Hybrytec · AU · Technologyransomqilin reclama a IMS Messsysteme · DE · Manufacturingransomqilin reclama a Strategic Properties · USransomqilin reclama a The Ashland Water Group · US · Energy & Utilitiesransomqilin reclama a The National Commission on Indigenous Peoples · PH · Government & Defenseransomchaos reclama a radienzliving.com · DE · Retail & E-Commerceransomchaos reclama a amarok.com · Technologyransomvortex reclama a APELLIS · US · Healthcareransomglobal secret group reclama a Johnson Bros. Bakery Supply, Inc. · US · Agriculture and Food Productionransomcurious worm reclama a t**l**kw*****p.com · Technologyransomqilin reclama a Airways Aviation · AE · Transportationransomqilin reclama a Ayala Property Management · PH · Otherransomqilin reclama a California Cross Dock · US · Transportationransomqilin reclama a Fahrenheit DDB · PE · Professional Servicesransomqilin reclama a Hybrytec · AU · Technologyransomqilin reclama a IMS Messsysteme · DE · Manufacturing
← Todos os CVEs
CVE Watch15 de jul. de 2026

CVE-2025-59465

A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` er

CVSS

7.5

Alta

EPSS

4.0%

p91

KEV

—

Exploit Today

27

0-100

Publicado: 20 de jan. de 2026 · Última mod.: 15 de jul. de 2026 · CWE-400 · CWE-248

EPSS · 30d
4.0%EPSS · 30 dias4.0%
2026-10-192026-11-15
Descrição técnica

A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example: ``` server.on('secureConnection', socket => { socket.on('error', err => { console.log(err) }) }) ```

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-95839—
—
———containerd is an open-source container runtime. From 2.2.0 until 2.2.10, 2.3.7, and 2.4.2, image manifest processing through the transfer service can encounter a child descriptor containing the io.containerd.manifest.subject annotation and a malformed digest. Pulling or importing such an image, including through a default CRI PullImage request, can trigger an unrecovered panic and crash the containerd daemon. In Kubernetes, kubelet retries can repeatedly trigger the crash and disrupt container operations on the worker node. This issue is fixed in versions 2.2.10, 2.3.7, and 2.4.2.6h
CVE-2026-1293027.5 ALT
—
———Guard Core is an API security core engine for the FastAPI-Guard, FlaskAPI Guard, and DjAPI Guard adapters. From 3.5.0 until 3.13.0, built-in penetration-detection patterns in guard_core/handlers/suspatterns_handler.py execute through a direct pattern.search(content) call instead of the timeout-protected create_safe_matcher() path used for custom patterns. The built-in template-injection detector contains an unbounded expression with quadratic behavior when scanning repeated opening braces. Because penetration detection and enhanced mode are enabled by a stock SecurityConfig, an unauthenticated request can block the shared asyncio event loop, affecting all application endpoints. The triggering input does not produce a detection match, so the request can complete without incrementing ban counters or being recorded as suspicious. This issue is fixed in version 3.13.0.6h
CVE-2026-1293016.5 MÉD
—
———mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3.8h
CVE-2026-1293005.3 MÉD
—
———mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.7.0 until 4.6.3, receiveds_format() in src/mailparser/utils.py catches only TypeError and ValueError while converting the trailing date of an attacker-controlled Received header. An out-of-range year can cause calendar.timegm() to raise OverflowError, and a sufficiently large timezone offset can cause datetime.fromtimestamp() to raise OSError. These exceptions are outside the MailParserError hierarchy, so one crafted header can abort the entire message parse through every parse_from_* entry point and may drop a queued batch. This issue is fixed in version 4.6.3.8h
CVE-2026-1292996.5 MÉD
—
———mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, multiple message-processing behaviors can raise exceptions or silently lose content. Headers colliding with methods such as Parse, Message, and Write_Attachments can place bound method objects into parsed output and raise TypeError when a caller requests JSON serialization such as mail_json. When byte input is parsed through parse_from_bytes(), an 8-bit header value returned as email.header.Header can likewise raise TypeError when an X_raw accessor passes the value to json.dumps; both exceptions are outside the MailParserError hierarchy. Separately, rewritten names such as Subject_json and X_Spam_Flag can be substituted or disappear from mail, headers, and JSON output while has_defects remains false, and a headerless message can be treated as falsy before parser state is initialized, causing body and attachment properties to return empty values without an error signal. These behaviors can abort message processing or hide malicious indicators from downstream scanners. This issue is fixed in version 4.6.2.7h
CVE-2026-1288425.3 MÉD
—
———@fastify/busboy is a streaming parser for multipart and url-encoded form data used by Fastify. In versions 1.0.0 through 3.2.5, the url-encoded parser stops accumulating a field only when the decoded length exactly equals the configured per-field size limit, and a malformed percent escape is passed through verbatim by the decoder, so the decoded length can jump from just below the limit to just above it and skip that equality check. The parser then keeps buffering the field in memory until the next delimiter or the end of the request, so a single unauthenticated url-encoded field or field name can grow to the size of the whole request body regardless of a much smaller configured per-field limit, with memory use bounded only by the independent whole-request body limit. The issue is fixed in @fastify/busboy 3.2.6, which clamps a field as soon as the decoded length reaches or exceeds the limit, and users should upgrade to 3.2.6 or later. As a workaround, set a conservative whole-request body limit so the per-field overshoot cannot exceed it.6h