Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain on-path position or control malicious SMTP server
-
DeliveryVictim initiates SMTP connection
-
ExploitStream continuation lines without completion
-
ExecutionQuadratic parser consumes CPU and memory
-
ImpactEvent loop blocked, service denial
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the vulnerable Nodemailer client to establish an SMTP connection to a server under attacker control, or the attacker to be on-path on an existing SMTP connection - the malicious continuation-line stream is delivered by the SMTP peer, not by an arbitrary remote client, and triggers before authentication completes. This is reflected in the CVSS AC:H and AT:P metrics. Limiting factors: the application must be configured to connect to an untrusted or attacker-influenceable SMTP server, or the network path must be compromised (e.g., no TLS, or TLS stripping/MITM); applications that only ever connect to a fixed, trusted, TLS-protected SMTP relay have substantially reduced exposure. No authentication (PR:N) or user interaction (UI:N) is required once the malicious server/position is in place. Remediation is upgrading to Nodemailer 10.0.10 or later. |
| Impact | This is a genuine but conditional availability risk, not a blanket critical. The CVSS 4.0 base score of 8.2 is driven entirely by high availability impact (VA:H) with no confidentiality or integrity impact (VC:N/VI:N), reflecting a pure denial-of-service via quadratic-complexity parsing (CWE-400) that blocks the Node.js event loop and exhausts memory. Critically, the vector itself tempers the score: AC:H and AT:P indicate elevated attack complexity and a specific attack requirement - the victim client must connect to a malicious SMTP server, or an attacker must occupy an on-path position on the SMTP connection. PR:N/UI:N confirm no authentication or user interaction is needed once that positioning exists, and the flaw triggers pre-authentication. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or weaponization. The practical priority is therefore moderate: the impact is real and the fix is clear, but exploitation presupposes either a compromised/attacker-run mail server the application trusts or network interposition, which meaningfully narrows the realistic attacker population compared to a typical AV:N/AC:L internet-facing flaw. |
| Exploit ScenarioDerived | An application using a vulnerable Nodemailer version is induced to connect to a mail server the attacker controls (or the attacker is on-path on the SMTP link). The server streams continuation reply lines indefinitely without sending a completion line before authentication; the quadratic parsing in SMTPConnection._onData/isPartialResponse pegs CPU and grows memory, freezing the Node.js event loop and taking the service down. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Denial of service in Nodemailer 3.0.0 through 10.0.9 allows an attacker-controlled or on-path SMTP server to stall a Node.js application by streaming SMTP continuation lines that never deliver a terminating completion line during the greeting/authentication phase. The vulnerable reply parser in SMTPConnection._onData and isPartialResponse re-evaluates its buffered response on every incoming chunk, so parsing cost grows quadratically with the size of the accumulated reply, blocking the single-threaded event loop and consuming memory before authentication completes. No public exploit code was identified at time of analysis, and exploitation is conditional: the client must be configured to connect to an untrusted or attacker-influenceable SMTP server, or an attacker must be positioned on-path on an interceptable SMTP connection, which is why the assessed vector carries AC:H and AT:P and this is a genuine but conditional availability risk rather than a blanket critical one.
RemediationAI
Upgrade to Nodemailer 10.0.10 or later - vendor-released patch: 10.0.10 - and confirm the change in your lockfile (npm ls nodemailer should report >= 10.0.10); because this is a transitive dependency in many stacks, update the parent package or add an override/resolution pin if the direct consumer has not yet bumped its range. Where immediate upgrade is not possible, apply compensating controls that directly target the delivery vector, accepting their trade-offs: force TLS on all SMTP connections with strict certificate validation (rejectUnauthorized: true, no opportunistic/stripped STARTTLS) so an on-path attacker cannot inject the continuation-line stream - this breaks any relay using self-signed or mismatched certificates; restrict the application to a fixed, hard-coded trusted relay hostname and port rather than user- or config-supplied SMTP targets, which removes attacker-supplied-server exposure but reduces configuration flexibility; enforce aggressive SMTP socket and greeting/response timeouts so an unterminated reply is torn down before the buffer grows large, at the cost of possibly aborting legitimate slow relays; and run outbound mail sending in a separate worker thread or child process with a memory cap so a blocked event loop is contained rather than taking down the whole application. See the advisories at https://github.com/nodemailer/nodemailer/security/advisories/GHSA-4g23-2xm8-66gc and https://www.vulncheck.com/advisories/nodemailer-3.0.0-before-10.0.10-denial-of-service-via-smtp-reply-parsing for the upstream fix details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Nodemailer is the widely used SMTP client library for Node.js, and the flaw lives in its SMTP reply parser rather than in any mail-processing logic. Under RFC 5321, an SMTP server returns multi-line replies where continuation lines are prefixed with a hyphen (for example '250-...') and the final line uses a space ('250 ...'); a client must buffer lines until it sees the completion line. In the affected code paths, SMTPConnection._onData repeatedly re-scans the growing accumulated response and isPartialResponse re-parses it on each chunk, producing quadratic (O(n^2)) time complexity per byte received instead of linear behavior. CWE-400 (Uncontrolled Resource Consumption) is the root-cause class: attacker-supplied input has no effective bound on how much cumulative work or memory it can force. Because Node.js executes application JavaScript on a single event-loop thread, the quadratic loop monopolizes the process, starving timers, I/O callbacks and other requests while memory grows with the unterminated buffer. The supplied CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N, base 8.2) is consistent with our independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H): network-reachable, high attack complexity, no privileges or user interaction required once the malicious peer or network position exists, with impact confined to availability. The PR:N metric confirms no authentication is needed, which matches the fact that the malicious stream is delivered before SMTP authentication completes. Exposure is bounded by the fact that the payload comes from the SMTP peer, not from an arbitrary remote client hitting the application directly, so deployments pinned to a fixed, trusted, TLS-validated relay are substantially less exposed.
Know when Node.js gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Network-reachable DoS triggered by a malicious/on-path SMTP peer so AV:N but AC:H; no auth needed pre-authentication so PR:N; only availability affected so C:N/I:N/A:H.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
2DescriptionCVE.org
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Technical POC Analysis
CWE-400 (Uncontrolled Resource Consumption), mechanism CWE-407 (Inefficient Algorithmic Complexity).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Nodemailer versions 3.0.0 through 10.0.9 contain a high-severity denial-of-service vulnerability that can stall Node.js applications during SMTP greeting or authentication when they connect to an attacker-controlled or on-path SMTP server; no public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis. Because this affects the email-sending path, business services that rely on Nodemailer for notifications, password resets, or workflow email could experience availability degradation or hangs if they use untrusted or interceptable SMTP endpoints. Leadership should prioritize inventory and egress controls while tracking vendor remediation.
No vendor-released patch identified at time of analysis; restrict SMTP egress to trusted servers, enforce TLS with certificate validation, set aggressive connection/greeting/auth timeouts, isolate mail-sending Node.js processes, and monitor event loop lag and memory usage.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
EUVD-2026-101755
GHSA-37fc-hcrp-mmff
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB