{"answers":{"affected":"2 open source packages ship an affected version, including nodemailer.","exploited":"There is no known exploitation of CVE-2026-92597 in the wild and no public exploit code.","fix":"Upgrade nodemailer to 9.1.0 or later.","what":"CVE-2026-92597 is a high-severity vulnerability in nodemailer, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92597 and fix it if it is affected.\n\nWhat it is: CVE-2026-92597 is a high-severity vulnerability in nodemailer, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92597 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nodemailer (npm): affected from 6.9.16; fixed in 9.1.0\n- nodemailer (npm): affected from 6.9.16; fixed in 9.1.0\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-92597/ (Markdown: https://insights.sbomify.com/CVE-2026-92597/index.md)","id":"CVE-2026-92597","markdown":"https://insights.sbomify.com/CVE-2026-92597/index.md","name":"CVE-2026-92597","record":{"aliases":["CLEANSTART-2026-MX71943","CLEANSTART-2026-NF96877","CLEANSTART-2026-ZC19840","DEBIAN-CVE-2026-92597","ECHO-caa4-97bc-c181","GHSA-8pjj-q6q6-qm29","GHSA-cc9r-2j5m-2m83","MINI-78w2-wfwh-995v","MINI-846x-x8jw-2fm4","MINI-9xw3-3p7p-g9gq","MINI-c43v-hcmx-6wqh","MINI-fr7m-6p43-99ph","MINI-gqjv-hwcm-mf7w","MINI-h46v-f28c-c847","MINI-hxfv-r86c-ccw6","MINI-r75g-xrmv-9qm9","MINI-rxw9-mf7m-9hcr","MINI-wcqc-qx8h-8vwh","UBUNTU-CVE-2026-92597"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js email library","requires_auth":"none","summary":"Attackers can bypass email domain validation to deliver mail to attacker-controlled domains by exploiting RFC 5322 comment parsing flaws in Nodemailer.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"Nodemailer versions \u003e= 6.9.16 and \u003c 9.1.0 mis-parse RFC 5322 comments in email addresses: in lib/addressparser, a comment closed immediately before a non-break character causes the tokenizer to concatenate the atoms surrounding the comment instead of treating the comment as folding whitespace that terminates the domain. A recipient address such as user@good-corp.com(x)evil.com is therefore read by Nodemailer as the single domain good-corp.comevil.com (registrable domain comevil.com, which an attacker can register) and used for both the SMTP envelope (RCPT TO) and the emitted To:/From: headers, while a conformant RFC 5322 parser terminates the domain at the comment and reads good-corp.com. An application that validates the recipient domain with a strict RFC 5322 parser (without inspecting parse defects) or a naive prefix/substring allow-list and then hands the raw address to Nodemailer can be induced to deliver mail to a domain the attacker controls. Fixed in 9.1.0.","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 before 9.1.0 Email Domain Validation Bypass via RFC 5322 Comment","id":"CVE-2026-92597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Nodemailer before 9.1.0 IDN/Punycode Domain Allow-list Bypass","id":"CVE-2026-92598"},"packages":[{"ecosystem":"npm","fixed":["9.1.0"],"introduced":["6.9.16"],"last_affected":[],"package":"nodemailer","purl":null,"source":"GHSA-cc9r-2j5m-2m83"},{"ecosystem":"npm","fixed":["9.1.0"],"introduced":["6.9.16"],"last_affected":[],"package":"nodemailer","purl":"pkg:npm/nodemailer","source":"GHSA-cc9r-2j5m-2m83"}],"prev":{"headline":"Nodemailer before 9.1.0 Denial of Service via addressparser","id":"CVE-2026-92596"},"products":["nodemailer"],"published":"2026-09-16","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-17","vendors":["nodemailer"]},"summary":"Attackers can bypass email domain validation to deliver mail to attacker-controlled domains by exploiting RFC 5322 comment parsing flaws in Nodemailer.","url":"https://insights.sbomify.com/CVE-2026-92597/"}