FortiMail (8.0.0-8.0.1) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/fortimail-8.0.0-8.0.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 02 Oct 2026 06:25:40 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgCritical FortiMail Zero-Day Exploited for Arbitrary File Writehttps://feed.craftedsignal.io/briefs/2026-10-fortimail-zero-day/Fri, 02 Oct 2026 06:25:40 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-fortimail-zero-day/Unauthenticated attackers are actively exploiting a path traversal and NULL byte injection vulnerability (CVE-2026-104286) in FortiMail to write arbitrary files and establish persistence.Fortinet has confirmed active, in-the-wild exploitation of a critical vulnerability (CVE-2026-104286, CVSS 9.8) impacting multiple versions of FortiMail. The flaw arises from an improper limitation of a pathname to a restricted directory combined with improper neutralization of NULL bytes, enabling unauthenticated remote attackers to perform arbitrary file writes via crafted HTTP or HTTPS requests. Threat actors are leveraging this capability to modify existing system files and inject new binaries to establish persistent unauthorized access. CISA has added this vulnerability to its Known Exploited Vulnerabilities (KEV) catalog, mandating that FCEB agencies apply patches or workarounds by October 4, 2026. Defenders must prioritize patching vulnerable versions or implementing the recommended CLI-based workarounds.

Attack Chain

  1. Attacker sends a crafted HTTP/HTTPS request targeting the FortiMail appliance.
  2. The request utilizes path traversal sequences combined with NULL byte injection to bypass file system restrictions.
  3. The FortiMail application incorrectly processes the request, allowing the attacker to write files outside of intended directories.
  4. Attacker overwrites or modifies critical system binaries, such as /bin/smit or /data/bin/webconsole.
  5. Attacker deploys malicious shared objects, such as /data/lib/liblog.so or /data/etc/ld.so.preload, to achieve arbitrary code execution.
  6. Attacker modifies configuration files, including /data/etc/httpd.conf, to maintain persistent access or redirect management traffic.
  7. Final objective achieved: establishment of a backdoor or persistence mechanism on the compromised appliance.

Impact

Successful exploitation allows unauthenticated remote attackers to gain unauthorized access to the underlying operating system of the FortiMail appliance. This can lead to full system compromise, exfiltration of sensitive email data, and the use of the appliance as a pivot point into the internal network. Active exploitation has been reported, necessitating immediate attention across all enterprise environments utilizing the affected FortiMail versions.

Recommendation

  • Upgrade FortiMail appliances to the vendor-specified fixed versions immediately (8.0.2, 7.6.7, 7.4.9, or branch 7.4+).
  • Implement the temporary CLI workaround: disable the IBE feature using 'config system encryption ibe' -> 'set status disable' -> 'end'.
  • Restrict access to the FortiMail management interface to trusted private networks only, blocking internet-facing management access.
  • Hunt for indicators of compromise, specifically looking for unauthorized modifications to /data/bin/webconsole, /data/etc/ld.so.preload, and /bin/smit.
]]>criticalthreatvulnerabilityremote-code-executionpersistencenetwork-security