On October 16, 2026, CISA added two vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog based on evidence of active exploitation: CVE-2025-61624, a path traversal vulnerability affecting multiple Fortinet products, and CVE-2026-102764, an authentication bypass via spoofing in BeyondTrust Remote Support. Both product families sit at exactly the wrong place in your architecture to have an exploitable bug: Fortinet appliances are perimeter devices with a direct line into internal networks, and BeyondTrust Remote Support is a privileged remote access platform that, by design, holds the keys to administer endpoints across the enterprise.
Inclusion in the KEV Catalog is not advisory — it is confirmation that threat actors are using these flaws in live intrusions. Under Binding Operational Directive (BOD) 26-04, Federal Civilian Executive Branch (FCEB) agencies are mandated to remediate KEV-listed vulnerabilities on accelerated timelines. For private-sector organizations, the KEV due date is the closest thing we have to an authoritative "patch this first" signal. If you run Fortinet edge devices or BeyondTrust Remote Support in any capacity, treat this as an incident, not a ticket.
Technical Analysis
CVE-2025-61624 — Fortinet Multiple Products Path Traversal
Path traversal (CWE-22) in a Fortinet product means an attacker can supply crafted path sequences — typically ../ or URL-encoded variants such as %2e%2e%2f and double-encoded forms like %252e%252e%252f — to escape the intended web root or API scope and read or interact with files outside the authorized directory. On Fortinet appliances, the high-value targets are well understood from prior exploitation patterns against this vendor: configuration files containing hashed and sometimes plaintext credentials, session tokens, administrative cookies, and VPN authentication data.
Key defensive characteristics of this class of bug:
- Affected component: web management / API interface exposed on Fortinet appliances. Management interfaces that are internet-reachable are the highest-risk exposure.
- Exploitation requirements: typically unauthenticated or low-authentication HTTP(S) requests to specific endpoints with traversal sequences in path or parameter values. No user interaction required.
- Impact: disclosure of sensitive files from the appliance filesystem, which frequently becomes the stepping stone to full administrative compromise, VPN session hijacking, and lateral movement into the internal network.
- Exploitation status: confirmed active exploitation — this is why it is in the KEV Catalog. Assume internet-facing, unpatched appliances have already been probed.
CVE-2026-102764 — BeyondTrust Remote Support Authentication Bypass by Spoofing
An authentication bypass by spoofing (CWE-290 family — authentication relying on untrusted/spoofable attributes) means the product makes an access decision based on something an attacker can forge — for example, a header value, token claim, or client-supplied identity attribute that is not cryptographically verified. The practical result: an attacker can impersonate a legitimate user or privileged session and gain access to the Remote Support platform without valid credentials.
Why this is severe in a BeyondTrust context:
- BeyondTrust Remote Support brokers privileged remote sessions to endpoints. A successful bypass hands the attacker a sanctioned remote access channel — no malware deployment needed for initial hands-on-keyboard access.
- Session artifacts (jump items, session keys, representative consoles) become attacker infrastructure. Activity can blend into legitimate administrative traffic, which is precisely why detection has to focus on anomalies around authentication and session establishment, not just signatures.
- Exploitation status: confirmed active exploitation per CISA KEV.
Common Thread
Both vulnerabilities target edge and remote access infrastructure — the exact product categories that have dominated initial-access vectors in ransomware and espionage campaigns over the last several years. If you only have bandwidth for two emergency changes this week, these are the two.
Detection & Response
Detection for these CVEs lives primarily in web access logs, VPN/security appliance logs, and identity/session telemetry. Hunt retroactively — exploitation predates today's KEV publication.
Sigma Rules
---
title: Path Traversal Attempt Against Fortinet Management Interface
id: 3f8c1a92-6d47-4e5b-9a21-c7e4f0b2d8a1
status: experimental
description: Detects path traversal sequences in HTTP requests targeting Fortinet appliance management and API endpoints, consistent with exploitation of CVE-2025-61624.
references:
- https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-adds-two-known-exploited-vulnerabilities-catalog
- https://attack.mitre.org/techniques/T1190/
author: Security Arsenal
date: 2026/10/16
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
detection:
selection_traversal:
c-uri|contains:
- '../'
- '..%2f'
- '%2e%2e%2f'
- '%2e%2e/'
- '..%252f'
- '%252e%252e'
- '..\\'
selection_sensitive:
c-uri|contains:
- '/etc/'
- 'passwd'
- 'shadow'
- 'forticloud'
- 'vpn'
- '.conf'
- 'sslvpn'
condition: selection_traversal and selection_sensitive
falsepositives:
- Vulnerability scanners and authorized penetration tests
level: high
---
title: HTTP Response Indicating Successful File Read on Fortinet Appliance
id: 8b2e4d61-1f93-4c27-a856-9d3b7e5f2c40
status: experimental
description: Detects successful (200) responses to requests containing encoded traversal sequences against Fortinet-hosted endpoints, indicating possible successful exploitation of CVE-2025-61624 rather than mere scanning.
references:
- https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-adds-two-known-exploited-vulnerabilities-catalog
author: Security Arsenal
date: 2026/10/16
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
detection:
selection:
c-uri|contains:
- '%2e%2e'
- '..%2f'
- '%252e%252e'
sc-status: 200
condition: selection
falsepositives:
- Authorized scanning activity; correlate with scanner source IPs
level: critical
---
title: Anomalous BeyondTrust Remote Support Session Establishment
id: 5c7a9f13-2e68-4d41-b037-6f1a8c3d9e52
status: experimental
description: Detects suspicious patterns in BeyondTrust Remote Support authentication and session logs potentially consistent with CVE-2026-102764 spoofing-based authentication bypass, including sessions without preceding successful authentication events.
references:
- https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-adds-two-known-exploited-vulnerabilities-catalog
- https://attack.mitre.org/techniques/T1078/
author: Security Arsenal
date: 2026/10/16
tags:
- attack.persistence
- attack.initial_access
- attack.t1078
logsource:
category: application
product: beyondtrust
detection:
selection:
EventType|contains:
- 'session_start'
- 'representative_login'
- 'jump_item_access'
AuthResult:
- 'bypassed'
- 'spoofed'
- 'unverified'
condition: selection
falsepositives:
- Misconfigured integrations; validate against change records
level: high
KQL — Microsoft Sentinel / Defender
Hunt retroactively across proxy, firewall, and Syslog/CEF-ingested appliance logs for traversal patterns and anomalous BeyondTrust session behavior:
// Hunt 1: Path traversal attempts targeting Fortinet appliances (proxy/WAF logs + CEF-ingested syslog)
let lookback = 30d;
let traversal = dynamic(["../", "..%2f", "%2e%2e%2f", "%252e%252e", "..%5c", "..\\"]);
CommonSecurityLog
| where TimeGenerated > ago(lookback)
| where DeviceVendor =~ "Fortinet" or RequestURL has_any (traversal)
| where RequestURL has_any (traversal)
| extend EncodedTraversal = RequestURL matches regex @"(%25)?2e(%25)?2e"
| summarize AttemptCount = count(), DistinctTargets = dcount(DestinationIP), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated)
by SourceIP, RequestURL, DeviceAction, ApplicationProtocol
| where AttemptCount > 2 or EncodedTraversal
| order by LastSeen desc;
// Hunt 2: BeyondTrust Remote Support sessions without a preceding successful authentication
// Ingest BeyondTrust syslog via the Syslog or CommonSecurityLog connector
let lookback = 14d;
Syslog
| where TimeGenerated > ago(lookback)
| where ProcessName has_any ("beyondtrust", "bomgar") or SyslogMessage has "Remote Support"
| where SyslogMessage has_any ("session started", "jump item", "representative")
| extend SessionUser = extract(@"user[=:]?(\S+)", 1, SyslogMessage)
| extend SrcIP = extract(@"(src|source)[=:]?(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})", 2, SyslogMessage)
| summarize Sessions = count(), FirstSession = min(TimeGenerated), LastSession = max(TimeGenerated)
by SessionUser, SrcIP
| join kind=leftanti (
Syslog
| where TimeGenerated > ago(lookback)
| where SyslogMessage has_any ("authentication successful", "login successful")
| extend AuthUser = extract(@"user[=:]?(\S+)", 1, SyslogMessage)
| summarize by AuthUser
) on $left.SessionUser == $right.AuthUser
| project SessionUser, SrcIP, Sessions, FirstSession, LastSession
| order by Sessions desc;
Velociraptor VQL
For BeyondTrust jump hosts and representative consoles on Windows endpoints, hunt for anomalous process lineage and unexpected outbound connections from the BeyondTrust client components:
-- Hunt for BeyondTrust Remote Support client processes spawning unexpected children
-- (post-exploitation via a hijacked privileged remote session)
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Name =~ '(?i)bomgar|beyondtrust|srs-|jumpclient'
OR (SELECT Name FROM pslist() WHERE Pid = Ppid) =~ '(?i)bomgar|beyondtrust'
-- Correlate: unexpected outbound connections from remote-support tooling
SELECT Pid, Name, RemoteIP, RemotePort, Status
FROM netstat()
WHERE Name =~ '(?i)bomgar|beyondtrust'
AND RemoteIP !~ '^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[01])\.)'
AND Status =~ 'ESTAB'
Remediation & Verification Script
Use the following to inventory exposed management interfaces and verify BeyondTrust/Fortinet exposure posture. Run from an administrative jump box:
#!/bin/bash
# CVE-2025-61624 / CVE-2026-102764 exposure verification
# 1) Enumerate internet-facing Fortinet management interfaces from your external attack surface inventory
# Replace targets.txt with your appliance list (one host:port per line)
while read -r target; do
echo "=== Testing $target for traversal exposure (CVE-2025-61624) ==="
# Benign probe: request a traversal path and check whether the appliance returns file content
response=$(curl -sk -o /dev/null -w "%{http_code}" --max-time 10 \
"https://$target/..%2f..%2f..%2fetc%2fpasswd")
echo "HTTP status: $response"
if [ "$response" == "200" ]; then
echo "[ALERT] $target returned 200 on traversal probe — investigate immediately"
fi
done < targets.txt
# 2) Check FortiOS firmware version against vendor advisory (run on the appliance via CLI)
# ssh admin@<fortigate> 'get system status | grep Version'
# Compare against fixed versions listed at https://www.fortiguard.com/psirt
# 3) Verify BeyondTrust Remote Support site version
# Log into /appliance and check the version string against the fixed build in the
# BeyondTrust advisory: https://www.beyondtrust.com/trust-center/security-advisories
# Inventory BeyondTrust Remote Support client deployments and check versions across Windows endpoints
$computers = Get-ADComputer -Filter * -Properties OperatingSystem |
Where-Object {$_.OperatingSystem -like "*Windows*"} | Select-Object -ExpandProperty Name
foreach ($c in $computers) {
try {
$sw = Invoke-Command -ComputerName $c -ErrorAction Stop -ScriptBlock {
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
"HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" -ErrorAction SilentlyContinue |
Where-Object {$_.DisplayName -match "BeyondTrust|Bomgar"} |
Select-Object DisplayName, DisplayVersion
}
if ($sw) { [PSCustomObject]@{Computer=$c; Product=$sw.DisplayName; Version=$sw.DisplayVersion} }
} catch { Write-Warning "Unreachable: $c" }
}
# Export and reconcile against the fixed version in the BeyondTrust advisory; flag anything older.
Remediation
- Patch immediately — treat as emergency change. Apply the fixed Fortinet firmware builds specified in the Fortinet PSIRT advisory (https://www.fortiguard.com/psirt) for every product in scope of CVE-2025-61624, and the fixed BeyondTrust Remote Support build from the BeyondTrust Trust Center advisory (https://www.beyondtrust.com/trust-center/security-advisories). Follow CISA KEV remediation due dates — for FCEB agencies these are binding under BOD 26-04; for everyone else they are the de facto SLA.
- Remove management interfaces from the internet. Fortinet administrative and API interfaces must never be internet-reachable. Restrict to dedicated management networks with ACLs and VPN/bastion access. Validate with external scanning — don't trust your own firewall rules.
- Hunt before you patch. Pull 30–90 days of web/proxy/appliance logs and run the queries above. KEV inclusion means exploitation predates the patch. If you find traversal requests with 200 responses, or BeyondTrust sessions without matching authentication events, open an incident: rotate all credentials stored on or transiting the appliance (VPN users, local admins, API keys, LDAP binds), review session recordings, and inspect endpoints accessed via BeyondTrust for persistence.
- Rotate credentials as a precaution on internet-exposed appliances even absent confirmed compromise — path traversal against Fortinet devices has historically been used to harvest credentials that enable follow-on access.
- Tighten BeyondTrust controls. Enforce MFA on all representative accounts, restrict login source networks, enable and review session recording, and alert on any session initiated outside maintenance windows.
- Operationalize the KEV feed. Subscribe to the CISA KEV Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) and wire it into your vulnerability management workflow with SLA tiers that override CVSS-based prioritization — exploited beats theoretical, every time.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.