Automated Threat Modeling

Quick look: FortiMail CVE-2026-126147, unauthenticated API path traversal with potential code execution

A brief summary of CVE-2026-126147, a CVSS 9.8 path traversal flaw in the FortiMail API that Fortinet says may allow unauthenticated code or command execution. Includes the fixed release matrix and an explanation of why the fix predates the advisory.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Quick look: FortiMail CVE-2026-126147, unauthenticated API path traversal with potential code execution

Introduction

Fortinet has disclosed a path traversal flaw in the FortiMail API that, according to the vendor, may let an unauthenticated attacker execute unauthorized code or commands using nothing more than crafted requests. The vendor-assigned CVSS v3.1 score is 9.8, and one entire release branch (7.2) has no fix. For FortiMail administrators, the practical question is which firmware build each appliance is running today.

The supplied CVE data lists the vendor as "Unknown". The affected vendor is Fortinet, Inc., and the authoritative source is Fortinet PSIRT advisory FG-IR-26-199. FortiMail is Fortinet's email security product, covering spam, phishing, malware, impersonation and business email compromise. It ships as customer-managed appliances and virtual machines as well as the hosted FortiMail Cloud service. Fortinet reports more than 900,000 customers across over 50 enterprise products. Those are company-reported figures, not a measurement of FortiMail market share.

Technical information

Root cause: CWE-22 in the FortiMail API

Fortinet classifies the bug as CWE-22, Improper Limitation of a Pathname to a Restricted Directory. MITRE defines this weakness as constructing a pathname from external input without neutralizing elements that can make the path resolve outside an intended parent directory. In practice that usually means sequences such as ../ in attacker-controlled input that walk out of the folder the application meant to confine file access to.

The stated impact sets this instance apart. Fortinet does not describe a file read limited to a restricted directory. It states the potential consequence is execution of unauthorized code or commands, reachable without authentication. The CWE definition explains the containment failure class, but it does not tell us the internal chain FortiMail follows from a traversed path to execution, and Fortinet has not published that chain.

What the advisory discloses

  • Vendor and product: Fortinet FortiMail
  • Affected component: API
  • Authentication requirement: none (unauthenticated attack)
  • Delivery method: crafted requests
  • Potential outcome: execution of unauthorized code or commands
  • Weakness: CWE-22
  • Severity: CVSS v3.1 base score 9.8, Critical, supplied by Fortinet as the CNA. NVD shows no separate NIST assessment, so the score should be attributed to Fortinet.

The base vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In plain terms, that means a network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, and high impact to confidentiality, integrity and availability. Per the CVSS specification these are intrinsic Base metrics describing the vulnerability, not measurements of observed attacks or incident damage.

Attack flow, as far as public information allows

Based only on the advisory and the CVSS vector, the attack path looks like this:

  1. An attacker with network reachability to the FortiMail API (AV:N) sends requests without any credentials (PR:N) and without needing a user to do anything (UI:N).
  2. The request is crafted so that a pathname derived from external input is not properly neutralized by the application.
  3. The resulting path resolves outside the directory FortiMail intended to restrict access to.
  4. Fortinet states that this may result in execution of unauthorized code or commands on the device.

The advisory does not disclose the specific endpoint, the request format, the vulnerable filesystem path, any payload, or the intermediate steps that connect pathname traversal to execution. The secondary sources we reviewed (Rescana, VulDB) add no CVE-specific proof of concept or indicators of compromise. We therefore do not attempt to reconstruct a reproducible exploitation method or exploit signature.

Exploitation status

Fortinet's advisory lists "Known Exploited: No". Rescana's November 11, 2026 review also reports the relevant advisories as not known exploited and the CVE as absent from the CISA Known Exploited Vulnerabilities catalog at the time of its check. No threat actor, campaign, malware family or victim population has been linked to this CVE in the reviewed sources. That status holds as of those dates and does not prove that exploitation is impossible.

A different FortiMail path traversal is easy to confuse with this one. CVE-2026-104286 (advisory FG-IR-26-175) was added to CISA's KEV catalog on October 1, 2026, and Singapore's Cyber Security Agency describes it as allowing unauthenticated arbitrary file writes through crafted HTTP or HTTPS requests. Shared vendor, product and weakness class do not mean shared exploit chain or shared indicators, so that incident's status and artifacts should stay attached to its own CVE.

Record inconsistencies

Fortinet dates its initial advisory November 10, 2026, while NVD lists publication and last modification on November 11, 2026. At retrieval, the CVE.org page still displayed a reserved record even though Fortinet and NVD carried full details. For scope and remediation, the Fortinet advisory is the actionable source.

Patch information

FortiMail is closed source, so there is no public commit, diff or code snippet to study. Everything below comes from FG-IR-26-199 and the release records around it.

Fixed releases (from FG-IR-26-199)

  • FortiMail 8.0: vulnerable 8.0.0 through 8.0.1, fixed in 8.0.2 or above. The release notes describe 8.0.2 as build 263.
  • FortiMail 7.6: vulnerable 7.6.0 through 7.6.6, fixed in 7.6.7 or above.
  • FortiMail 7.4: vulnerable 7.4.0 through 7.4.8, fixed in 7.4.9 or above.
  • FortiMail 7.2: all versions vulnerable (NVD lists 7.2.0 through 7.2.9). There is no fix on this branch. Fortinet only says to "migrate to a fixed release".

For 7.2 customers this means moving to a newer branch rather than applying a 7.2.x update. Fortinet's earlier October hardening table, as reported by Rescana, told 7.2 users to move to the 7.4 branch or later. Rescana also points administrators to Fortinet's upgrade path tool for planning the jump.

FortiMail Cloud was patched by Fortinet

Fortinet says it fixed the hosted service on October 5, 2026 by moving all Cloud firmware to v7.6.7 GA or v8.0.2 GA. FortiMail Cloud customers need not take any action for this issue. This statement applies to the FortiMail Cloud service only. It does not cover customer-managed FortiMail appliances or virtual machines that happen to be hosted in a cloud environment.

The fix shipped weeks before the advisory

  • Per Rescana's review of the release note change logs, FortiMail 7.6.7 is dated October 2, and 8.0.2 and 7.4.9 are dated October 3. Fortinet then included them in its coordinated "security hardening release" announced October 21.
  • At that time Fortinet published no CVE IDs or per-issue details. FG-IR-26-199, which ties these builds to CVE-2026-126147, only appeared on November 10, 2026.
  • Any appliance upgraded to one of these builds in October was already protected before the CVE was public. Check the running firmware version. Do not rely on when you patched relative to the advisory date.

One upgrade covers several advisories

The same releases (8.0.2, 7.6.7, 7.4.9) also fix the other critical FortiMail advisories in the batch: FG-IR-26-216, FG-IR-26-207 and FG-IR-26-208. FG-IR-26-200 is fixed in 8.0.2 and 7.6.7 only, because 7.4 and 7.2 are not affected by it. Rescana also notes that these fixed versions match those in the earlier advisory FG-IR-26-175 (CVE-2026-104286, exploited in the wild). Fortinet has not said whether the two issues are related, so we do not assume they are. Either way, one firmware floor covers several critical issues.

What the fix probably changes (inference, not confirmed)

Fixes for CWE-22 bugs typically do three things:

  • Resolve the full real path of the requested file before using it.
  • Reject the request if that path falls outside an allowed base directory.
  • Block decoded or encoded traversal sequences before any file access happens.

Fortinet has not said which component or endpoint changed, and there is no diff to confirm any of this. Treat it as background on the bug class. It does not describe Fortinet's actual code change.

No stopgap

The advisory lists "Virtual Patch: No", meaning there is no FortiGuard IPS signature to bridge the gap, and no separate workaround is documented. Rescana discusses an IPS virtual patch for FG-IR-26-270, which is a different advisory and should not be treated as protection for FG-IR-26-199. Upgrading the firmware is the only fix Fortinet offers.

Credit

Fortinet credits Sam Mckee and Theo Leleu of its Product Security team, who found the flaw internally using the AI model Claude Mythos.

Affected systems and versions

  • FortiMail 8.0: 8.0.0 through 8.0.1
  • FortiMail 7.6: 7.6.0 through 7.6.6
  • FortiMail 7.4: 7.4.0 through 7.4.8
  • FortiMail 7.2: all versions (NVD lists 7.2.0 through 7.2.9)
  • FortiMail Cloud: remediated by Fortinet on October 5, 2026, with no customer action required

The vulnerable component is the FortiMail API, and the vector assumes network reachability to it. The advisory applies to customer-managed FortiMail appliances and virtual machines on the listed versions, regardless of where they are hosted.

Vendor security history

Fortinet's track record with FortiMail and its other products gives some context, though none of it changes the exploitation status of this specific CVE:

  • CVE-2026-104286 (FortiMail, FG-IR-26-175): a separate path traversal that CISA added to its KEV catalog on October 1, 2026 based on evidence of active exploitation. Singapore's Cyber Security Agency describes it as permitting unauthenticated arbitrary file writes via crafted HTTP or HTTPS requests and points to FG-IR-26-175 for workarounds and known indicators.
  • CVE-2025-64446 and CVE-2025-58034 (FortiWeb): CISA reported exploitation of both, including a chain capable of unauthenticated remote code execution. This is historical evidence about another product, not attribution or exploit guidance for this FortiMail flaw.

On the process side, Fortinet's published vulnerability policy describes collaborative investigation, severity-based prioritization, regularly scheduled advisories, and accelerated announcements when observed exploitation increases customer risk. For this CVE, Fortinet reports that it found the flaw internally, and it remediated FortiMail Cloud on October 5, 2026, more than a month before the November 10 advisory. On market position, Fortinet was placed in the Challenger category of the 2025 Gartner Magic Quadrant for Email Security. Gartner notes its assessments are research opinions, not endorsements.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization