CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Fortinet FortiManager

product · product:fortinet-fortimanager single-source

Coverage
2
first 2026-08-15 → last 2026-10-16
Latest activity
2026-10-16
Unit 42: a memory-resident FortiGate implant rides an exploited FortiOS flaw that has no fix on 7.2, 7.0 and…
Peak priority
notable
2 notable
Targets
telco
sectors: telco, public-sector, finance · regions: europe
Sources cited
8
4 hosts

Action items (3)

Do-now tasks recorded on the entries about Fortinet FortiManager, newest first. Check the date before acting on an older one.

  • Upgrade FortiClient for Windows to 7.4.4 or 7.2.12 across the remote-working fleet, or disable application-based filtering in the EMS remote-access profile's VPN tunnel settings in the meantime; the flaw needs no credential, only an attacker positioned to answer the endpoint's DNS, which is the normal condition of a laptop on an untrusted network before the tunnel comes up.
    2026-08-15CVE-2026-26035 +3
  • Check whether the Wildcard option is enabled on any FortiWeb Remote Type administrator account (System > Administrators) and disable it; this is Fortinet's own workaround for CVE-2026-26035 and it removes the exposure without waiting for a maintenance window, ahead of upgrading to 8.0.3, 7.6.7 or 7.4.12. On the 7.2 and 7.0 branches that configuration change is the whole remediation for now, because their fixed builds are listed as upcoming rather than released.
    2026-08-15CVE-2026-26035 +3
  • Check whether fgfm-peercert-withoutsn is set on any FortiManager or FortiManager Cloud instance and disable it, then upgrade to 7.6.2 / 7.4.6 / 7.2.10, with the option set, a valid certificate is enough to impersonate a managed FortiGate over FGFM.
    2026-08-15CVE-2026-26035 +3

Defender insights

What each entry about Fortinet FortiManager tells a defender to do, newest first.

2026-10-16NOTABLEexploitedUnit 42: a memory-resident FortiGate implant rides an exploited FortiOS flaw that has no fix on 7.2, 7.0 and 6.4

Exposure · triage · detection

Story timeline

  1. 2026-10-16PEERSTITCH: a memory-resident FortiGate implant installed through the FortiOS CLI path traversal CVE-2025-61624, which Fortinet lists as exploited and leaves unfixed on FortiOS 7.2, 7.0 and 6.4, after a FortiManager compromise exposed the configurations of 500+ firewalls
    active-threatsUnit 42: a memory-resident FortiGate implant rides an exploited FortiOS flaw that has no fix on 7.2, 7.0 and 6.4
  2. 2026-08-15CVE-2026-26035, FortiWeb: one non-default RADIUS admin setting turns any username and password into a valid GUI/CLI login, alongside an FGFM impersonation bug and a FortiClient flaw reachable by anyone who can answer a laptop's DNS
    trending-vulnerabilitiesFortinet patches a FortiWeb admin-login bypass gated on a 'Wildcard' option, an FGFM impersonation flaw, and a FortiClient RCE reached via crafted DNS
ATT&CK techniques (11 across 9 tactics)

11 techniques observed across 2 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessValid Accounts · External Remote Services · Exploit Public-Facing Application
  • ExecutionCommand and Scripting Interpreter: JavaScript
  • PersistenceValid Accounts · External Remote Services
  • Privilege EscalationProcess Injection: Ptrace System Calls · Exploitation for Privilege Escalation · Valid Accounts
  • StealthProcess Injection: Ptrace System Calls · Indicator Removal · Valid Accounts
  • Defense ImpairmentDisable or Modify Tools: Clear Linux or Mac System Logs
  • Credential AccessNetwork Sniffing · Unsecured Credentials: Credentials In Files · Adversary-in-the-Middle
  • DiscoveryNetwork Sniffing
  • CollectionAdversary-in-the-Middle

Initial Access TA0001

T1078Valid Accounts×2

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1190Exploit Public-Facing Application×2

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

Execution TA0002

T1059.007Command and Scripting Interpreter: JavaScript×1

Adversaries may abuse various implementations of JavaScript for execution. JavaScript (JS) is a platform-independent scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

Persistence TA0003

T1078Valid Accounts×2

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

Privilege Escalation TA0004

T1055.008Process Injection: Ptrace System Calls×1

Adversaries may inject malicious code into processes via ptrace (process trace) system calls in order to evade process-based defenses as well as possibly elevate privileges. Ptrace system call injection is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1068Exploitation for Privilege Escalation×1

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1078Valid Accounts×2

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

Stealth TA0005

T1055.008Process Injection: Ptrace System Calls×1

Adversaries may inject malicious code into processes via ptrace (process trace) system calls in order to evade process-based defenses as well as possibly elevate privileges. Ptrace system call injection is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1070Indicator Removal×1

Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity. Rather than broadly removing evidence, adversaries may target specific artifacts that appear anomalous or are likely to draw scrutiny, while leaving sufficient data intact to maintain the appearance of normal system behavior.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1078Valid Accounts×2

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

Defense Impairment TA0112

T1685.006Disable or Modify Tools: Clear Linux or Mac System Logs×1

Adversaries may clear system logs to hide evidence of an intrusion. macOS and Linux both keep track of system or user-initiated actions via system logs. The majority of native system logging is stored under the `/var/log/` directory. Subfolders in this directory categorize logs by their related functions, such as:

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

Credential Access TA0006

T1040Network Sniffing×1

Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1552.001Unsecured Credentials: Credentials In Files×1

Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

Discovery TA0007

T1040Network Sniffing×1

Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.

Evidence: 2026-10-16/peerstitch-fortigate-implant-cve-2025-61624-fortimanager · ATT&CK page ↗

Collection TA0009

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-08-15/fortiweb-radius-wildcard-bypass-fortimanager-fgfm · ATT&CK page ↗

Entries about Fortinet FortiManager (2)

2026-10-16 · view entry permalink →

NOTABLECVE-2025-61624exploitedNATOB2

PEERSTITCH: a memory-resident FortiGate implant installed through the FortiOS CLI path traversal CVE-2025-61624, which Fortinet lists as exploited and leaves unfixed on FortiOS 7.2, 7.0 and 6.4, after a FortiManager compromise exposed the configurations of 500+ firewalls

Unit 42 investigated a September 2024 intrusion at a telecommunications organization, tracked as cluster CL-STA-0954, that began with CVE-2024-47575 against a centralized FortiManager appliance: the attackers registered a rogue virtual FortiGate, then exfiltrated an archive with the running configurations, cryptographic material and database files of more than 500 managed FortiGate firewalls (Unit 42, 2026-10-14). Unit 42 recovered the configurations' reversible-ciphertext credentials by brute force; the attackers later logged in over SSL VPN with legitimate credentials and pushed packet-capture settings to downstream firewalls (Unit 42, 2026-10-14).

For root they used CVE-2025-61624, a path traversal in the FortiOS CLI system.auto-script engine that lets an authenticated administrative account read and write arbitrary files as root (Unit 42, 2026-10-14). That installed PEERSTITCH, an ARM64 injector that attaches with ptrace to the logging daemon miglogd and the IPsec daemon iked, allocates a 16 KB read-write-execute region, NOP-patches three fixed offsets and links the daemons through /proc memory so that tagged VPN sessions skip default FortiOS validation; it leaves no persistent binary on disk, opens no listening port and makes no outbound connection of its own (Unit 42, 2026-10-14). Command and control ran through the firewall's own Apache mod_md ACME module, whose DNS-01 challenge handler executes Node.js with parameters from an attacker-run ACME server and so opens a reverse shell (Unit 42, 2026-10-14).

Fortinet's advisory FG-IR-26-122 of 2026-04-14 covers the CLI path traversal in FortiOS, FortiPAM, FortiProxy and FortiSwitchManager, lists it as known exploited, and for FortiOS gives fixes only in 7.6.5 and 7.4.10, telling users of 7.2, 7.0 and 6.4 to migrate to a fixed release (Fortinet, 2026-04-14).

Triage: legitimate FortiManager work also creates and deletes auto-scripts and adds devices; the report's signals are ../ in an auto-script name, a device registered from outside the management network, and accounts that match no administrator or tenant the organization created.

PEERSTITCH leaves no persistent binary on disk, opens no listening ports and initiates no outbound network connections.

The vulnerability allows an authenticated administrative account to read and write arbitrary files as root via path traversal in the FortiOS CLI system.auto-script engine.

the attackers exfiltrated an archive containing running configurations, cryptographic material and database files containing information about more than 500 managed FortiGate firewalls

The cryptographic trust material governing the platform's relationship with every managed device leaves with the attacker and remains valid until it is rotated.

Palo Alto Networks Unit 42 2026-10-14

Builds on: FBI and Secret Service: FortiBleed is still active, locks admins out of FortiGates and feeds…

threat16 Oct 04:22Zsingle-sourceOpen finding →

2026-08-15 · view entry permalink →

NOTABLECVE-2026-26035 +3NATOA2

CVE-2026-26035, FortiWeb: one non-default RADIUS admin setting turns any username and password into a valid GUI/CLI login, alongside an FGFM impersonation bug and a FortiClient flaw reachable by anyone who can answer a laptop's DNS

Fortinet issued patches for eight vulnerabilities across its products on 2026-08-12 (SecurityWeek, 2026-08-13). Four of the flaws in that batch matter to a defender's next week. The most consequential is CVE-2026-26035 (CVSS 8.8, CWE-287): where FortiWeb's Remote RADIUS Type Admin authentication is configured with specific, non-default settings, a remote unauthenticated attacker can log into the FortiWeb GUI or CLI with a random username and password (Fortinet PSIRT, 2026-08-12). The setting in question is named in the advisory's own workaround: the Wildcard option on a Remote Type administrator account, reached in the GUI under System > Administrators. The affected branches, read from Fortinet's CSAF record rather than the advisory's rendered table, are FortiWeb 8.0.0 through 8.0.2, 7.6.0 through 7.6.6, 7.4.0 through 7.4.11, 7.2.0 through 7.2.12 and 7.0.0 through 7.0.12. Released fixes exist for three of those five: 8.0.3, 7.6.7 and 7.4.12. The 7.2 and 7.0 branches are answered only by builds the record marks as upcoming (7.2.13 and 7.0.13) so an estate on either has no patch to install today and the Wildcard configuration check is its whole remediation.

CVE-2026-70468 (CVSS 7.3, CWE-288) is the management-plane counterpart: a remote unauthenticated attacker holding a valid certificate can impersonate any FortiGate managed by a FortiManager that has a specific CLI option set, via crafted FGFM protocol requests (Fortinet PSIRT, 2026-08-12). The option is fgfm-peercert-withoutsn, and disabling it is the vendor's stated workaround. Affected are FortiManager 7.6.1, 7.4.3 through 7.4.5 and 7.2.5 through 7.2.9 plus the corresponding FortiManager Cloud versions, fixed in 7.6.2, 7.4.6 and 7.2.10; FortiManager 8.0 is listed as not affected. CVE-2026-70466 (CVSS 4.8, CWE-184) is an incomplete list of disallowed inputs in the FortiWeb WAF that lets an unauthenticated attacker bypass policies via specifically crafted requests (Fortinet PSIRT, 2026-08-12), a lower score, but a WAF that can be walked past is a compensating control that has stopped compensating. Its version data is the one to read carefully: 8.0.0 through 8.0.2 are answered by 8.0.3 and 7.6.0 through 7.6.5 by 7.6.6, but the 7.4, 7.2 and 7.0 branches are all listed as affected at every version with no fixed build at all (migration is the only remediation, and Fortinet offers an interim virtual patch, FG-VD-10009598.0day, in FortiWeb signature database update FMWP 26.071) the concrete lever for the three branches with no fixed build.

The fourth flaw in the batch is the one that reaches past the data centre. CVE-2026-70465 (CVSS 7.3, CWE-120) is a buffer copy without checking the size of input in FortiClient for Windows that "may allow an unauthenticated attacker in a position to alter or craft DNS responses to the targeted host to execute arbitrary code via malicious packets" (Fortinet PSIRT, 2026-08-12). The precondition is not a credential but a network position: anyone able to answer the endpoint's DNS queries (a hostile or compromised local network, a captive portal, an on-path attacker upstream of a home or hotel connection) can reach the code path. That is precisely the position a remote-working laptop puts itself in every time it joins an untrusted network before the VPN comes up, which makes this a teleworker-fleet problem rather than a server-patching one. FortiClient for Windows 7.4.0 through 7.4.3 upgrade to 7.4.4 and 7.2.0 through 7.2.11 upgrade to 7.2.12; the 8.0 branch is not affected. Fortinet's stated workaround is to disable application-based filtering in the FortiClient EMS remote-access profile's VPN tunnel settings. SecurityWeek notes Fortinet makes no mention of any of these vulnerabilities being exploited in the wild (SecurityWeek, 2026-08-13).

None of them is reported exploited: SecurityWeek records that Fortinet makes no mention of any of these vulnerabilities being exploited in the wild. What lifts them above the ordinary patch queue is that two of them are configuration-gated, which cuts both ways: an estate that never enabled the Wildcard option or fgfm-peercert-withoutsn is not exposed at all and needs only a routine upgrade, while one that did is exposed right now and can close the hole today with a settings change rather than a maintenance window. That makes the first task an inventory question, not a patching question, and it is answerable in minutes across a fleet. The certificate precondition on the FortiManager bug is worth reading precisely: it does not say a certificate issued to the impersonated FortiGate, and the advisory's own framing is an alternate-path authentication bypass, so a defender should treat any valid certificate the deployment would accept as sufficient rather than assuming device-specific binding.

Detection concepts, telemetry class first: in administrative authentication logs on FortiWeb, a successful GUI or CLI admin login for a username that does not exist in the backing RADIUS directory is the signature of this bypass being used, the login succeeds locally, so the discriminator is the mismatch between the accepted account and the identity store that was supposed to authorise it. In management-fabric telemetry on FortiManager, watch for FGFM session establishment from a source presenting a certificate whose subject does not correspond to the device serial the session claims, and for a managed FortiGate appearing to check in from an unexpected address or twice from different sources. Fortinet edge and management products have a sustained recent history of rapid post-disclosure weaponisation (this pipeline recorded a Gunra ransomware campaign abusing older FortiOS authentication-bypass flaws for initial access four days ago) so the interval between a published advisory and a working exploit is the planning assumption here, not the absence of exploitation today.

An Improper Authentication vulnerability [CWE-287] in the FortiWeb Remote Radius Type Admin Authentication configured with specific, non-default settings may allow a remote unauthenticated attacker to login into the Fortiweb GUI/CLI with a random username and password

Fortinet PSIRT, FG-IR-26-158 2026-08-12

An Authentication Bypass Using an Alternate Path or Channel [CWE-288] vulnerability in FortiManager and FortiManager Cloud may allow a remote unauthenticated attacker to impersonate any FortiGate managed by the FortiManager with a specific CLI option set via crafted FGFM requests if the attacker has a valid certificate.

Fortinet PSIRT, FG-IR-26-160 2026-08-12

A buffer copy without checking size of input vulnerability [CWE-120] in FortiClient Windows may allow an unauthenticated attacker in a position to alter or craft DNS responses to the targeted host to execute arbitrary code via malicious packets.

Fortinet PSIRT, FG-IR-26-156 2026-08-12
vulnerability15 Aug 04:56Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1
  • Threats1

Source distribution

  • fortiguard.com4 (50%)
  • fortiguard.fortinet.com2 (25%)
  • securityweek.com1 (12%)
  • unit42.paloaltonetworks.com1 (12%)