High7.1Red Hat Linux

High [CVE-2026-82659] Arbitrary file read and Server-Side Request Forgery via raw option bypass

This high-severity Red Hat Linux advisory covers CVE-2026-82659 affecting Red Hat Developer Hub, Self-service automation portal 2.

CVE-2026-82659 Published Aug 31, 2026Updated by vendor Aug 31, 2026

CVE-2026-82659

Affected products & platforms

Red Hat LinuxUnclassified

Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

nodemailer before 9.0.1 fails to apply disableFileAccess and disableUrlAccess flags to message-level raw option, allowing authenticated attackers to read arbitrary files or perform server-side request forgery by supplying path or href properties.

Attackers can exploit this 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. A flaw was found in nodemailer.

This allows them to read arbitrary files from the system or perform Server-Side Request Forgery (SSRF), potentially leading to information disclosure or unauthorized access to internal network resources. Red Hat severity: Important — CVSS 7.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).

Weakness: CWE-918. Affected Red Hat products: Red Hat Developer Hub; Self-service automation portal 2.

Red Hat lists Red Hat Enterprise Linux 10; Red Hat Hardened Images as not affected. Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

< 9.0.1

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.