Skip to content

[Snyk] Upgrade nodemailer from 6.9.3 to 6.10.1 - #74

Open
X-oss-byte wants to merge 1 commit into
devfrom
snyk-upgrade-0fbd05494a2c9c5184985c55fbcd172c
Open

[Snyk] Upgrade nodemailer from 6.9.3 to 6.10.1#74
X-oss-byte wants to merge 1 commit into
devfrom
snyk-upgrade-0fbd05494a2c9c5184985c55fbcd172c

Conversation

@X-oss-byte

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade nodemailer from 6.9.3 to 6.10.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 15 versions ahead of your current version.

  • The recommended version was released 10 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-NODEMAILER-6219989
586 Proof of Concept
Release notes
Package name: nodemailer
  • 6.10.1 - 2025-04-13

    6.10.1 (2025-02-06)

    Bug Fixes

  • 6.10.0 - 2025-01-23

    6.10.0 (2025-01-23)

    Features

    • services: add Seznam email service configuration (#1695) (d1ae0a8)

    Bug Fixes

    • proxy: Set error and timeout errors for proxied sockets (aa0c99c)
  • 6.9.16 - 2024-10-28

    6.9.16 (2024-10-28)

    Bug Fixes

    • addressparser: Correctly detect if user local part is attached to domain part (f2096c5)
  • 6.9.15 - 2024-09-03

    6.9.15 (2024-08-08)

    Bug Fixes

  • 6.9.14 - 2024-06-19

    6.9.14 (2024-06-19)

    Bug Fixes

    • api: Added support for Ethereal authentication (56b2205)
    • services.json: Add Email Services Provider Feishu Mail (CN) (#1648) (e9e9ecc)
    • services.json: update Mailtrap host and port in well known (#1652) (fc2c9ea)
    • well-known-services: Add Loopia in well known services (#1655) (21a28a1)
  • 6.9.13 - 2024-03-20

    6.9.13 (2024-03-20)

    Bug Fixes

    • tls: Ensure servername for SMTP (d66fdd3)
  • 6.9.12 - 2024-03-08

    6.9.12 (2024-03-08)

    Bug Fixes

    • message-generation: Escape single quote in address names (4ae5fad)
  • 6.9.11 - 2024-02-29

    6.9.11 (2024-02-29)

    Bug Fixes

    • headers: Ensure that Content-type is the bottom header (c7cf97e)
  • 6.9.10 - 2024-02-22

    6.9.10 (2024-02-22)

    Bug Fixes

    • data-uri: Do not use regular expressions for parsing data URI schemes (12e65e9)
    • data-uri: Moved all data-uri regexes to use the non-regex parseDataUri method (edd5dfe)
  • 6.9.9 - 2024-02-01

    6.9.9 (2024-02-01)

    Bug Fixes

    • security: Fix issues described in GHSA-9h6g-pr28-7cqp. Do not use eternal matching pattern if only a few occurences are expected (dd8f5e8)
    • tests: Use native node test runner, added code coverage support, removed grunt (#1604) (be45c1b)
  • 6.9.8 - 2023-12-30
  • 6.9.7 - 2023-10-22
  • 6.9.6 - 2023-10-09
  • 6.9.5 - 2023-09-06
  • 6.9.4 - 2023-07-19
  • 6.9.3 - 2023-05-29
from nodemailer GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade nodemailer from 6.9.3 to 6.10.1.

See this package in npm:
nodemailer

See this project in Snyk:
https://app.snyk.io/org/sammytezzy/project/1d5126e3-8677-4428-99d9-461852e366ec?utm_source=github&utm_medium=referral&page=upgrade-pr
@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@changeset-bot

changeset-bot Bot commented Feb 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 060994d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants