Threat reportZero-DayTL-2026-2830
Fortinet FortiMail critical path traversal flaw CVE-2026-104286 (FG-IR-26-175) exploited in zero-day attacks
Fortinet disclosed CVE-2026-104286 (CVSS 9.8), a path traversal / NULL byte neutralization flaw in the FortiMail management interface that lets unauthenticated attackers write arbitrary files via crafted HTTP/HTTPS requests. Fortinet confirmed zero-day exploitation and CISA added the CVE to the KEV catalog with a federal remediation deadline of 2026-10-04.
Key facts
| Identifiers | TL-2026-2830, CVE-2026-104286 |
|---|---|
| Also known as | FG-IR-26-175 |
| Severity | CRITICAL |
| CVSS | 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| First disclosed | |
| Exploitation status | Linked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-104286 (added ) |
| Affected products | Fortinet FortiMail |
| Weaknesses (CWE) | CWE-22, CWE-158 |
| MITRE ATT&CK techniques | T1020 Automated Exfiltration, T1036.005 Match Legitimate Resource Name or Location, T1048 Exfiltration Over Alternative Protocol, T1053.003 Cron, T1059.004 Unix Shell, T1105 Ingress Tool Transfer, T1114 Email Collection, T1114.003 Email Forwarding Rule, T1136.001 Create Account: Local Account, T1190 Exploit Public-Facing Application, T1505 Server Software Component, T1554 Compromise Host Software Binary and 1 more in the attack flow |
| Motivation | UNKNOWN |
| Target sectors | government administration, enterprise, email-infrastructure |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 6 cited sources |
Detection coverage
As of 2026-10-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2830 across Splunk SPL, Microsoft KQL and Sigma, covering 30 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: FortiMail Compromise Artifact File Write — liblog.so, ld.so.preload, webconsole, mailservice, httpd.conf, smit, migadmin.tar.gz — Post-Exploitation
Detects creation or modification of the files Fortinet lists as added or changed on compromised FortiMail appliances (FG-IR-26-175): /data/lib/liblog.so, /data/etc/ld.so.preload, /bin/smit, /data/bin/webconsole, /data/bin/mailservice, /data/etc/httpd.conf and /data/migadmin.tar.gz. The combination of a new shared library, an ld.so.preload entry, a modified system binary and altered web server config indicates implanted persistent preloaded code after the arbitrary file write. Requires any telemetry that records file paths (EDR on Linux, auditd, FIM, or forensic triage collections).
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1574.006, T1554, T1505, T1036.005
- Data sources: Endpoint.Filesystem datamodel, auditd, DeviceFileEvents, linux file_event
- Severity: critical
- Confidence: high
Splunk SPL
| tstats summariesonly=false count min(_time) as firstTime max(_time) as lastTime values(Filesystem.action) as actions values(Filesystem.process_name) as processes from datamodel=Endpoint.Filesystem where (Filesystem.file_path="*/data/lib/liblog.so" OR Filesystem.file_path="*/data/etc/ld.so.preload" OR Filesystem.file_path="*/data/bin/webconsole" OR Filesystem.file_path="*/data/bin/mailservice" OR Filesystem.file_path="*/data/etc/httpd.conf" OR Filesystem.file_path="*/data/migadmin.tar.gz" OR Filesystem.file_path="/bin/smit") by Filesystem.dest Filesystem.file_path Filesystem.user
| rename Filesystem.* as *
```Map each artifact to the ATT&CK technique it evidences```
| eval technique=case(match(file_path, "ld[.]so[.]preload|liblog[.]so"), "T1574.006", match(file_path, "httpd[.]conf"), "T1505", match(file_path, "/bin/smit$"), "T1554", true(), "T1036.005")
| convert ctime(firstTime) ctime(lastTime)
| table firstTime lastTime dest user file_path actions processes technique countMicrosoft KQL
let IOCPaths = dynamic(['/data/lib/liblog.so', '/data/etc/ld.so.preload', '/bin/smit', '/data/bin/webconsole', '/data/bin/mailservice', '/data/etc/httpd.conf', '/data/migadmin.tar.gz']);
DeviceFileEvents
| where Timestamp > ago(24h)
| where ActionType in ('FileCreated', 'FileModified', 'FileRenamed')
| where FolderPath in~ (IOCPaths)
| project Timestamp, DeviceName, ActionType, FolderPath, SHA256, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessAccountNameSigma
title: FortiMail FG-IR-26-175 Compromise Artifact File Created or Modified
id: b7d2e9f4-6c8a-4f2b-8d47-3e9a51c8b222
status: experimental
description: Detects creation or modification of files Fortinet lists as added or changed on FortiMail appliances compromised via CVE-2026-104286, including the preloaded shared library liblog.so, the ld.so.preload entry, the modified /bin/smit binary, the added webconsole and mailservice binaries, httpd.conf and migadmin.tar.gz.
references:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-175
- https://www.bleepingcomputer.com/news/security/fortinet-warns-of-critical-fortimail-flaw-exploited-in-zero-day-attacks/
author: Threadlinqs Team
date: 2026-10-01
tags:
- attack.persistence
- attack.t1574.006
- attack.t1554
- attack.t1505
- attack.defense-evasion
- attack.t1036.005
- cve.2026.104286
logsource:
product: linux
category: file_event
detection:
selection_paths:
TargetFilename|endswith:
- '/data/lib/liblog.so'
- '/data/etc/ld.so.preload'
- '/data/bin/webconsole'
- '/data/bin/mailservice'
- '/data/etc/httpd.conf'
- '/data/migadmin.tar.gz'
selection_smit:
TargetFilename: '/bin/smit'
condition: selection_paths or selection_smit
fields:
- TargetFilename
- Image
- User
falsepositives:
- Legitimate FortiMail firmware upgrade or configuration restore touching httpd.conf or the /data partition
- AIX hosts where smit is a legitimate system management tool
level: criticalKnown false positives:
- Legitimate FortiMail firmware upgrades or configuration restores that rewrite httpd.conf or files under /data
- AIX systems where /bin/smit is a legitimate binary
Tuning notes: FortiMail appliances rarely forward file telemetry natively; feed this from FIM, auditd on exported images, EDR where supported, or forensic triage collections. Exclude change windows for approved firmware upgrades by correlating with Fortinet upgrade events. Treat any hit on liblog.so or ld.so.preload as confirmed compromise and verify with the SHA-256 IOCs. Restrict /bin/smit matching to non-AIX assets.
- Inbound Connection From FG-IR-26-175 Attacker IPs ([indicator] / [indicator]) — Exploitation · unlock with TL Creds
- FortiMail Implant Hash and Binary Execution Match — liblog.so / webconsole / mailservice / smit / ld.so.preload — Post-Exploitation · unlock with TL Creds
- Mail Gateway Egress to FG-IR-26-175 Attacker IPs or Bulk Non-Mail Transfer — Exfiltration · unlock with TL Creds
- Successful FortiMail Path Traversal / NUL Byte Write Request (2xx Response) — Likely Arbitrary File Write · unlock with TL Creds
- Dynamic Linker Hijack via ld.so.preload and liblog.so Implant — Persistence · unlock with TL Creds
- Outbound HTTP Upload to [indicator] on FG-IR-26-175 Attacker IP — Archive Exfiltration · unlock with TL Creds
- FortiMail Management Interface Path Traversal / NUL Byte Request (CVE-2026-104286) — Exploitation · unlock with TL Creds
- FortiMail Archive Account Configured Toward Attacker IP or [indicator] Path — Email Exfiltration · unlock with TL Creds
Indicators of compromise
As of 2026-10-10, Threadlinqs Intelligence tracks 30 indicators of compromise for TL-2026-2830.
Sample indicators (3 of 30)
- IP address:
79.141.169[.]187 - File hash:
8015f34dc84922b03688399d7f9fe7a00361789f7e420c7e2a2cdb23e75cef84 - IP address:
45.129.0[.]192
Defanged, TLP:CLEAR. Full set of 30 indicators: unlock with TL Creds.
Technical analysis
CVE-2026-104286 (Fortinet PSIRT FG-IR-26-175) is a combination of CWE-22 (path traversal) and CWE-158 (improper neutralization of NULL byte or NUL character) in the FortiMail management interface. An unauthenticated remote attacker can write arbitrary files on the underlying system through crafted HTTP or HTTPS requests. The CVSS v3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); Fortinet's temporal vector is E:P/RL:O/RC:C. NVD (published 2026-10-01 20:17 UTC) marks exploitation as active, the flaw as automatable, and technical impact as total.
Fortinet states the flaw is exploited in the wild as a zero-day. The advisory credits Gwendal Guegniaud of the Fortinet Product Security team, so the issue was found internally. The advisory lists two source IPs associated with the attacks (79.141.169.187 and 45.129.0.192) and a set of files added or modified on compromised appliances: /data/lib/liblog.so, /data/etc/ld.so.preload, /bin/smit, /data/bin/webconsole, /data/bin/mailservice, /data/etc/httpd.conf and /data/migadmin.tar.gz (SHA-256 hashes recorded in the IOC list). The combination of an added shared library, an added ld.so.preload entry, a modified system binary and a modified web server configuration indicates that the arbitrary file write was used to implant persistent, preloaded code on the appliance.
BleepingComputer additionally reports that compromised systems showed archive account configurations pointing to 79.141.169.187 for remote data exfiltration via the /uploads directory, i.e. the appliance's mail archiving function was reconfigured to ship data to attacker infrastructure. The advisory does not attribute the activity to a named actor, name a malware family, or describe the payload's function; none is asserted here. CISA lists known ransomware campaign use as Unknown. BeaconBeagle returned 404 (no record) for 79.141.169.187.
Affected versions per Fortinet: FortiMail 8.0.0-8.0.1, 7.6.0-7.6.6, 7.4.0-7.4.8 and 7.2.0-7.2.9. The NVD CPE data additionally spans 7.0.0-7.0.9. Fixed releases are 8.0.2, 7.6.7 and 7.4.9; BleepingComputer describes them as pending/upcoming, while the PSIRT table lists them as the fixed versions. FortiMail 7.2 users must migrate to 7.4 or later. Workarounds are to disable the IBE (identity-based encryption) feature (config system encryption ibe / set status disable) and to restrict management interface access to trusted private networks, with no Internet-facing management exposure. CISA added the CVE to the KEV catalog on 2026-10-01 with a due date of 2026-10-04 and directs agencies to apply vendor mitigations per BOD 26-04 or discontinue use of the product if mitigations are unavailable; BleepingComputer notes agencies must perform forensic triage and mitigation. Fortinet says it is communicating with relevant government organizations, including CISA.
MITRE ATT&CK techniques by tactic:
Exfiltration
T1020 Automated Exfiltration; T1048 Exfiltration Over Alternative Protocol
Defense Evasion
T1036.005 Match Legitimate Resource Name or Location; T1574.006 Dynamic Linker Hijacking
Persistence
T1053.003 Cron; T1136.001 Create Account: Local Account; T1505 Server Software Component; T1554 Compromise Host Software Binary
Execution
Command and Control
Collection
T1114 Email Collection; T1114.003 Email Forwarding Rule
Initial Access
T1190 Exploit Public-Facing Application
stealth
Remediation
Patches
- Upgrade FortiMail 7.4 to 7.4.9 or later
- Upgrade FortiMail 7.6 to 7.6.7 or later
- Upgrade FortiMail 8.0 to 8.0.2 or later
- Migrate FortiMail 7.2 to 7.4 or later
Immediate actions
- Disable the IBE feature: config system encryption ibe / set status disable
- Restrict FortiMail management interface access to trusted private networks and remove Internet-facing management exposure
- Block 79.141.169.187 and 45.129.0.192 and hunt for the Fortinet-listed IOC files and hashes on appliances
- Review FortiMail archive account configurations for entries pointing to 79.141.169.187 or other unrecognized destinations
- Perform forensic triage of appliances per CISA/BOD 26-04 guidance before and after mitigation
Workarounds
- Disable IBE support
- Allow management interface access from trusted networks only
Longer-term hardening
- Keep FortiMail management planes off the public Internet
- Monitor appliance file integrity for unexpected shared libraries and ld.so.preload entries
Affected and fixed versions
- Fortinet — FortiMail
Vulnerable versions: 8.0.0-8.0.1; 7.6.0-7.6.6; 7.4.0-7.4.8; 7.2.0-7.2.9; 7.0.0-7.0.9 (NVD record only)
Fixed in: 8.0.2; 7.6.7; 7.4.9; 7.2 users: upgrade to 7.4 or later
Timeline
Last updated · 6 updates · revalidated 6× · latest source
- watchTowr describes exploitation of the FortiMail IBE flaw as trivial and notes that an arbitrary file write leads to command execution on the device; Zero Hunt Research reports permanent backdoor installations on compromised appliances.
- Fortinet states it is communicating with relevant government organizations, including CISA, about the exploitation.
- BleepingComputer reports the zero-day exploitation, listing attacker IPs locked-ioc-21 and locked-ioc-22, the modified/added files, and archive account configurations pointing to locked-ioc-21 for exfiltration via locked-ioc-24.
- CISA adds CVE-2026-104286 to the Known Exploited Vulnerabilities catalog; known ransomware campaign use is listed as Unknown; required action references BOD 26-04.
- Fixed FortiMail releases 7.4.9, 7.6.7 and 8.0.2 are named in the advisory (BleepingComputer describes them as pending); FortiMail 7.2 users are told to migrate to 7.4 or later.
- NVD publishes the CVE-2026-104286 record at 20:17 UTC (CVSS 3.1 base 9.8, CWE-22; CPE ranges 7.0.0 through 8.0.1) and updates it about an hour later.
- Fortinet publishes PSIRT advisory FG-IR-26-175 for CVE-2026-104286, confirming active exploitation in the wild; the flaw was found internally by Fortinet Product Security (credit: Gwendal Guegniaud).
- CERT-FR (ANSSI) publishes CERTFR-2026-AVI-1257 for the FortiMail flaw, citing Fortinet's confirmation of active exploitation and rating the impact as remote arbitrary code execution (no CVSS score given).
- Help Net Security and Beazley Security publish follow-up analysis: NULL byte processing truncates input parsing so traversal sequences bypass path validation, exploitation requires IBE enabled with the web interface reachable, and root cron entries referencing /migadmin, the archive234 account and IBE log errors are listed as compromise indicators.
- Follow-up analyses report that no fixed FortiMail build (7.4.9, 7.6.7, 8.0.2) has shipped; disabling IBE and restricting web/management access remain the only mitigations, and neither evicts an already-compromised appliance.
- CISA federal agency remediation deadline: apply vendor mitigations per BOD 26-04 and perform forensic triage, or discontinue use of the product.
- GovCERT.HK publishes High Threat Security Alert A26-10-05 for the FortiMail vulnerability.
- Per GovCERT.HK alert A26-10-05, Fortinet fixed releases 7.4.9, 7.6.7 and 8.0.2 are available for CVE-2026-104286 (FortiMail Cloud patched the same day); earlier follow-up analyses had reported no shipped fix.
- Fortinet states FortiMail Cloud has been remediated.
- Fortinet advisory FG-IR-26-175 is updated on 2026-10-05 with IOCs, and SOC Prime publishes analysis; one estimate puts 1,000-10,000 FortiMail systems exposed internet-wide, and no actor or victim count has been disclosed.
- Fortinet updates FG-IR-26-175 with a clarification on the FortiMail Cloud fix.
Update history
- 2026-10-10 — Fortinet FortiMail Unauthenticated Path Traversal / Arbitrary File Write Leading to RCE (CVE-2026-104286) Exploited as Zero-Day: What changed No severity, exploitability, status or CVSS change (already CRITICAL / ACTIVE / 9.8).
- 2026-10-07 — Fortinet FortiMail unauthenticated path traversal / NULL-byte arbitrary file write leading to RCE actively exploited as zero-day (CVE-2026-104286): What changed No severity, exploitability, status or CVSS change (already CRITICAL / ACTIVE / 9.8).
- 2026-10-05 — CVE-2026-104286: Critical FortiMail Zero-Day Exploited for Unauthenticated File Writes: What changed No field escalation: severity CRITICAL, exploitability ACTIVE and status ACTIVE already match the newer report. New MITRE (1) T1136.001 (Create Account) added for the attacker-created archive234 archive account.
- 2026-10-04 — Fortinet FortiMail zero-day CVE-2026-104286 actively exploited (IBE path traversal / NULL-byte handling, unauthenticated arbitrary file write to persistent root code execution): What changed No severity, exploitability or status change; both reports agree on CRITICAL / ACTIVE / CVSS 9.8. New indicators (6) Indicator values are withheld at this access level.
- 2026-10-04 — Critical FortiMail Zero-Day (CVE-2026-104286) Exploited in Attacks Allows Unauthenticated Arbitrary File Writes: What changed No severity, exploitability, status or CVSS change; both reports already agree on CRITICAL / ACTIVE / 9.8. New indicators (1) Indicator values are withheld at this access level. Attribution Unchanged.
- 2026-10-04 — Critical FortiMail zero-day exploited in the wild (CVE-2026-104286): What changed No severity/exploitability/status change (already CRITICAL/ACTIVE).
Sources cited
- NVD CVE-2026-104286 record NVD (NIST) · Advisory · 2026-10-01
- NVD CVE API record for CVE-2026-104286 NVD (NIST) · Advisory · 2026-10-01
- CISA KEV catalog entry for CVE-2026-104286 CISA · Government advisory · 2026-10-01
- CISA Known Exploited Vulnerabilities JSON feed CISA · Government advisory · 2026-10-01
- Fortinet PSIRT FG-IR-26-175 Fortinet · Vendor report · 2026-10-01
- Fortinet warns of critical FortiMail flaw exploited in zero-day attacks BleepingComputer · News · 2026-10-01
Other reports on CVE-2026-104286
Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated .