The most dangerous vulnerability in the room is often not the one with the scariest acronym. It is the one sitting on a security gateway, reachable over ordinary web traffic, waiting for someone to remember that the maintenance window is next Thursday. CVE-2026-104286 is that kind of bug, which is exactly why it should not be treated like another line item in the quarterly patch spreadsheet.
Fortinet FortiMail is an email security gateway, which means it lives near the front door while politely inspecting the mail. According to OpenCVE, CVE-2026-104286 carries a CVSS v3.1 score of 9.8 Critical, is marked KEV: Yes, and has an action of Immediate Patch. That is not a patch note. That is the smoke alarm asking why everyone is still in a meeting.
The KEV entry changes the queue
According to OpenCVE, CVE-2026-104286 was published on 2026-10-01 and is a path traversal vulnerability affecting Fortinet FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and 7.2.0 through 7.2.9. OpenCVE says an unauthenticated attacker can write arbitrary files on the underlying system through crafted HTTP or HTTPS requests. It also lists EPSS at 2.2 percent Low, which is a useful reminder that probability scoring and observed exploitation signals are different animals, and only one of them is currently standing in CISA KEV wearing muddy boots.
@title FortiMail exploit shape
@source CVE-2026-104286 - Vulnerability Details - OpenCVE
HTTP requests ····· unauthenticated
│
▼
path traversal ···· arbitrary file write
│
▼
underlying system · system compromise
@caption The flaw turns ordinary web requests into file writes on FortiMail systems.
The Cybersecurity and Infrastructure Security Agency maintains the Known Exploited Vulnerabilities Catalog, according to CISA, and its very name does a lot of work here. KEV is not a vibes board for scary CVEs. It is the defensive triage shelf for flaws known to matter in the real world, which is why security gateways on that shelf deserve priority over cleaner, calmer, more easily scheduled work.
The exploit is boring in the dangerous way
BleepingComputer reported that Fortinet warned customers the FortiMail vulnerability was being actively exploited and affects the FortiMail management interface. The flaw combines improper limitation of a pathname to a restricted directory with improper handling of a NULL byte or NULL character, and BleepingComputer attributed the discovery to Gwendal Guégniaud of Fortinet's Product Security team. Translation from vulnerability poetry: a request that should stay in its lane can be shaped to write files where it should not.
That is not flashy, which is what makes it practical. Threat actors do not need a dramatic monologue when unauthenticated HTTP or HTTPS traffic can reach a management interface and produce unauthorized code or commands, as BleepingComputer reported. The character motivation is simple: security gateways are useful footholds because they sit at chokepoints, and chokepoints are where patient intruders bring snacks.
The patch picture is messy, because of course it is
BleepingComputer reported on 2026-10-01 that Fortinet urged customers to apply shared workarounds until a security update could be installed. The same report said FortiMail 7.2 users can patch by upgrading to the 7.4 branch or later. For affected FortiMail 7.4, 7.6, and 8.0 installations, BleepingComputer said security updates were not yet available at that time, with Fortinet listing FortiMail 7.4.9, 7.6.7, and 8.0.2 as upcoming versions containing the fix.
This is where KEV becomes more useful than calendar hygiene. Ordinary patch cycles assume time is mostly yours. KEV listed gateway flaws politely disagree, then kick the door. If your FortiMail deployment falls into the affected ranges named by OpenCVE, the practical order is version check first, mitigation second, permanent fix as soon as the relevant fixed build is available.
What it actually means for you
OpenCVE lists the impact as arbitrary file write capable of system compromise, and says malicious files can compromise confidentiality, integrity, and availability. In human terms, this is not just an email filtering problem. It is a gateway integrity problem, and once the device that is supposed to help screen hostile traffic becomes the questionable roommate, defenders should assume normal trust boundaries need a second look.
For security teams, the takeaway is blunt but manageable: identify exposed FortiMail versions, apply available workarounds or upgrades, and treat KEV status as a priority override rather than a footnote. For leaders, this is a budgeting lesson with fewer acronyms than usual: perimeter security products need emergency maintenance paths, because attackers do not wait for the next change advisory board meeting to achieve quorum. Watch Fortinet's fixed build availability and CISA KEV updates next, then use this one as a dry run for how your team handles exploited flaws in gateways before the next thriller score lands.