⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.7

How to Fix CVE-2026-23708: Authentication bypass in FortiSOAR PaaS

By Sai Kiran Pandrala. Last verified: 2026-05-25.

⚡ At a glance
Severity6.7 (Medium)
Actively exploited?No public listing in CISA KEV
AffectedFortinet FortiSOAR PaaS 7.6.0 to <7.6.3, 7.5.0 to <7.5.2; Fortinet FortiSOAR on-premise 7.6.0 to <7.6.3, 7.5.0 to <7.5.2
Fixed inFortiSOAR PaaS 7.6.3; FortiSOAR PaaS 7.5.2; FortiSOAR on-premise 7.6.3; FortiSOAR on-premise 7.5.2
Type (CWE)CWE-287: Escalation of privilege

What is CVE-2026-23708?

A improper authentication vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.3, FortiSOAR PaaS 7.5.0 through 7.5.2, FortiSOAR on-premise 7.6.0 through 7.6.3, FortiSOAR on-premise 7.5.0 through 7.5.2 may allow an unauthenticated attacker to bypass authentication via replaying captured 2FA request. The attack requires being able to intercept and decrypt authentication traffic and precise timing to replay the request before token expiration, which raises the attack complexity.

Am I affected?

From the device CLI, run the version check:


# Cisco IOS/IOS XE
show version | include Version

# FortiGate (FortiOS)
get system status

# Palo Alto (PAN-OS)
show system info | match sw-version

# Juniper (Junos)
show version

Compare what you see against the Affected row above (Fortinet FortiSOAR PaaS 7.6.0 to <7.6.3, 7.5.0 to <7.5.2; Fortinet FortiSOAR on-premise 7.6.0 to <7.6.3, 7.5.0 to <7.5.2). If your build sits inside that range, the device is exposed and should be upgraded.

How to fix CVE-2026-23708

The primary fix is to upgrade FortiSOAR PaaS to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: FortiSOAR PaaS 7.6.3; FortiSOAR PaaS 7.5.2; FortiSOAR on-premise 7.6.3; FortiSOAR on-premise 7.5.2.

FortiGate (FortiOS CLI)


# Vendor advisory: https://fortiguard.fortinet.com/psirt/FG-IR-26-101
get system status              # confirm current version
execute backup config tftp <file> <tftp-server>
execute restore image tftp <patched-image>.out <tftp-server>
execute reboot

Complete operator runbook (network appliance)

Run this from your management workstation (Linux/macOS or Windows with a TFTP server reachable). It shells into the device, backs up the running config, transfers the patched image, and reloads.


# Vendor advisory: https://fortiguard.fortinet.com/psirt/FG-IR-26-101
#!/usr/bin/env bash
# CVE-2026-23708 fix runbook for Fortinet FortiSOAR PaaS
# Target build: FortiSOAR PaaS 7.6.3; FortiSOAR PaaS 7.5.2; FortiSOAR on-premise 7.6.3; FortiSOAR on-premise 7.5.2

set -euo pipefail
DEVICE="${1:?usage: $0 <device-ip> <patched-image-file> <tftp-server-ip>}"
IMAGE="${2:?patched image filename required}"
TFTP="${3:?tftp server ip required}"
LOG="/var/log/cve-2026-23708-$(date +%Y%m%d-%H%M%S).log"

echo "[1/4] Pulling current config from $DEVICE"
ssh admin@"$DEVICE" "show version" | tee -a "$LOG"
ssh admin@"$DEVICE" "copy running-config tftp://$TFTP/cve-2026-23708-pre.cfg"

echo "[2/4] Uploading patched image $IMAGE via TFTP"
ssh admin@"$DEVICE" "copy tftp://$TFTP/$IMAGE flash:$IMAGE" | tee -a "$LOG"

echo "[3/4] Setting boot image and reloading"
ssh admin@"$DEVICE" "configure terminal
 boot system flash:$IMAGE
 end
 write memory
 reload" | tee -a "$LOG"

echo "[4/4] Wait ~5 minutes, then verify"
sleep 300
ssh admin@"$DEVICE" "show version | include Version" | tee -a "$LOG"
echo "Compare reported version against FortiSOAR PaaS 7.6.3; FortiSOAR PaaS 7.5.2; FortiSOAR on-premise 7.6.3; FortiSOAR on-premise 7.5.2"

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network appliance ACL


# Cisco IOS example: restrict management plane to a trusted subnet
configure terminal
access-list 99 permit 10.0.0.0 0.255.255.255
line vty 0 15
 access-class 99 in
end
write memory

Service-level fallback


# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop fortisoar
sudo systemctl disable fortisoar

How to verify the fix worked


# Linux
fortisoar --version 2>/dev/null || dpkg -s fortisoar | grep -i version
rpm -q fortisoar 2>/dev/null || true


# Windows
winget list | findstr /I "fortisoar"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above FortiSOAR PaaS 7.6.3; FortiSOAR PaaS 7.5.2; FortiSOAR on-premise 7.6.3; FortiSOAR on-premise 7.5.2. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-23708 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

6.7 (medium). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*