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
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/wneessen/go-mail/commit/42e92cfe027be04aff72921adb0f72f11d517479 Patch
- https://github.com/wneessen/go-mail/pull/496 Issue Tracking, Patch
- https://github.com/wneessen/go-mail/security/advisories/GHSA-wpwj-69cm-q9c5 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.2 · pebcakNVD modified 2026-10-09 09:10
Affected (CPE criteria) 1
cpe:2.3:a:pebcak:go-mail:*:*:*:*:*:go:*:*
References 5
- https://github.com/wneessen/go-mail/commit/42e92cfe027be04aff72921adb0f72f11d517479 Patch
- https://github.com/wneessen/go-mail/issues/495 Exploit, Issue Tracking
- https://github.com/wneessen/go-mail/pull/496 Issue Tracking, Patch
- https://github.com/wneessen/go-mail/security/advisories/GHSA-wpwj-69cm-q9c5 Vendor Advisory
- https://github.com/wneessen/go-mail/issues/495 Exploit, Issue Tracking