PatchSiren cyber security CVE debrief
CVE-2026-82659 nodemailer CVE debrief
CVE-2026-82659 was published on 2026-08-31T09:17:03.633Z and has not been modified since then. The NVD entry is currently Received. This vulnerability exists in nodemailer before version 9.0.1, where the disableFileAccess and disableUrlAccess flags are not applied to the message-level raw option, allowing authenticated attackers to read arbitrary files or perform server-side request forgery. Evidence is limited to the supplied CVE description and NVD assessment. Defenders should verify affected product deployments, review official advisories, and monitor for suspicious activity. Users of nodemailer before version 9.0.1 should be aware of this vulnerability and take necessary actions to mitigate it.
- Vendor
- nodemailer
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-31
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-31
- Advisory updated
- 2026-08-31
Who should care
Users of nodemailer before version 9.0.1 should be aware of this vulnerability and take necessary actions to mitigate it. Affected operators, platforms, and security teams should review official advisories, assess their exposure, and apply patches or mitigations as needed. Vulnerability management and security teams should prioritize patching and monitor for suspicious activity related to this vulnerability.
Technical summary
The vulnerability exists in nodemailer before version 9.0.1, where the disableFileAccess and disableUrlAccess flags are not applied to the message-level raw option, allowing authenticated attackers to read arbitrary files or perform server-side request forgery. This issue can be exploited by crafting raw messages with file paths or URLs that bypass the intended sandbox, with fetched content delivered in the outgoing message to attacker-controlled recipients.
Defensive priority
Authenticated attackers can exploit this vulnerability to read arbitrary files or perform server-side request forgery.
Recommended defensive actions
- Apply the patch or upgrade to nodemailer version 9.0.1 or later
- Restrict access to the nodemailer application
- Monitor for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability exists in nodemailer before version 9.0.1, where the disableFileAccess and disableUrlAccess flags are not applied to the message-level raw option. This allows authenticated attackers to read arbitrary files or perform server-side request forgery. Evidence is limited to the supplied CVE description and NVD assessment. Defenders should verify affected product deployments, review official advisories, and monitor for suspicious activity.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-82659 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-82659
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-82659 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-82659
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/nodemailer/nodemailer/security/advisories/GHSA-p6gq-j5cr-w38f
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/nodemailer-before-9.0.1-file-read-and-ssrf-via-raw-option
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.