Skip to content

Warning: Actively Exploited FortiMail Vulnerability, Patch Immediately!

Ccb.Belgium.Be • October 2, 2026

CVE/CVSS: CVE-2026-104286: 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C)

Fortinet -

A critical, actively exploited vulnerability in Fortinet FortiMail lets attackers take over the device without a password. Organisations running FortiMail should patch immediately.

FortiMail is an email security gateway: it sits between the internet and your mail servers and filters all incoming and outgoing email. That position makes it attractive to attackers. Whoever controls it can read and alter company email and use it as a foothold into the internal network.

The flaw scores 9.8 out of 10 and is effectively a zero-day : attackers were using it before any patch existed. It needs no login and no user interaction, and can be triggered remotely over the network, so it is easy to exploit. Several organisations have confirmed active exploitation and CISA added it to its Known Exploited Vulnerabilities list.

Fixed versions are not yet released. Apply Fortinet's temporary workaround today, update as soon as the patch is out, and check whether your devices were already compromised.

The flaw is a path traversal (CWE-22) combined with improper handling of NULL bytes (CWE-158) in FortiMail. An unauthenticated attacker can send crafted requests to write arbitrary files anywhere on the underlying system. The vulnerable code sits in the Identity-Based Encryption (IBE) feature. Devices with IBE enabled and the FortiMail management interface reachable from the internet are most exposed.

This vulnerability is being actively exploited. Apply the workaround now and patch as soon as Fortinet releases a fix.

Apply the workaround now.

Disable the IBE feature support using the following CLI command:

If IBE cannot be deactivated:

Block direct internet access to /ibe unless public external IBE access is genuinely required.

Fortinet documentation notes that external IBE users use the secure-message link flow, while internal users can use webmail login. Many environments can therefore restrict /ibe to trusted networks or a VPN without fully breaking internal mail access.

See Fortinet's documentation:

Patch as soon as fixes ship. Upgrade to 8.0.2, 7.6.7 or 7.4.9. Plan a migration to 7.4 or later for devices on 7.2 or 7.0, which will not receive a fix.

The CCB recommends organizations upscale monitoring and detection capabilities to identify any related suspicious activity and ensure a swift response in case of an intrusion.

In case of an intrusion, you can report an incident via .

While patching appliances or software to the newest version may protect against future exploitation, it does not remediate historic compromise.

Follow the Fortinet advisory for patch release and updated IoCs

In case of compromise

Delete any illicit archiving policies and review configuration changes.

Rotate all FortiMail local administrator passwords, API tokens, and SSH keys.

Rotate the LDAP/AD service account password.

Review FortiMail trust relationships with other applications and rotate any secrets belonging to trusted applications, including cloud integrations.

Rotate FortiSandbox credentials/API keys and re-establish trust.

Review and rotate FortiManager/FortiAnalyzer trust, if applicable.

Review unauthorized or suspicious access to connected services such as Azure.

Rotate SNMP community strings.

Rotate mail relay, archive, backup, SFTP/FTP/SCP/SMB, and remote logging credentials.

Revoke and replace all certificates and private keys stored on FortiMail.

Rotate DKIM keys and update DNS records.

Rebuild the appliances to eliminate risks from a potential compromise, and patch to the latest version.

Keep monitoring the appliances for changes after applying the patch.

Onboard CLI logs to a SIEM and alert on configuration changes.

Implement a WAF in front of the webserver component.

Configure a reverse proxy with whitelisting for sensitive pages (/admin, etc.), in addition to any whitelisting configured on FortiMail.

Indicators of Compromise

[ADDED]/data/lib/liblog.so MD5 - 64c90a00c7fda4d5c7973ed64c25783a SHA256 - 8015f34dc84922b03688399d7f9fe7a00361789f7e420c7e2a2cdb23e75cef84

[MODIFIED]/bin/smit MD5 - 5241738a3e9988404239e12243f6d35b SHA256 - 77324ac428bde86d351fc5fc06f6d64a6bfe737dfb2743df1d4c5ac2418a5b6a

[ADDED]/data/bin/webconsole MD5 - ae0ea6502d3fa5f0664bceb73189eb54 SHA256 - 7a6cea9f5c9e2e9994d4e3c4da73f86cf5acd05ea5d312c066c9d1dafd69ee38

[ADDED]/data/bin/mailservice MD5 - f90fa81a5f521d785f2b2f765e3ab897 SHA256 - 4000276a150a165d3c2537d1e19fb393c4de8333076a16655e28059cae82157b

[MODIFIED]/data/etc/httpd.conf MD5 - 61af1c4bce1c2eebc8ff689ca5337791 SHA256 - 703e97c64e61e41dc3aaba580d82bb2aa7b6a11b54ee6fb467ed5d5a3bffdef5

[ADDED]/data/etc/ld.so.preload MD5 - 8eb64f25d2a8e18e05aae058629473cf SHA256 - 8953ec7960b09f544a880b072ad4e6cfda7a8303f486251d3478dcfdfbac23b6

[MODIFIED] /data/migadmin.tar.gz MD5 - 49a7156a7d043cc8f9f680579db22f86 SHA256 - d6fe51c22b91776f4c961ea58bcac5917f15d560a619d7ce726d3d51795609d3

type=event subtype=system pri=debug user=system ui=cron msg="(root) CMD (/bin/sh -c 'O=/migadmin ...

type=kevent subtype=admin pri=information user=admin ui=(null) action=logout status=success reason=unknown msg="User admin logged out from (null)."

type=kevent subtype=config pri=information user=admin ui=cli module=unknown submodule=unknown msg="Added 'archive234' to 'archive account' : rotation-size[50]rotation-time[1] rotation-hour[14]destination[remote]remote-ip[79.141.169.187]remote-username[archive234]remote-password[***]remote-directory[/uploads] (user: admin, from: cli)"

FortiMail::IBE::DecrypterMediaIn::DecrypterMediaIn(FortiMail::MediaIn&, const FortiMail::IBE::KeyFinder&, const FortiMail::EmailAddress&, const FortiMail::Buffer&, FortiMail::IBE::DecrypterMediaIn::Version): Caught BufferException(2), BufferImpl.cpp:973, 'Invalid Base64 Encoding at pos 0. Character=0x2a'

Internal user *@domain.tld failed to log in.

UUID: ed9ad3e1-d3bf-44bc-8c79-9b1fc54984ff