mailparser 3.9.38 → 3.9.39

package/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-    ".": "3.9.38"
+    ".": "3.9.39"
 }

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [3.9.39](https://github.com/nodemailer/mailparser/compare/v3.9.38...v3.9.39) (2026-10-14)
+
+
+### Bug Fixes
+
+* **deps:** update nodemailer to 10.1.1, libmime to 5.4.8 and mailsplit to 5.4.21 ([43ddf3e](https://github.com/nodemailer/mailparser/commit/43ddf3e9214b2a14b20319d1679ffe001a3a6889))
+
 ## [3.9.38](https://github.com/nodemailer/mailparser/compare/v3.9.37...v3.9.38) (2026-10-10)
 
 

package/SECURITY.md

@@ -3,21 +3,24 @@
 mailparser is an email parsing library for Node.js. It is routinely pointed at
 untrusted, adversarial, and malformed messages, so parser robustness is a
 security concern: a crafted message should never be able to crash the host
-process, exhaust memory or CPU, pollute prototypes, or leak data across parses.
-We take security reports seriously and aim to respond quickly.
+process, exhaust memory or CPU through amplification, pollute prototypes, or
+leak data across parses. We welcome responsible reports of vulnerabilities that
+present a credible security risk to users. Please distinguish security
+vulnerabilities from ordinary bugs, unusual edge cases, and hardening
+suggestions.
 
 ## Supported Versions
 
-Security fixes are released only against the latest version. We do not backport
-patches to older releases - upgrading to the current 3.x release line is the
-supported way to receive security updates.
+Security fixes are released only against the latest major version. We do not
+backport patches to older majors, so upgrading to the current release line is
+the supported way to receive security updates.
 
 | Version | Supported          |
 | ------- | ------------------ |
 | 3.x     | :white_check_mark: |
 | < 3.0   | :x:                |
 
-If you are on an older version, please upgrade. See the release notes at
+If you are on an older major, please upgrade. See the release notes at
 <https://github.com/nodemailer/mailparser/releases> before updating.
 
 > [!NOTE]
@@ -26,51 +29,126 @@ If you are on an older version, please upgrade. See the release notes at
 > [PostalMime](https://github.com/postalsys/postal-mime), which works in both
 > Node.js and browser environments.
 
-## Reporting a Vulnerability
+## What Qualifies as a Security Vulnerability
 
-**Please do not report security vulnerabilities through public GitHub issues,
-pull requests, or discussions.**
+A security report should identify a realistic way for an attacker to cross a
+security boundary in a supported version of mailparser. Unexpected behavior, a
+failing test, or a technically correct proof of concept is not sufficient on its
+own to establish security impact.
 
-Report privately through one of the following channels:
+In particular, explain:
 
-1. **GitHub Security Advisories (preferred).** Open a private report at
-   <https://github.com/nodemailer/mailparser/security/advisories/new>. This keeps
-   the discussion private until a fix is published and lets us credit you.
-2. **Email.** Send details to **andris@postalsys.com** (the contact listed in
-   [`SECURITY.txt`](SECURITY.txt)). Encrypt sensitive details if possible - our
-   PGP key fingerprint is `5D952A46E1D8C931F6364E01DC6C83F4D584D364`.
+- **Attacker capabilities:** Who is the attacker, and what inputs, systems, or
+  responses can they control _without_ already having the privileges or secrets
+  they are trying to gain?
+- **Attack path:** How does attacker-controlled input reach the affected code
+  through a supported public API or a realistic application integration?
+- **Prerequisites:** What configuration and user actions are required? If the
+  attack depends on unusual options or deliberately malformed input, explain why
+  those conditions could arise in a real application.
+- **Impact:** What confidentiality, integrity, or availability boundary is
+  crossed, and what can the attacker achieve as a result?
 
-When reporting, please include as much of the following as you can:
+A vulnerability involving an optional or less common feature can still qualify
+if these conditions are met. Conversely, the existence of a defensive check in
+the code does not, by itself, establish that every bypass of that check has a
+realistic security impact.
 
-- The affected version(s) and environment (mailparser version, Node.js version,
-  OS).
-- A clear description of the issue and its impact (e.g. denial of service via
-  CPU or memory exhaustion, ReDoS, prototype pollution, unhandled exception that
-  crashes the process, information disclosure between parses).
-- A minimal proof of concept - ideally the raw `.eml` sample or a short script
-  that reproduces the issue.
-- Any suggested remediation, if you have one.
+## Reporting a Vulnerability
 
-We are a small team, so there is no guaranteed response time - sometimes reports
-are handled within hours, sometimes they take longer. Accepted issues are fixed
-in a new release and coordinated through a GitHub Security Advisory, and
-reporters who wish to be named are credited.
+**Do not disclose suspected exploitable vulnerabilities through public GitHub
+issues, pull requests, or discussions before coordinating with the
+maintainers.**
 
-## CVEs
+Report privately through one of the following channels:
 
-We track and disclose vulnerabilities through GitHub Security Advisories. We do
-not request or manage CVE identifiers ourselves. If you need a CVE assigned for a
-reported issue, please request one yourself - for example, through GitHub's own
-CVE request flow on the published advisory, or another CNA.
+1. **GitHub Security Advisories (preferred):**
+   <https://github.com/nodemailer/mailparser/security/advisories/new>.
+2. **Email:** **andris@postalsys.com**, as listed in
+   [`SECURITY.txt`](SECURITY.txt). Encrypt sensitive details if possible.
+
+### Required Information
+
+Please provide enough information to evaluate both the defect and its security
+impact. Reports should include:
+
+1. The affected mailparser version or commit, Node.js version, and relevant
+   configuration.
+2. A concise description of the issue and the affected public API or code path
+   (`MailParser` or `simpleParser`. The raw `.eml` sample that triggers the
+   issue is the most useful reproduction).
+3. A minimal, tested reproduction, including steps to run it, expected behavior,
+   and observed behavior.
+4. A concrete threat model: attacker control, prerequisites, trust boundary, and
+   resulting impact. Clearly distinguish what your reproduction proves from what
+   you believe might be possible.
+5. An explanation of why the issue affects real deployments beyond a
+   deliberately constructed test setup, where this is not obvious.
+
+A suggested fix is welcome but does not replace an explanation of
+exploitability. A complete real-world exploit is not always necessary, but the
+report must make a credible security impact clear.
+
+### Reports That May Be Treated as Ordinary Bugs
+
+The following generally do **not** qualify for private security handling unless
+you can demonstrate an additional, meaningful security boundary crossing:
+
+- Issues that require the attacker to control trusted application code,
+  administrator-only configuration, or the secret they supposedly extract.
+- Problems caused solely by application-level misuse, exposed credentials, or
+  insecure deployment choices outside mailparser's control.
+- Contrived proof-of-concept setups where the tester controls both sides of a
+  request, without explaining how a separate attacker could trigger the issue.
+- Parser quirks, unexpected behavior, and bypasses of internal checks with no
+  demonstrated security impact.
+- Speculative findings based only on static analysis or an automated tool's
+  assessment, without a verified reproduction and credible attack scenario.
+
+These may still be valid bugs and may be considered through the normal issue
+tracker. Please coordinate before making any potentially exploitable details
+public. Classification as a bug does not guarantee a fix or a particular
+priority.
+
+### Automated and AI-Assisted Reports
+
+Automated analysis and AI tools are welcome as research aids, but the person
+submitting a report is responsible for verifying its claims. **Do not submit
+bulk, unverified, or speculative AI-generated findings.** Test each finding
+against a supported release and establish the actual security impact. Reports
+that do not meet the requirements above may be closed without further
+investigation or individual feedback; they can be resubmitted with stronger
+evidence.
+
+## Triage and Disclosure
+
+mailparser is maintained by a small team, and there is **no guaranteed response
+or resolution time**. Reports are prioritized based on demonstrated impact,
+exploitability, affected usage, and available maintenance resources.
+
+A private report does not automatically become a security advisory. Confirmed
+vulnerabilities may be fixed and disclosed through GitHub Security Advisories;
+other findings may be closed, deferred, or handled as ordinary bugs. Please do
+not disclose details of an unresolved, potentially exploitable issue publicly
+without coordinating with the maintainers.
+
+## CVEs and Credit
+
+We do not request or manage CVE identifiers. A report being acknowledged, a bug
+being fixed, or a pull request being merged does **not** mean that mailparser
+has confirmed a security vulnerability or endorsed a CVE assignment. We do not
+guarantee advisories, CVE identifiers, or public credit for reports. For
+confirmed vulnerabilities disclosed through an advisory, substantive reporters
+may be credited if they wish.
 
 ## Scope
 
-In scope: the mailparser library source in this repository - the streaming MIME
+In scope: the mailparser library source in this repository: the streaming MIME
 parser (`MailParser`), the convenience parser (`simpleParser`), header and
-address decoding, charset/transfer-encoding handling, and attachment and HTML/
-text extraction. Of particular interest are inputs that cause unbounded resource
-consumption, catastrophic regular-expression backtracking, prototype pollution,
-or process crashes.
+address decoding, charset and transfer-encoding handling, and attachment and
+HTML/text extraction. Of particular interest are small crafted inputs that cause
+amplified resource consumption, catastrophic regular-expression backtracking,
+prototype pollution, or process crashes.
 
 Out of scope:
 
@@ -78,13 +156,11 @@ Out of scope:
   Parsed email content is attacker-controlled data; you must sanitize and escape
   it before rendering, storing, or executing it. In particular, the `html` field
   is not sanitized for safe display in a browser.
-- Vulnerabilities in third-party dependencies that are already tracked and fixed
-  upstream - report those to the respective project (we will still bump the
-  dependency once a fix is available).
-- Issues that require an already-compromised host or a malicious local
-  environment.
 - Resource consumption that is proportional to a legitimately large input (for
   example, parsing a genuine 100MB message uses memory) rather than amplified by
   a crafted small input.
+- Vulnerabilities in third-party dependencies that are already tracked upstream
+  (we will still bump the dependency once a fix is available).
+- Social-engineering reports.
 
 Thank you for helping keep mailparser and its users safe.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "mailparser",
-    "version": "3.9.38",
+    "version": "3.9.39",
     "description": "Parse e-mails",
     "main": "index.js",
     "scripts": {
@@ -22,10 +22,10 @@
         "he": "1.2.0",
         "html-to-text": "10.0.1",
         "iconv-lite": "0.7.3",
-        "libmime": "5.4.7",
+        "libmime": "5.4.8",
         "linkify-it": "5.0.2",
-        "@zone-eu/mailsplit": "5.4.20",
-        "nodemailer": "10.1.0",
+        "@zone-eu/mailsplit": "5.4.21",
+        "nodemailer": "10.1.1",
         "punycode.js": "2.3.1",
         "tlds": "1.261.0"
     },
@@ -41,7 +41,7 @@
         "grunt-contrib-nodeunit": "5.0.0",
         "grunt-eslint": "27.0.0",
         "iconv": "3.0.1",
-        "prettier": "3.9.9",
+        "prettier": "3.9.10",
         "random-message": "1.1.0"
     },
     "repository": {