{"answers":{"affected":"3 open source packages ship an affected version, including github.com/wneessen/go-mail. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59937 exists.","fix":"Upgrade github.com/wneessen/go-mail to 0.7.1 or later.","what":"CVE-2025-59937 is a high-severity vulnerability in wneessen go-mail, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59937 and fix it if it is affected.\n\nWhat it is: CVE-2025-59937 is a high-severity vulnerability in wneessen go-mail, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59937 exists.\n\nAffected packages and fixed versions:\n- github.com/wneessen/go-mail (Go): affected all versions; fixed in 0.7.1\n- github.com/wneessen/go-mail (Go): affected all versions; fixed in 0.7.1\n- github.com/wneessen/go-mail (Go): affected all versions; fixed in 0.7.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59937/ (Markdown: https://insights.sbomify.com/CVE-2025-59937/index.md)","id":"CVE-2025-59937","markdown":"https://insights.sbomify.com/CVE-2025-59937/index.md","name":"CVE-2025-59937","record":{"aliases":["GHSA-wpwj-69cm-q9c5","GO-2025-3988"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Go mail library","requires_auth":"none","summary":"Attackers can manipulate SMTP commands via crafted email addresses, potentially causing wrong routing or parameter smuggling in applications using this Go library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"go-mail","vendor":"pebcak"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"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","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"go-mail has insufficient address encoding when passing mail addresses to the SMTP client","id":"CVE-2025-59937","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"Heap buffer overflow in wazuh-analysisd","id":"CVE-2025-59938"},"packages":[{"ecosystem":"Go","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"github.com/wneessen/go-mail","purl":null,"source":"GHSA-wpwj-69cm-q9c5"},{"ecosystem":"Go","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"github.com/wneessen/go-mail","purl":"pkg:golang/github.com/wneessen/go-mail","source":"GHSA-wpwj-69cm-q9c5"},{"ecosystem":"Go","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"github.com/wneessen/go-mail","purl":"pkg:golang/github.com/wneessen/go-mail","source":"GO-2025-3988"}],"prev":{"headline":"get-jwks poisoned JWKS cache allows post-fetch issuer validation bypass","id":"CVE-2025-59936"},"products":["go-mail"],"published":"2025-09-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-30","vendors":["wneessen"]},"summary":"Attackers can manipulate SMTP commands via crafted email addresses, potentially causing wrong routing or parameter smuggling in applications using this Go library.","url":"https://insights.sbomify.com/CVE-2025-59937/"}