nodemailer 10.0.7 → 10.0.8

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # CHANGELOG
 
+## [10.0.8](https://github.com/nodemailer/nodemailer/compare/v10.0.7...v10.0.8) (2026-09-11)
+
+
+### Bug Fixes
+
+* **mime-node:** clean the boundary where it is written, not only where it is built ([e14278d](https://github.com/nodemailer/nodemailer/commit/e14278d2dae9427280c79450605a27b1c5d2c355))
+* **mime-node:** drop every control character from multipart boundary material ([a82a355](https://github.com/nodemailer/nodemailer/commit/a82a35554848a2e07485ff81f80aefe2736e5a04))
+
 ## [10.0.7](https://github.com/nodemailer/nodemailer/compare/v10.0.6...v10.0.7) (2026-09-11)
 
 

package/dist/cjs/mime-node/index.js

@@ -100,13 +100,21 @@ function normalizeDomain(domain, toUnicode) {
     return toUnicode ? punycode.toUnicode(domain) : punycode.toASCII(domain);
 }
 /**
- * Removes the line breaks that would split a value across lines once it is written out.
+ * Removes the characters that must never reach a multipart delimiter line.
+ *
+ * A line break splits the delimiter, so the boundary declared in the header can never
+ * match it again and the parts go out as body lines instead. The other C0 controls and
+ * DEL do not split anything but must not be written either: RFC 5321 does not allow a
+ * NUL in DATA at all, and an MTA or a scanner that stops at one reads a different
+ * message than a client that does not, which is the same parser disagreement a split
+ * delimiter creates. Both sides are cleaned together, since the declared value and the
+ * delimiters come from this one result.
  *
  * @param value Value to clean
- * @return Value with every CR and LF removed
+ * @return Value with every control character removed
  */
-function _stripLineBreaks(value) {
-    return value.replace(/[\r\n]+/g, '');
+function _stripBoundaryControls(value) {
+    return value.replace(/[\x00-\x1f\x7f]+/g, '');
 }
 /**
  * Creates a new mime tree node. Assumes 'multipart/*' as the content type
@@ -128,12 +136,11 @@ class MimeNode {
         this.nodeCounter = 0;
         options = options || {};
         /**
-         * shared part of the unique multipart boundary. A line break here would split
-         * the delimiter lines the tree is streamed with, so the declared boundary could
-         * never match them again and the remainder would go out as body lines
+         * shared part of the unique multipart boundary. Control characters are dropped
+         * here rather than at the delimiter, see _stripBoundaryControls
          */
-        this.baseBoundary = _stripLineBreaks(options.baseBoundary || node_crypto_1.default.randomBytes(8).toString('hex'));
-        this.boundaryPrefix = _stripLineBreaks(options.boundaryPrefix || '--_NmP');
+        this.baseBoundary = _stripBoundaryControls(options.baseBoundary || node_crypto_1.default.randomBytes(8).toString('hex'));
+        this.boundaryPrefix = _stripBoundaryControls(options.boundaryPrefix || '--_NmP');
         this.disableFileAccess = !!options.disableFileAccess;
         this.disableUrlAccess = !!options.disableUrlAccess;
         this.normalizeHeaderKey = options.normalizeHeaderKey;
@@ -1180,19 +1187,20 @@ class MimeNode {
         this.contentType = structured.value.trim().toLowerCase();
         this.multipart = /^multipart\//i.test(this.contentType) ? this.contentType.substr(this.contentType.indexOf('/') + 1) : false;
         if (this.multipart) {
-            // A line break in the boundary would split the delimiter lines the tree is
-            // streamed with, so the declared boundary could never match them again and
-            // the remainder would go out as body lines. The declared value and the
-            // delimiters are assigned from the same expression here, so whatever the
-            // header emitter then does with it, the two sides cannot disagree.
+            // The declared value and the delimiters are assigned from the same expression
+            // here, so whatever the header emitter then does with it, the two sides cannot
+            // disagree about which characters the boundary is made of.
             //
             // Stripping runs before the fallback rather than over the whole chain: a
-            // boundary that was nothing but line breaks would otherwise strip to '' and
+            // boundary made only of control characters would otherwise strip to '' and
             // leave the node declaring no boundary and streaming bare '--' delimiters.
-            // The generated boundary is stripped too, since baseBoundary and
-            // boundaryPrefix are public and may have been written after construction.
-            const declared = _stripLineBreaks(structured.params.boundary || this.boundary || '');
-            this.boundary = structured.params.boundary = declared || _stripLineBreaks(this._generateBoundary());
+            // _generateBoundary cleans what it builds, but this is the one place the boundary
+            // is written, so it cleans the value it is about to write rather than trusting
+            // where it came from. MimeNode is exported and subclassable, so the generator is
+            // not necessarily the one below. Stripping twice costs nothing, it is idempotent.
+            const declared = _stripBoundaryControls(structured.params.boundary || this.boundary || '');
+            this.boundary = structured.params.boundary =
+                declared || _stripBoundaryControls(this._generateBoundary());
         }
         else {
             this.boundary = false;
@@ -1205,7 +1213,9 @@ class MimeNode {
      * @internal
      */
     _generateBoundary() {
-        return this.rootNode.boundaryPrefix + '-' + this.rootNode.baseBoundary + '-Part_' + this._nodeId;
+        // baseBoundary and boundaryPrefix are public, so they may hold something the
+        // constructor never cleaned, and the -Part_ suffix keeps the result non empty
+        return _stripBoundaryControls(this.rootNode.boundaryPrefix + '-' + this.rootNode.baseBoundary) + '-Part_' + this._nodeId;
     }
     /**
      * Encodes a header value for use in the generated rfc2822 email.

package/dist/cjs/package-info.d.ts

@@ -1,3 +1,3 @@
 export declare const name = "nodemailer";
-export declare const version = "10.0.7";
+export declare const version = "10.0.8";
 export declare const homepage = "https://nodemailer.com/";

package/dist/cjs/package-info.js

@@ -3,5 +3,5 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.homepage = exports.version = exports.name = void 0;
 exports.name = 'nodemailer';
-exports.version = '10.0.7';
+exports.version = '10.0.8';
 exports.homepage = 'https://nodemailer.com/';

package/dist/esm/mime-node/index.js

@@ -62,13 +62,21 @@ function normalizeDomain(domain, toUnicode) {
     return toUnicode ? punycode.toUnicode(domain) : punycode.toASCII(domain);
 }
 /**
- * Removes the line breaks that would split a value across lines once it is written out.
+ * Removes the characters that must never reach a multipart delimiter line.
+ *
+ * A line break splits the delimiter, so the boundary declared in the header can never
+ * match it again and the parts go out as body lines instead. The other C0 controls and
+ * DEL do not split anything but must not be written either: RFC 5321 does not allow a
+ * NUL in DATA at all, and an MTA or a scanner that stops at one reads a different
+ * message than a client that does not, which is the same parser disagreement a split
+ * delimiter creates. Both sides are cleaned together, since the declared value and the
+ * delimiters come from this one result.
  *
  * @param value Value to clean
- * @return Value with every CR and LF removed
+ * @return Value with every control character removed
  */
-function _stripLineBreaks(value) {
-    return value.replace(/[\r\n]+/g, '');
+function _stripBoundaryControls(value) {
+    return value.replace(/[\x00-\x1f\x7f]+/g, '');
 }
 /**
  * Creates a new mime tree node. Assumes 'multipart/*' as the content type
@@ -90,12 +98,11 @@ class MimeNode {
         this.nodeCounter = 0;
         options = options || {};
         /**
-         * shared part of the unique multipart boundary. A line break here would split
-         * the delimiter lines the tree is streamed with, so the declared boundary could
-         * never match them again and the remainder would go out as body lines
+         * shared part of the unique multipart boundary. Control characters are dropped
+         * here rather than at the delimiter, see _stripBoundaryControls
          */
-        this.baseBoundary = _stripLineBreaks(options.baseBoundary || crypto.randomBytes(8).toString('hex'));
-        this.boundaryPrefix = _stripLineBreaks(options.boundaryPrefix || '--_NmP');
+        this.baseBoundary = _stripBoundaryControls(options.baseBoundary || crypto.randomBytes(8).toString('hex'));
+        this.boundaryPrefix = _stripBoundaryControls(options.boundaryPrefix || '--_NmP');
         this.disableFileAccess = !!options.disableFileAccess;
         this.disableUrlAccess = !!options.disableUrlAccess;
         this.normalizeHeaderKey = options.normalizeHeaderKey;
@@ -1142,19 +1149,20 @@ class MimeNode {
         this.contentType = structured.value.trim().toLowerCase();
         this.multipart = /^multipart\//i.test(this.contentType) ? this.contentType.substr(this.contentType.indexOf('/') + 1) : false;
         if (this.multipart) {
-            // A line break in the boundary would split the delimiter lines the tree is
-            // streamed with, so the declared boundary could never match them again and
-            // the remainder would go out as body lines. The declared value and the
-            // delimiters are assigned from the same expression here, so whatever the
-            // header emitter then does with it, the two sides cannot disagree.
+            // The declared value and the delimiters are assigned from the same expression
+            // here, so whatever the header emitter then does with it, the two sides cannot
+            // disagree about which characters the boundary is made of.
             //
             // Stripping runs before the fallback rather than over the whole chain: a
-            // boundary that was nothing but line breaks would otherwise strip to '' and
+            // boundary made only of control characters would otherwise strip to '' and
             // leave the node declaring no boundary and streaming bare '--' delimiters.
-            // The generated boundary is stripped too, since baseBoundary and
-            // boundaryPrefix are public and may have been written after construction.
-            const declared = _stripLineBreaks(structured.params.boundary || this.boundary || '');
-            this.boundary = structured.params.boundary = declared || _stripLineBreaks(this._generateBoundary());
+            // _generateBoundary cleans what it builds, but this is the one place the boundary
+            // is written, so it cleans the value it is about to write rather than trusting
+            // where it came from. MimeNode is exported and subclassable, so the generator is
+            // not necessarily the one below. Stripping twice costs nothing, it is idempotent.
+            const declared = _stripBoundaryControls(structured.params.boundary || this.boundary || '');
+            this.boundary = structured.params.boundary =
+                declared || _stripBoundaryControls(this._generateBoundary());
         }
         else {
             this.boundary = false;
@@ -1167,7 +1175,9 @@ class MimeNode {
      * @internal
      */
     _generateBoundary() {
-        return this.rootNode.boundaryPrefix + '-' + this.rootNode.baseBoundary + '-Part_' + this._nodeId;
+        // baseBoundary and boundaryPrefix are public, so they may hold something the
+        // constructor never cleaned, and the -Part_ suffix keeps the result non empty
+        return _stripBoundaryControls(this.rootNode.boundaryPrefix + '-' + this.rootNode.baseBoundary) + '-Part_' + this._nodeId;
     }
     /**
      * Encodes a header value for use in the generated rfc2822 email.

package/dist/esm/package-info.d.ts

@@ -1,3 +1,3 @@
 export declare const name = "nodemailer";
-export declare const version = "10.0.7";
+export declare const version = "10.0.8";
 export declare const homepage = "https://nodemailer.com/";

package/dist/esm/package-info.js

@@ -1,4 +1,4 @@
 // Generated by scripts/build.js from package.json. Do not edit by hand.
 export const name = 'nodemailer';
-export const version = '10.0.7';
+export const version = '10.0.8';
 export const homepage = 'https://nodemailer.com/';

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "nodemailer",
-    "version": "10.0.7",
+    "version": "10.0.8",
     "description": "Easy as cake e-mail sending from your Node.js applications",
     "type": "module",
     "main": "./dist/cjs/nodemailer.js",