CVE-2025-68686 — Fortios
MEDIUMCVE-2025-68686 is a medium-severity (CVSS 5.9) Information Exposure vulnerability in fortinet fortios. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-07-27) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
An Exposure of Sensitive Information to an Unauthorized Actor vulnerability [CWE-200] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.1, FortiOS 7.4.0 through 7.4.6, FortiOS 7.2…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-07-27. Federal agencies were required to remediate by 2026-08-10.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-68686.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-68686 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,189 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
An Exposure of Sensitive Information to an Unauthorized Actor vulnerability [CWE-200] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.1, FortiOS 7.4.0 through 7.4.6, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions 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.
Affected Products
fortiosfortinetDetection & mitigation playbook
Vendor / applianceDetect
Inventory every fortinet fortios deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2025-68686 yet — track the fortinet fortios advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2025-68686 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.