Automated Threat Modeling

Brief Summary: FortiMail CVE-2026-126153, Unauthenticated Path Traversal Leading to Command Execution

A brief summary of CVE-2026-126153, a CVSS 7.5 path traversal flaw in the Fortinet FortiMail API that may let an unauthenticated attacker execute unauthorized commands. Covers affected branches, fixed builds, the FortiMail 7.2 migration requirement and FortiMail Cloud status.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: FortiMail CVE-2026-126153, Unauthenticated Path Traversal Leading to Command Execution

Introduction

A path traversal flaw in the Fortinet FortiMail API may allow an unauthenticated attacker on the network to execute unauthorized commands by sending crafted requests. Fortinet shipped the fixed firmware on October 3, 2026, but held advisory FG-IR-26-205 until November 10, 2026. Patched builds have therefore been available to compare against vulnerable ones for weeks, a point Fortinet itself raises when explaining why upgrading matters.

FortiMail is Fortinet's email security platform, built to protect organizations against spam, phishing, malware, impersonation and business email compromise. It is deployed as physical appliances, as virtual machines and as the hosted FortiMail Cloud service. Fortinet, founded in 2000, is an established network security vendor whose Security Fabric spans secure networking, security operations and universal SASE. FortiMail is one part of that broadly deployed security portfolio.

Key facts at a glance:

  • CVE: CVE-2026-126153 (Fortinet advisory FG-IR-26-205)
  • Weakness: CWE-22, improper limitation of a pathname to a restricted directory
  • Severity: CVSS v3.1 base score 7.5 (High), assigned by Fortinet as CNA. Fortinet also shows a separate temporal score of 7.1
  • Authentication required: None
  • Known exploited: No, per the vendor advisory
  • Virtual patch: No

Technical information

Root cause: CWE-22 in the API

Fortinet classifies this bug as CWE-22 and lists the affected component as the API. MITRE defines CWE-22 as a failure to keep a pathname constructed from external input within its intended parent directory, so that special pathname elements cause resolution outside that directory. The CWE taxonomy covers both relative and absolute traversal, but the classification on its own does not tell us which request syntax or pathname handling behavior triggers this specific FortiMail issue.

Fortinet does disclose how the weakness connects to its outcome. A pathname restriction failure, reachable through crafted requests, may let an unauthenticated attacker execute unauthorized commands. The advisory does not identify the affected file handling function, the API route, the request method, the port, a payload, or how traversal is turned into command execution. It also does not state that commands run as root, nor does it claim appliance takeover, email theft or lateral movement for this CVE.

The fix is closed source. There is no public commit, diff or technical root-cause write-up, so everything here comes from the advisory, NVD, Fortinet's firmware feed and its disclosure blog post.

What the CVSS vector measures

NVD records the following base vector, sourced from Fortinet:

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

Interpreted against the FIRST CVSS v3.1 specification:

  • Attack Vector: Network. Exploitable remotely over the network.
  • Attack Complexity: Low. No special conditions are scored.
  • Privileges Required: None. No account is needed.
  • User Interaction: None. No other user has to participate.
  • Scope: Unchanged. No scope change is scored.
  • Confidentiality: None, Integrity: High, Availability: None.

The impact profile is integrity only. "Unauthenticated command execution" sounds broader than that, and it should be taken seriously, but the published scoring does not support extending it into confidentiality loss such as mailbox access, or into availability impact. NIST's own assessment was not available in the retrieved NVD record. Fortinet's 7.1 temporal score is a separate figure and does not replace the 7.5 base score.

Attack flow as disclosed

Based solely on the advisory and the CVSS vector, the attack reduces to the following sequence:

  1. The attacker has network reachability to the API of an affected, customer-managed FortiMail instance. No credentials and no user interaction are required.
  2. The attacker sends a crafted request whose pathname input contains elements that resolve outside the directory the API is meant to restrict access to.
  3. The vulnerable firmware fails to confine the resolved path to that restricted directory.
  4. According to Fortinet, this condition can result in the execution of unauthorized commands.

The steps between 3 and 4 are not public. We have no sourced information on which file operation is reached, whether traversal enables a write, read or include that leads to execution, or what privilege context the resulting commands run in. Any detailed exploit reconstruction would currently be speculation.

Why the disclosure timeline matters

Fortinet's blog explains that it released the fixed firmware first and held the public advisory for the next Patch Tuesday, giving customers a window to upgrade before details became public. Fortinet also notes that once updates are public, the fixes show attackers where the code changed. With fixed builds posted on October 3, 2026, anyone can now diff patched and unpatched firmware, which shortens the practical gap between disclosure and independent rediscovery of the bug.

Patch information

Fortinet fixed CVE-2026-126153 in new FortiMail firmware. Fixed releases by branch:

  • FortiMail 8.0: vulnerable 8.0.0 through 8.0.1, fixed in 8.0.2 or above, build B0263. The 8.0.2 release notes confirm it is build 263.
  • FortiMail 7.6: vulnerable 7.6.0 through 7.6.6, fixed in 7.6.7 or above, build B0858.
  • FortiMail 7.4: vulnerable 7.4.0 through 7.4.8, fixed in 7.4.9 or above, build B0630.
  • FortiMail 7.2: all versions (7.2.0 through 7.2.9) are vulnerable, and this branch has no fix. Fortinet directs customers to move to a fixed release, and its blog says to upgrade to the 7.4 branch or later.

Fortinet's support firmware feed shows all three fixed builds (8.0.2 B0263, 7.6.7 B0858, 7.4.9 B0630) were posted on October 3, 2026, more than a month before the advisory went public on November 10, 2026.

What the fix covers. Fortinet does not name the specific code path or explain how the check was hardened. It states only that its Product Security team found the issue internally using an AI model. Path traversal fixes in general canonicalise the requested path and reject it unless it stays inside the allowed base directory. That is the typical pattern for this bug class, but Fortinet has not confirmed it for FortiMail, and it should not be read as a description of what changed.

FortiMail Cloud. Fortinet fixed its hosted FortiMail Cloud service on October 5, 2026 by moving all tenants to 7.6.7 GA or 8.0.2 GA. Cloud customers do not need to take any action. Operators must upgrade their own on-premises appliances and VMs.

No virtual patch. The advisory lists "Virtual Patch: No". Fortinet has not published a FortiGuard IPS or WAF signature that blocks this traversal in transit, and it provides no workaround. Installing fixed firmware is the only vendor fix.

Verifying remediation. The build number in the system dashboard or CLI should be at least the fixed build for your branch (B0263, B0858 or B0630). Any 7.2.x unit remains vulnerable at any build until it moves to the 7.4 branch or later. Review Fortinet's FortiMail upgrade path documentation before jumping across branches.

Affected systems and versions

  • FortiMail 8.0.0 through 8.0.1
  • FortiMail 7.6.0 through 7.6.6
  • FortiMail 7.4.0 through 7.4.8
  • FortiMail 7.2, all versions. NVD's structured range lists 7.2.0 through 7.2.9, while Fortinet's advisory says all 7.2 versions. We recommend working from the vendor's broader wording and its explicit migration instruction.

Deployment model determines who acts:

  • Customer-managed appliances and virtual machines on an affected version must be upgraded (8.0, 7.6, 7.4) or migrated (7.2). A published fix is not evidence that an installation already runs it.
  • Fortinet remediated FortiMail Cloud on October 5, 2026. That applies only to the managed service, not to customer-operated instances.

The advisory marks the issue as Known Exploited: No, and the reviewed records identify no threat actor, campaign, public exploit or indicators of compromise for this CVE. HKCERT included it in its November 11, 2026 bulletin covering multiple Fortinet vulnerabilities and recommends applying vendor fixes. That bulletin's impact statements are aggregate and should not be read as specific to this CVE.

Vendor security history

Fortinet's published security vulnerability policy describes STRIDE-based threat modeling, static and dynamic application security testing, fuzzing, software bill of materials tracking, manual audits and penetration testing, with remediated findings published through PSIRT advisories. The company reports that approximately 60% of its vulnerabilities discovered in 2025 were identified internally. That figure measures discovery. It says nothing about how many vulnerabilities were prevented. CVE-2026-126153 was also found internally, and Fortinet credits Gwendal Guegniaud of its Product Security team with the discovery.

The same product family also has a recent, documented exploitation record. In an alert dated October 2, 2026, Belgium's Centre for Cybersecurity reported that several organizations confirmed exploitation of CVE-2026-104286, a separate FortiMail vulnerability involving unauthenticated arbitrary file writing, and that CISA added it to its Known Exploited Vulnerabilities catalog. The CCB warned about device takeover, access to company email and use of the device as a foothold. Those consequences belong to CVE-2026-104286. Nothing in the reviewed sources ties its actors or techniques to CVE-2026-126153, even though both affect FortiMail and involve pathname handling.

For context on market position, Fortinet reports Gartner named it a Leader in the 2026 Magic Quadrant for Hybrid Mesh Firewall. That recognition concerns firewalls, not FortiMail, and says nothing about the security quality of this product line.

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