{"answers":{"affected":"2 open source packages ship an affected version, including nodemailer.","exploited":"There is no known exploitation of CVE-2026-100701 in the wild and no public exploit code.","fix":"Upgrade nodemailer to 10.0.2 or later.","what":"CVE-2026-100701 is a medium-severity vulnerability in nodemailer, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100701 and fix it if it is affected.\n\nWhat it is: CVE-2026-100701 is a medium-severity vulnerability in nodemailer, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-100701 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nodemailer (npm): affected from 5.0.0; fixed in 10.0.2\n- nodemailer (npm): affected from 5.0.0; fixed in 10.0.2\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-2026-100701/ (Markdown: https://insights.sbomify.com/CVE-2026-100701/index.md)","id":"CVE-2026-100701","markdown":"https://insights.sbomify.com/CVE-2026-100701/index.md","name":"CVE-2026-100701","record":{"aliases":["CLEANSTART-2026-HG25385","CLEANSTART-2026-HM32228","CLEANSTART-2026-RE54835","CLSA-2026-1790673224","CLSA-2026-1790676821","CLSA-2026-1792139197","CLSA-2026-1792429268","DEBIAN-CVE-2026-100701","ECHO-94cb-1303-48fb","GHSA-2mg4-38wg-2h6f","GHSA-6vj9-mwq6-2f5v","MINI-382w-fxj2-c42r","MINI-3m96-xh7r-w5mw","MINI-3xp6-vqgw-hxxf","MINI-6j7g-xhmp-v9pg","MINI-87cc-fwgm-2f6r","MINI-9g8f-c762-82gg","MINI-c9q6-mghv-5qj2","MINI-cc3c-vw9w-wqxm","MINI-cr44-5jmg-7r3g","MINI-f96p-m8xh-5p7r","MINI-jhm3-78jc-mrp3","MINI-p3rg-pc2r-w9mw","MINI-p56m-38g3-4p29","MINI-r25p-5wqv-qmvj","MINI-wg54-j58f-wxqf","UBUNTU-CVE-2026-100701"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js email library","requires_auth":"low_privilege","summary":"An attacker can exploit a DNS cache flaw in Nodemailer to force incorrect TLS servername validation, potentially disclosing SMTP credentials in multi-tenant environments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports (secure: true) resolve the same non-IP host with different tls.servername values, the first transport's servername is returned on the cache hit and overwrites the second transport's explicitly configured value, so Nodemailer sends the wrong SNI value and validates the peer certificate against the wrong identity. In multi-tenant services or SNI-routed SMTP gateways, an attacker who can prime the cache can cause a victim transport to connect to the attacker's TLS virtual host and accept the attacker's certificate even with rejectUnauthorized: true, disclosing the victim's SMTP credentials. Fixed in 10.0.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion","id":"CVE-2026-100701","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Nodemailer before 10.0.2 Stack Exhaustion via Nested Recipient Arrays","id":"CVE-2026-100702"},"packages":[{"ecosystem":"npm","fixed":["10.0.2"],"introduced":["5.0.0"],"last_affected":[],"package":"nodemailer","purl":null,"source":"GHSA-6vj9-mwq6-2f5v"},{"ecosystem":"npm","fixed":["10.0.2"],"introduced":["5.0.0"],"last_affected":[],"package":"nodemailer","purl":"pkg:npm/nodemailer","source":"GHSA-6vj9-mwq6-2f5v"}],"prev":{"headline":"nodemailer before 10.0.6 Denial of Service via addressparser","id":"CVE-2026-100700"},"products":["nodemailer"],"published":"2026-09-26","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-26","vendors":["nodemailer"]},"summary":"An attacker can exploit a DNS cache flaw in Nodemailer to force incorrect TLS servername validation, potentially disclosing SMTP credentials in multi-tenant environments.","url":"https://insights.sbomify.com/CVE-2026-100701/"}