Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/wneessen/go-mail

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.2GoPublished

    go-mail has insufficient address encoding when passing mail addresses to the SMTP client

    CVE-2025-59937 · GHSA-wpwj-69cm-q9c5

    Affected
    • Go github.com/wneessen/go-mail < 0.7.1
    Fixed in
    0.7.1· Vendor fix available
    Issue
    Impact Due to incorrect handling of the mail.Address values when a sender- or recipient address is passed to the corresponding MAIL FROM or RCPT TO commands of the SMTP client, this could lead to a possible wrong address routing or even to ESMTP parameter smuggling. Vulnerability details Instead of making use of the String() method of mail.Address, which takes care of proper escaping and quotation of mail address, we used the Address value of the mail.Address which is the raw value when passing it to our SMTP client. This meant, if a mail address like this was set: "toni.tester@example.com ORCPT=admin@admin.com"@example.com for a sender or recipient, instead of the correctly quoted/escaped address, the SMTP client would get the raw value passed which would translate into something like this being passed to the SMTP server: RCPT TO:<toni.tester@example.com ORCPT=admin@admin.com@example.com. Since ORCTP is a valid command for the SMTP server, the mail would be routed to the wrong…

    Recommended action: Upgrade to 0.7.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →