CVE-2026-92595
Description
A flaw was found in Nodemailer. Plugin or application code that resolves untrusted message content through the MailMessage.resolveContent() API using its legacy three-argument signature can bypass intended sandbox restrictions. This vulnerability allows an attacker to read arbitrary local files or perform Server-Side Request Forgery (SSRF) by issuing outbound HTTP(S) requests. This bypass occurs because the disableFileAccess and disableUrlAccess sandbox options are not honored in this specific usage.
Statement
This Moderate flaw in Nodemailer allows information disclosure and server-side request forgery (SSRF) in Red Hat products that utilize the nodemailer package. The vulnerability arises when applications process untrusted message content via the legacy three-argument MailMessage.resolveContent() API, bypassing intended sandbox restrictions. Exploitation requires an application to specifically use this deprecated API signature with untrusted input.
Mitigation
The vulnerability in Nodemailer is dependent on specific application code usage of a legacy API signature and requires the sandbox flags to be explicitly enabled. Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 5.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Integrity
Technical Impact: Execute Unauthorized Code or Commands
Access Control
Technical Impact: Bypass Protection Mechanism
By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
