Live › vulnerability › CVE-2025-68686
Go to dashboardFortiOS SSL-VPN symlink persistence patch bypass (CWE-200). The April 2025 patch checked for the substring /lang/custom, so requesting /lang//custom skips the check and serves the root filesystem read-only through a symlink an attacker already planted. It is only abusable on devices already compromised through another bug. Devices that never had SSL-VPN enabled are not affected. Fixed in 7.4.7 and 7.6.2; 7.2, 7.0 and 6.4 have no fix and need migrating. A public PoC and checker exist.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| FortiOS | vendor | >= 7.6.0, <= 7.6.1; >= 7.4.0, <= 7.4.6; 7.2 all; 7.0 all; 6.4 all | 7.4.7, 7.6.2 |
| fortinet fortios | vendor | >= 6.4.0, < 7.4.7 | 7.4.7 |
| fortinet fortios | vendor | >= 7.6.0, < 7.6.2 | 7.6.2 |
| Fortinet FortiOS | vendor | – |
| – |
7.4.7 or later and 7.6 to 7.6.2 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Fortinet FortiOS contains an exposure of sensitive information to an unauthorized actor vulnerability. This may allow a remote unauthenticated attacker to bypass the patch developed for the symbolic link persistency mechanism observed in some post-exploit cases, via crafted HTTP requests. An attacker would need first to have compromised the product via another vulnerability, at filesystem level.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
This page as .md · .json · in your agent: get_signal("CVE-2025-68686")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.