critical

CVE-2025-59937

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

Published 29 Sep 2025Modified 9 Oct 2026CWE 88

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

GHSA8.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by GHSA (high).

Description

go-mail is a comprehensive library for sending mails with Go. In versions 0.7.0 and below, 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, there is a possibility of wrong address routing or even ESMTP parameter smuggling. For successful exploitation, it is required that the user's code allows for arbitrary mail address input (i. e. through a web form or similar). If only static mail addresses are used (i. e. in a config file) and the mail addresses in use do not consist of quoted local parts, this should not affect users. This issue is fixed in version 0.7.1

Affected packages and fixed versions

Source	Package	Fixed in
chainguard	gitea, gitea-fips, sftpgo	1.24.6-r1 and 1 more
go::GitHub Security Advisory Go	github.com/wneessen/go-mail	0.7.1
wolfi	gitea, sftpgo	1.24.6-r1 and 1 more

Show all 6 entries from 3 sources

Source	Package	Fixed in
chainguard	gitea	1.24.6-r1
chainguard	gitea-fips	1.24.6-r1
chainguard	sftpgo	2.6.6-r9
go::GitHub Security Advisory Go	github.com/wneessen/go-mail	0.7.1
wolfi	gitea	1.24.6-r1
wolfi	sftpgo	2.6.6-r9

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs