<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 21 Oct 2026 20:12:02 +0000</lastBuildDate>
    <item>
      <title>GHSA-8vvx-rff5-p5rq — Nodemailer: Nested structured recipient arrays bypass the parser depth limit and cause stack exhaustion DoS</title>
      <link>https://db.gcve.eu/vuln/ghsa-8vvx-rff5-p5rq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nodemailer&lt;/p&gt;
&lt;p&gt;## Submission metadata&lt;/p&gt;
&lt;p&gt;| Field | Value |
|---|---|
| Ecosystem | npm |
| Package | `nodemailer` |
| Repository | https://github.com/nodemailer/nodemailer |
| Tested commit | `40d52215aac65b811d7e131bc916f68605efd9d2` |
| Current tested version | `10.0.1` |
| Confirmed vulnerable versions | `2.7.2`, `3.0.0`, `7.0.11`, `9.1.1`, `10.0.1` |
| Proposed affected range | `&amp;gt;= 2.7.2, &amp;lt;= 10.0.1` |
| Patched version | 10.0.2 |&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Nodemailer 10.0.1 does not safely process deeply nested arrays supplied through recipient fields such as `to`, `cc`, and `bcc`.&lt;/p&gt;
&lt;p&gt;The public `MimeNodeAddressInput` type recursively permits arrays, but `MimeNode._parseAddresses()` flattens only the outermost array. A remaining nested array is passed to `addressparser()`, whose `Tokenizer` coerces the input with `.toString()`. Native `Array.prototype.toString()` recursively processes every nested array through `join()` and `toString()` until the V8 call stack is exhausted.&lt;/p&gt;
&lt;p&gt;A valid 10,021-byte JSON recipient value containing one address wrapped in 5,000 arrays causes:&lt;/p&gt;
&lt;p&gt;```text
RangeError: Maximum call stack size exceeded
```&lt;/p&gt;
&lt;p&gt;The exception occurs through the normal `sendMail()` API before the `maxRecipients` limit is evaluated. If the integrating application does not catch the synchronous exception around the complete `sendMail()` invocation, the Node.js worker or server process terminates.&lt;/p&gt;
&lt;p&gt;No SMTP server, remote host, large attachment, or successful email delivery is required.&lt;/p&gt;
&lt;p&gt;This is distinct from…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nodemailer&lt;/p&gt;
&lt;p&gt;## Submission metadata&lt;/p&gt;
&lt;p&gt;| Field | Value |
|---|---|
| Ecosystem | npm |
| Package | `nodemailer` |
| Repository | https://github.com/nodemailer/nodemailer |
| Tested commit | `40d52215aac65b811d7e131bc916f68605efd9d2` |
| Current tested version | `10.0.1` |
| Confirmed vulnerable versions | `2.7.2`, `3.0.0`, `7.0.11`, `9.1.1`, `10.0.1` |
| Proposed affected range | `&amp;gt;= 2.7.2, &amp;lt;= 10.0.1` |
| Patched version | 10.0.2 |&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Nodemailer 10.0.1 does not safely process deeply nested arrays supplied through recipient fields such as `to`, `cc`, and `bcc`.&lt;/p&gt;
&lt;p&gt;The public `MimeNodeAddressInput` type recursively permits arrays, but `MimeNode._parseAddresses()` flattens only the outermost array. A remaining nested array is passed to `addressparser()`, whose `Tokenizer` coerces the input with `.toString()`. Native `Array.prototype.toString()` recursively processes every nested array through `join()` and `toString()` until the V8 call stack is exhausted.&lt;/p&gt;
&lt;p&gt;A valid 10,021-byte JSON recipient value containing one address wrapped in 5,000 arrays causes:&lt;/p&gt;
&lt;p&gt;```text
RangeError: Maximum call stack size exceeded
```&lt;/p&gt;
&lt;p&gt;The exception occurs through the normal `sendMail()` API before the `maxRecipients` limit is evaluated. If the integrating application does not catch the synchronous exception around the complete `sendMail()` invocation, the Node.js worker or server process terminates.&lt;/p&gt;
&lt;p&gt;No SMTP server, remote host, large attachment, or successful email delivery is required.&lt;/p&gt;
&lt;p&gt;This is distinct from…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8vvx-rff5-p5rq</guid>
    </item>
  </channel>
</rss>
