CVE-2025-68686

FortiOS is the operating system inside FortiGate security appliances—the equipment many organizations place at the edge of their networks to control firewall policy, VPN access, routing, administration, logging, and trusted connections. CVE-2025-68686 matters because it affects the trustworthiness of that control plane after a deeper compromise has already occurred. ^[1][3][4]

Fortinet says another vulnerability must first let the attacker compromise the FortiOS filesystem. The attacker can then send crafted HTTP requests, without authenticating for this later step, to bypass an earlier patch for a symbolic-link persistence mechanism. In ordinary language: this is not the first door into the appliance; it is a way to defeat an attempted cleanup and preserve attacker-relevant state.^[1][3][4]

This CVE Watch Brief tracks authoritative changes to exploitation status, affected versions, fixed releases, severity, weakness classification, and response requirements. CISA added the CVE to KEV on 27 July 2026 and set a 10 August federal required-action date.^[2][5][6]

The public record does not identify the earlier vulnerability, actor, victims, victim count, or ransomware outcome. The product therefore keeps four states separate: an affected product, an exposed asset, suspicious local evidence, and a confirmed incident.

FortiGate appliances often sit at the boundary between an organization and the internet. They can terminate VPN connections, enforce network policy, route traffic, hold certificates and credentials, and expose an administrative control plane. A persistent attacker on that device may therefore have a better position than an attacker on an ordinary endpoint: the appliance can see trusted traffic and may connect directly to sensitive internal systems.

CVE-2025-68686 does not describe the original break-in. Fortinet says a separate vulnerability must first allow an attacker to compromise FortiOS at filesystem level. In some post-exploitation cases, attackers used symbolic links—a filesystem mechanism that points one file location to another—as part of persistence. This CVE allows crafted HTTP requests to bypass Fortinet’s earlier patch for that persistence mechanism. Put simply: the attacker must already be inside, but may be able to defeat the owner’s attempt to remove the foothold. ^[1][3][4]

The formal CVSS 3.1 score is 5.9 Medium. Its vector—AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N—says the attack is reachable over a network, needs no authenticated account or user click, but has high complexity because the filesystem must already be compromised. The rated impact is High for confidentiality and None for integrity and availability. That score describes the CVE in isolation. It should not be used to downgrade a real appliance investigation when the prerequisite itself means an attacker may already have achieved privileged access. ^[1][3][4]

Fortinet assigns CWE-200, “Exposure of Sensitive Information to an Unauthorized Actor.” In practical terms, the documented consequence is that information the attacker should not be able to obtain may remain exposed. MITRE labels CWE-200 a broad category and discourages using it as a precise root-cause mapping. The responsible reading is therefore: CWE-200 describes the confidentiality consequence in the vendor record; it does not tell us exactly which data was taken, name the underlying initial-access bug, or fully explain the symbolic-link patch bypass. ^[1][3][7]

On 27 July, CISA moved the CVE into the Known Exploited Vulnerabilities Catalog. That turns a theoretical product risk into a known-exploitation response problem and sets a 10 August required-action date for federal civilian agencies. CISA also points to forensic-triage requirements. For other organizations, the deadline is not automatically binding, but the underlying signal is still important: exploitation has been observed and an exposed affected device deserves a short, owned response window.^[2][5][6]

Owners should identify every affected appliance, restrict exposed administration, preserve evidence, upgrade to 7.6.2+ or 7.4.7+, and investigate historical access. Older 7.2, 7.0, and 6.4 branches remain listed as affected without a fixed release in the CNA solution field; remaining on the newest build of one of those branches is not a documented fix.^[1][4]

The practical closure question is not merely “Did the version number change?” Forensic triage should focus on unexpected symbolic links and filesystem changes, administrative and authentication activity, configuration drift, account and session changes, process or service changes, network egress, and evidence from both members of an HA pair. If integrity cannot be established, restore from trusted media and a validated configuration rather than declaring the incident closed because the version number changed. ^[2][6]

The public record remains narrow. It does not identify the prerequisite vulnerability, actor, victim, victim count, or ransomware outcome. CISA’s Unknown ransomware field is an unconfirmed relationship, not reassurance. Executive reporting should say “known exploitation of a post-compromise persistence bypass” and keep local exposure, compromise, attribution, and business impact separate. ^[2]