Skip to main content
Vulnerability Database/CVE-2026-106173

CVE-2026-106173: FortiSIEM Path Traversal Vulnerability

CVE-2026-106173 is a path traversal flaw in Fortinet FortiSIEM 7.5.0 that enables attackers to execute unauthorized code through crafted packets. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106173 Overview

CVE-2026-106173 is a path traversal vulnerability [CWE-22] in Fortinet FortiSIEM 7.5.0. The flaw stems from improper limitation of a pathname to a restricted directory. Attackers can send specially crafted packets to execute unauthorized code or commands on affected systems.

The vulnerability is network-exploitable without authentication or user interaction. Fortinet published advisory FG-IR-26-180 describing the issue. The weakness affects the Security Information and Event Management (SIEM) platform used by enterprises for log aggregation and threat detection.

Critical Impact

Unauthenticated remote attackers can execute arbitrary code or commands on FortiSIEM 7.5.0 instances by delivering crafted packets, undermining the integrity of the SIEM collecting enterprise security telemetry.

Affected Products

  • Fortinet FortiSIEM 7.5.0
  • Fortinet FortiSIEM collectors and supervisors on the affected release
  • Deployments exposing FortiSIEM services to untrusted networks

Discovery Timeline

  • 2026-10-13 - CVE-2026-106173 published to the National Vulnerability Database (NVD)
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-106173

Vulnerability Analysis

The vulnerability is a path traversal weakness classified under [CWE-22]. FortiSIEM 7.5.0 fails to properly restrict file path inputs supplied through network-facing components. An attacker can craft packets containing traversal sequences such as ../ to escape the intended directory boundary.

The traversal reaches code paths that interpret attacker-controlled filenames or commands. This allows execution of unauthorized code or operating system commands in the context of the FortiSIEM service. Because FortiSIEM centralizes security logs and detections, compromise of the appliance degrades downstream monitoring across the environment.

Fortinet documents the issue in advisory FG-IR-26-180. Review the Fortinet PSIRT Advisory FG-IR-26-180 for vendor-confirmed version boundaries and fixed builds.

Root Cause

The root cause is missing or insufficient canonicalization of file path input before use in filesystem or command operations. Normalization routines fail to reject sequences that resolve outside the restricted directory. When attacker input flows into a sink that reads, writes, or executes based on path, the traversal translates into code or command execution.

Attack Vector

The attack vector is network-based and does not require authentication or user interaction. An attacker sends specially crafted packets to a FortiSIEM 7.5.0 service. The packet payload embeds traversal sequences that reach a vulnerable file-handling or command-dispatch routine. Successful exploitation yields execution of attacker-chosen code or commands on the appliance.

No verified public proof-of-concept code is available at the time of writing. Describing exploitation in prose only, the attacker leverages the lack of path validation to reference files or scripts outside the intended working directory and trigger their execution through the vulnerable handler.

Detection Methods for CVE-2026-106173

Indicators of Compromise

  • Inbound requests to FortiSIEM services containing ../, ..\, URL-encoded %2e%2e%2f, or double-encoded traversal sequences
  • Unexpected child processes spawned by FortiSIEM daemons, including shell interpreters or scripting engines
  • New or modified files in FortiSIEM application directories outside normal upgrade windows
  • Outbound connections from FortiSIEM collectors or supervisors to unknown external hosts

Detection Strategies

  • Inspect network traffic to FortiSIEM management and ingestion ports for traversal patterns and anomalous payload sizes
  • Correlate FortiSIEM process ancestry with baseline behavior to identify unauthorized command execution
  • Review FortiSIEM audit and system logs for unexpected file access attempts and failed path resolutions
  • Alert on configuration file changes and new executable artifacts on FortiSIEM hosts

Monitoring Recommendations

  • Enable detailed logging on perimeter devices in front of FortiSIEM and forward to an independent log store
  • Monitor FortiSIEM appliances for integrity drift using file integrity monitoring
  • Track authentication, session, and command execution events on the FortiSIEM host operating system
  • Validate that FortiSIEM self-telemetry is still arriving at the central SIEM function to detect tampering

How to Mitigate CVE-2026-106173

Immediate Actions Required

  • Identify all FortiSIEM 7.5.0 deployments, including supervisors, workers, and collectors
  • Restrict network reachability to FortiSIEM services to trusted management networks and known log sources
  • Apply the fixed version listed in Fortinet advisory FG-IR-26-180 as soon as it is available in your change window
  • Rotate credentials, API keys, and integration secrets stored on potentially exposed appliances

Patch Information

Fortinet publishes affected and fixed versions in advisory FG-IR-26-180. Consult the Fortinet PSIRT Advisory FG-IR-26-180 for the authoritative upgrade path for FortiSIEM 7.5.0. Validate upgrades in a staging environment and confirm log ingestion and correlation rules continue to function after patching.

Workarounds

  • Place FortiSIEM behind a filtering device that blocks path traversal patterns in inbound traffic
  • Enforce source IP allowlists on FortiSIEM management and ingestion endpoints
  • Disable or firewall off any FortiSIEM services not required by the deployment
  • Increase monitoring on FortiSIEM hosts until the vendor patch is applied
bash
# Configuration example: restrict inbound access to FortiSIEM to known sources
# Replace interface and subnet values with environment-specific values
iptables -A INPUT -p tcp -s 10.10.0.0/16 --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.