PULSE
FEED
ransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcareransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcare
← Todos os CVEs
CVE Watch16 de nov. de 2026

CVE-2026-129301

mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object

CVSS

6.5

Média

EPSS

—

KEV

—

Exploit Today

—

0-100

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

EPSS · 30d

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

Descrição técnica

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.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
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.5h
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.5h
CVE-2026-1247247.5 ALT
—
———@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 1.0.0 through 3.2.5, when a request reaches the configured limit on the number of multipart parts, each further part is skipped without attaching an error listener to the skipped part stream. If the request body ends in the middle of such a skipped part, the vendored Dicer parser emits an error on that stream, and because nothing is listening Node.js raises an unhandled error event and the process exits. A single crafted unauthenticated request is therefore enough to crash the server. The bug is latent in the parser on its own and was first demonstrated through @fastify/multipart versions 10.1.2 through 10.1.4, which keep feeding the request body to the parser after a limit error, and it affects any consumer that sets a finite parts limit and parses request bodies that can be terminated early. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. There is no complete application level workaround because the crash happens inside the parser before application code runs, though consumers that set a finite parts limit should also attach an error listener to the parser stream.9h
CVE-2026-1281235.9 MÉD
40.5%
——12SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. From version 5.5.7 until versions 5.5.8 and 6.0.1, , @sveltejs/adapter-node can attempt to add a header to an immutable request in a context that causes the server to crash, denying service to any other requests routed to that server. This issue is fixed in 5.5.8 and 6.0.1.3d
CVE-2026-1281175.9 MÉD
41.8%
——13SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to versions 2.70.4 and 3.1.1, the reroute hook could rewrite an invalid percent-encoded pathname into a valid route and reach a comparison that decoded the original malformed pathname outside the guarded decoding operation. The resulting unhandled URIError could crash an adapter-node server and deny service to other requests. This issue is fixed in 2.70.4 and 3.1.1.3d
CVE-2026-1280776.5 MÉD
19.5%
——6Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.4, Nuxt parses a request path beginning with // as a URL host before rendering a page, while Nitro server/middleware and routeRules continue to evaluate the original path. An unauthenticated request such as //x/admin can therefore resolve to the /admin page without route-scoped serverHandlers, server/middleware path checks, redirects, or security headers configured for /admin. API handlers in server/api and server/routes, appMiddleware, page middleware are unaffected. This issue is fixed in version 4.6.4.7h