Skip to content
VulniPulse
Medium5.4Red Hat Linux

Medium [CVE-2026-82661] Header injection via unsanitized list comment fields

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

CVE-2026-82661 Published Aug 31, 2026Updated by vendor Aug 31, 2026
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

Summary

Nodemailer before 8.0.9 fails to sanitize carriage return and line feed characters in list comment fields, allowing attackers to inject arbitrary message headers. An attacker with control over list.*.comment parameters can inject CRLF sequences to create additional headers in generated RFC822 messages, altering mail client behavior and message semantics.

A flaw was found in Nodemailer, an email sending library. By failing to sanitize carriage return and line feed (CRLF) characters, an attacker can alter mail client behavior and message semantics, potentially leading to email spoofing or other integrity issues.

Red Hat severity: Moderate — CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). Weakness: CWE-93.

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
  • < 8.0.9

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.

Sign in to join the discussion.