Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: fortinet (15 articles)Clear

Critical FortiSIEM path traversal flaw gains public exploit enabling unauthenticated remote code execution

Fortinet patched CVE-2026-106173, a critical path traversal flaw rated 9.4 in FortiSIEM that lets an unauthenticated attacker execute commands through specially crafted packets, and researchers have now released a public proof of concept. The attacker connects to the gRPC service on TCP port 27918 and writes a file outside the intended directory, using a null byte in the query-id parameter to truncate the filename so the write lands on an existing path such as a Redis health-check script that cron runs every 60 seconds. FortiSIEM 7.5.0 is affected, 7.6 is not, and users should upgrade to 7.5.1 or above. Horizon3.ai published the research.

Check
Upgrade FortiSIEM 7.5.0 to 7.5.1 or above immediately, since a public proof of concept now exists, and restrict access to the gRPC service on port 27918.
Affected
FortiSIEM 7.5.0 lets an unauthenticated attacker write a file outside the intended directory through crafted packets to the gRPC service, achieving remote code execution via a cron-run script.
Fix
Apply the FortiSIEM 7.5.1 upgrade, restrict network access to the management and gRPC services, and review hosts for unexpected changes to cron-run scripts.

FBI warns FortiBleed credential campaign stays active and locks administrators out of Fortinet VPN gateways

The FBI and Secret Service warned that FortiBleed, a credential-harvesting campaign against internet-facing FortiGate firewalls and SSL VPN gateways, remains active. The Russian-speaking operation uses credential stuffing and password spraying, then deploys a Go tool called FortigateSniffer to intercept authentication traffic, exploiting reused or leaked credentials and legacy SHA-256 password storage rather than a software flaw. It had collected more than 86,644 working device credentials across 194 countries as of June. Attackers create new admin accounts and reuse session cookies for persistence, and some victims are locked out when original accounts are changed or deleted. Operator overlaps link it to INC and Lynx ransomware.

Check
Review internet-facing Fortinet firewalls for unfamiliar admin accounts, reset VPN and admin passwords, terminate active sessions, and enable phishing-resistant authentication per the FBI and CISA guidance.
Affected
Internet-facing FortiGate firewalls with reused, leaked, or weakly stored credentials let attackers validate logins, add admin accounts, hijack sessions, and lock out legitimate administrators.
Fix
Reset VPN and admin credentials, remove rogue accounts such as fortiAdmin or forticloud-sync, store credentials with PBKDF2, enable strong authentication, and report incidents to the FBI and Secret Service.

Fortinet FortiMail zero-day under active exploitation allows unauthenticated arbitrary file writes

CISA added a critical FortiMail flaw to its Known Exploited Vulnerabilities catalog after reports of active exploitation. Tracked as CVE-2026-104286 and rated 9.8, it combines a path traversal with improper NULL byte neutralization, letting an unauthenticated attacker write arbitrary files on the underlying system through crafted HTTP or HTTPS requests. Fortinet confirmed in-the-wild exploitation. Affected versions are 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, with fixed builds coming in the 8.0.2, 7.6.7, and 7.4.9 releases and a move off 7.2 to branch 7.4. Until fixes land for some versions, Fortinet recommends disabling IBE feature support and restricting access to the administrative interface.

Check
Identify internet-facing FortiMail appliances, apply the fixed release for your branch when available, and meanwhile disable IBE and restrict the admin interface.
Affected
FortiMail versions in the affected ranges let an unauthenticated attacker write arbitrary files via crafted web requests, and exploitation is already occurring.
Fix
Upgrade to the fixed FortiMail builds, apply the IBE and admin-access workarounds in the interim, and review hosts for unexpected written files.

CISA flags exploited Cisco, Citrix, Fortinet, and WatchGuard edge flaws

CISA added several actively exploited flaws in internet-facing security appliances to its catalog, ordering federal agencies to patch by September 12. The most severe, CVE-2026-20079 scored 10.0, is an authentication bypass in Cisco Secure Firewall Management Center that lets an unauthenticated attacker run scripts and gain root on the device; Cisco confirmed exploitation since August. A Citrix NetScaler authentication bypass, CVE-2026-19490, saw a surge of attacks on September 8, and a Fortinet FortiOS flaw, CVE-2025-25249, is being used to deliver a remote access trojan. Separately, CISA warned that a critical WatchGuard Firebox firewall flaw is now being exploited in ransomware attacks. Edge appliances remain prime targets.

Check
Immediately patch internet-facing Cisco Secure FMC, Citrix NetScaler, Fortinet FortiOS, and WatchGuard Firebox devices to fixed versions, prioritizing anything reachable from the internet, and hunt exposed appliances for signs of compromise.
Affected
Organizations running affected Cisco Secure FMC, Citrix NetScaler, Fortinet FortiOS, or WatchGuard Firebox appliances (CVE-2026-20079, CVE-2026-19490, CVE-2025-25249); all are exploited, from unauthenticated root access to RAT and ransomware deployment.
Fix
Patch these appliances now given the short federal deadline and active exploitation, restrict management interfaces from the internet, monitor for auth-bypass and script-execution activity, and treat any exposed unpatched device as compromised.

CISA orders agencies to patch two exploited Fortinet FortiSandbox flaws

CISA has added two critical Fortinet FortiSandbox vulnerabilities to its exploited-vulnerabilities catalog and ordered federal agencies to patch them by July 19. Tracked as CVE-2026-39808 and CVE-2026-25089, both are operating-system command injection flaws that let an unauthenticated attacker run commands remotely with low complexity and no user interaction. Fortinet disclosed and fixed them in April and June, and threat intelligence firm Defused reported in-the-wild abuse of FortiSandbox flaws in June. FortiSandbox is a threat-detection appliance, and Fortinet gear sits at many network edges, so these devices are a recurring target in espionage and ransomware campaigns, making prompt patching important.

Check
Identify Fortinet FortiSandbox appliances in your environment, check their versions against Fortinet's advisories for these flaws, and upgrade to the fixed releases, prioritizing any internet-reachable or edge-facing devices.
Affected
Organizations running affected Fortinet FortiSandbox versions (CVE-2026-39808, CVE-2026-25089); unauthenticated attackers can run commands remotely, and active exploitation of FortiSandbox flaws has been reported, making unpatched appliances a real risk.
Fix
Upgrade FortiSandbox to the fixed versions, such as 4.4.9 for the April flaw, restrict and monitor management access to these appliances, and review logs and configurations for unauthorized commands or changes.

FortiBleed leak exposes VPN credentials for nearly 74,000 Fortinet firewalls

A newly surfaced dataset dubbed FortiBleed exposes what appear to be Fortinet and FortiGate VPN credentials tied to 73,932 firewall URLs at organizations around the world. Separately, researchers at SOCRadar report roughly 30,000 compromised Fortinet firewalls exposing networks to attack. Exposed VPN credentials are a direct route into corporate networks, letting attackers log in as legitimate users, bypass perimeter defenses, and stage ransomware or data theft. Fortinet gear is a perennial target, with many of these exposures stemming from past unpatched flaws and credential harvesting. Organizations cannot assume old Fortinet credentials are safe just because devices were later patched.

Check
Check whether your Fortinet or FortiGate VPN appliances appear in the exposed dataset, review VPN authentication logs for logins from unfamiliar locations, and confirm whether previously exposed devices were fully remediated.
Affected
Organizations running internet-facing Fortinet and FortiGate VPNs whose credentials appear among the 73,932 exposed firewall URLs; reused or never-rotated VPN passwords are most at risk.
Fix
Force-reset all Fortinet VPN credentials, enable phishing-resistant MFA on VPN access, restrict management interfaces, and fully patch or replace appliances, treating any potentially exposed device as compromised until verified.

Attackers now exploiting three critical FortiSandbox flaws, one with AI-built exploit

Threat-intelligence firm Defused reports that attackers are now exploiting three critical flaws in Fortinet's FortiSandbox, the appliance other Fortinet products rely on to judge whether files are malicious. Two (CVE-2026-39813, a JRPC API path traversal that bypasses authentication, and CVE-2026-39808, an unauthenticated command-injection that runs code as root) were patched in April; the third (CVE-2026-25089) only last week. All are unauthenticated and rated critical. Compromising a sandbox is especially dangerous because attackers can make it wave real malware through as clean. Notably, the exploit for one flaw appears to have been generated with AI and is likely faulty, yet attackers are trying it anyway.

Check
Identify FortiSandbox, FortiSandbox Cloud, and PaaS instances and their versions, confirm whether the web and JRPC API interfaces are reachable from untrusted networks, and review logs for unauthenticated command execution.
Affected
FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS that are unpatched against CVE-2026-39813, CVE-2026-39808, or CVE-2026-25089, especially instances exposed to untrusted networks; all three need no authentication.
Fix
Upgrade FortiSandbox to the fixed releases for all three CVEs immediately, restrict management and API interfaces to trusted networks, and treat any unpatched appliance as potentially compromised pending review.

Critical FortiSandbox flaw lets unauthenticated attackers run commands

Fortinet has patched a critical flaw in FortiSandbox, the appliance that detonates suspicious files and feeds malware verdicts to the rest of a Fortinet security deployment. The bug (CVE-2026-25089, rated 9.8) is an OS command injection in the web interface that lets a remote, unauthenticated attacker run arbitrary commands by sending crafted HTTP requests. Compromising a sandbox is especially dangerous because attackers can both pivot deeper into the network and blind the very system meant to catch malware. Fixed versions are FortiSandbox 5.0.6 and 4.4.9, with matching updates for the Cloud and PaaS editions.

Check
Identify FortiSandbox appliances and their version and whether the web interface is reachable from untrusted networks, and review HTTP and admin logs for unexpected command execution.
Affected
FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS web interfaces before the fixed releases (CVE-2026-25089), reachable by remote unauthenticated attackers over HTTP.
Fix
Upgrade FortiSandbox to 5.0.6 or 4.4.9 (and the matching Cloud and PaaS releases) now, and restrict management-interface access to trusted networks until patched.

FortiClient EMS CVE-2026-35616 actively exploited to deploy EKZ infostealer - disguised as endpoint update via VPN scripting

Arctic Wolf has observed active exploitation of CVE-2026-35616, an authentication-bypass flaw in FortiClient Enterprise Management Server (EMS), to deliver an undocumented credential stealer called EKZ. Attackers abuse the endpoint APIs to perform administrative actions without authentication, then modify EMS configuration and VPN policies to inject malicious scripts. Seconds after endpoints establish an IPsec tunnel to a Fortinet-managed gateway, EKZ is pushed disguised as an endpoint update via VPN scripting workflows. Fortinet released emergency hotfixes for versions 7.4.5 and 7.4.6 in early April and CISA ordered federal agencies to patch the same week; Shadowserver tracked 2,000 internet-exposed EMS instances at the time.

Check
Inventory FortiClient EMS deployments and confirm patch level. Search for unauthorized EMS configuration or VPN policy changes since early April. Look for EKZ stealer behavior on endpoints.
Affected
FortiClient EMS versions before the 7.4.5 and 7.4.6 hotfixes. Internet-exposed instances are at highest risk; Shadowserver counted 2,000 exposed in April when CISA mandated federal patching.
Fix
Apply the Fortinet hotfixes. Audit EMS admin actions and VPN policy modifications since April. Rotate credentials and certificates that EMS managed. Apply Arctic Wolf EKZ IoCs.

Critical patches from Ivanti, Fortinet, SAP, VMware Fusion, and n8n - RCE, SQL injection, prototype pollution

A wave of critical patches landed across enterprise vendors. Fortinet shipped fixes for two unauthenticated code-execution flaws (CVE-2026-44277 in FortiAuthenticator, CVE-2026-26083 in FortiSandbox / FortiSandbox Cloud / FortiSandbox PaaS, both CVSS 9.1). SAP patched a 9.6-rated SQL injection in S/4HANA and a missing-auth check in SAP Commerce that allows unauthenticated code execution. Ivanti Xtraction got a fix for arbitrary file read and write. Broadcom patched a VMware Fusion macOS local-privilege-escalation (CVE-2026-41702). And the n8n automation platform shipped five CVSS 9.4 issues, including XML-driven prototype pollution that authenticated workflow editors could turn into RCE.

Check
Pull the installed-version list for FortiAuthenticator, FortiSandbox/Cloud/PaaS, SAP S/4HANA, SAP Commerce, Ivanti Xtraction, VMware Fusion, and self-hosted n8n. Compare against the fixed versions in action_solution.
Affected
FortiAuthenticator before 6.5.7/6.6.9/8.0.3; FortiSandbox before 4.4.9/5.0.2; SAP S/4HANA, SAP Commerce, Ivanti Xtraction before 2026.2; VMware Fusion before 26H1; n8n before 1.123.32/2.17.4/2.18.1.
Fix
Upgrade FortiAuthenticator to 6.5.7/6.6.9/8.0.3, FortiSandbox to 4.4.9/5.0.2, Ivanti Xtraction to 2026.2, VMware Fusion to 26H1, and n8n to 1.123.32/2.17.4/2.18.1. Apply SAP's May notes for CVE-2026-34260 and CVE-2026-34263.