Vulnerability · GHSA-m943-m63m-w62w
Nodemailer: A ";" inside a quoted string or comment ends an address group early in addressparser, turning display text into a recipient
Published Oct 23, 2026 · catalog updated Oct 23, 2026 · Nodemailer: A ";" inside
Last checked Oct 24, 2026, 15 days ago.
Open the advisory
Exploitation likelihood is not on this record for GHSA-m943-m63m-w62w. A missing EPSS score is not a low risk. Compare Nodemailer: A ";" inside with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Nodemailer: A ";" inside).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Medium6.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Version ranges on file
- Affected products
- npm nodemailer
### Vulnerability summary addressparser ends an RFC 5322 group at the first , including one inside a quoted display name or a comment. The text after it is parsed again as top level recipients with the quoting flipped, so text that every conformant parser reads as a display name or comment becomes a live address. names only , and Nodemailer read it as the single recipient . Affected: 3.0.0 through 10.1.3. ### Attacker capabilities The attacker controls the text of an address field that an application passes to Nodemailer, or the header of an inbound message parsed with mailparser. No access to the application, its configuration or its credentials is needed. The value is a syntactically valid RFC 5322 group that conformant parsers accept without defects. ### Realistic exploitation scenario An application validates the recipients of a submitted address list with a conformant parser and only allows addresses at its own domain. The attacker submits . The validator sees one mailbox, , and approves it. Nodemailer delivers to only. The same works through a quoted display name, . The boundary crossed is the application's recipient allow list. ### Proof of concept Python's reads the same value as the single mailbox , with no defects reported. The envelope a message gets is built from the same parse, so issues the RCPT TO shown above. ### Security impact Mail that an application intends for an approved recipient goes to a recipient chosen by the attacker, which discloses its content, and the intended recipient never receives it. The misreading only occurs on values a conformant validator approves, so correct validation is bypassed, which makes it a security issue rather than a parsing bug. Affected are applications that pass user influenced address lists to Nodemailer and consumers of the standalone parser such as mailparser. The fix tracks quoted strings and comments inside a group and reads only a outside them. Found in an internal review of addressparser on 2026-10-18. Ver
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- npm nodemailer>= 3.0.0, < 10.1.4
How to fix GHSA-m943-m63m-w62w
Upgrade
GHSA-m943-m63m-w62w lists a fix boundary at 10.1.4. Compare the installed build with that boundary before you change production.
Version check
Affected < 10.1.4
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for GHSA-m943-m63m-w62w. A missing EPSS score is not a low risk. Compare Nodemailer: A ";" inside with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with >= 3.0.0, < 10.1.4. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-20: Improper Input Validation; CWE-436. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 23, 2026 · GitHub Advisory Database
Detected
### Vulnerability summary addressparser ends an RFC 5322 group at the first , including one inside a quoted display name or a comment. The text after it is parsed again as top level recipients with the quoting flipped, so text that every conformant parser reads as a display name or comment becomes a live address. names only , and Nodemailer read it as the single recipient . Affected: 3.0.0 through
Oct 23, 2026 · GitHub Advisory Database
Updated
### Vulnerability summary addressparser ends an RFC 5322 group at the first , including one inside a quoted display name or a comment. The text after it is parsed again as top level recipients with the quoting flipped, so text that every conformant parser reads as a display name or comment becomes a live address. names only , and Nodemailer read it as the single recipient . Affected: 3.0.0 through
Sources
- GitHub Advisory DatabasePackage advisoryGHSA-m943-m63m-w62w
Nodemailer: A ";" inside a quoted string or comment ends an address group early in addressparser, turning display text into a recipient
github.com
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitHub Advisory DatabaseOct 24, 2026