How to Fix CVE-2026-21741: Execute unauthorized code or commands in FortiNAC-F
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 2.2 (Low) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Fortinet FortiNAC-F 7.6.0 to <7.6.5, 7.4.0 to <7.4.3, 7.2.0 to <7.2.9 |
| Fixed in | FortiNAC-F 7.6.5; FortiNAC-F 7.4.3; FortiNAC-F 7.2.9 |
| Type (CWE) | CWE-601: Execute unauthorized code or commands |
What is CVE-2026-21741?
An URL Redirection to Untrusted Site ('Open Redirect') vulnerability [CWE-601] vulnerability in Fortinet FortiNAC-F 7.6.0 through 7.6.5, FortiNAC-F 7.4 all versions, FortiNAC-F 7.2 all versions may allow a remote privileged attacker with system administrator role to redirect users to an arbitrary website via crafted CSV file.
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 FortiNAC-F 7.6.0 to <7.6.5, 7.4.0 to <7.4.3, 7.2.0 to <7.2.9). If your build sits inside that range, the device is exposed and should be upgraded.
How to fix CVE-2026-21741
The primary fix is to upgrade FortiNAC-F to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: FortiNAC-F 7.6.5; FortiNAC-F 7.4.3; FortiNAC-F 7.2.9.
FortiGate (FortiOS CLI)
# Vendor advisory: https://fortiguard.fortinet.com/psirt/FG-IR-26-118
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-118
#!/usr/bin/env bash
# CVE-2026-21741 fix runbook for Fortinet FortiNAC-F
# Target build: FortiNAC-F 7.6.5; FortiNAC-F 7.4.3; FortiNAC-F 7.2.9
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-21741-$(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-21741-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 FortiNAC-F 7.6.5; FortiNAC-F 7.4.3; FortiNAC-F 7.2.9"
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 fortinac
sudo systemctl disable fortinac
How to verify the fix worked
# Linux
fortinac --version 2>/dev/null || dpkg -s fortinac | grep -i version
rpm -q fortinac 2>/dev/null || true
# Windows
winget list | findstr /I "fortinac"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above FortiNAC-F 7.6.5; FortiNAC-F 7.4.3; FortiNAC-F 7.2.9. 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
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-39814: Execute unauthorized code or commands in FortiWeb — Execute unauthorized code or commands in FortiWeb
- How to Fix CVE-2026-24018: Escalation of privilege in FortiClientLinux — Escalation of privilege in FortiClientLinux
- How to Fix CVE-2026-39815: SQL injection in FortiDDoS-F , SQL injection in FortiDDoS-F
- How to Fix CVE-2026-22627: Execute unauthorized code or commands in FortiSwitchAXFixed , Execute unauthorized code or commands in FortiSwitchAXFixed
- How to Fix CVE-2026-25691: Path traversal in FortiSandbox , Path traversal in FortiSandbox
Is CVE-2026-21741 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?
2.2 (low). 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
- Official vendor advisory: https://fortiguard.fortinet.com/psirt/FG-IR-26-118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21741
*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.*