What is CVE-2025-68686?

CVE-2025-68686 is Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability. The supplied enrichment data classifies it as Info Disclosure mapped to CWE-200 Exposure of Sensitive Information.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

8 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-68686 using CVSS 5.9, EPSS 29%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVmediumInfo Disclosurepublic exploit

CVE-2025-68686

CVE-2025-68686 — Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-68686 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Feb 10, 2026Updated Jul 28, 2026Sources: NVD, Fortinet (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jul 27, 2026

EPSS

29%

ahead of 98% of scored CVEs

Affects

Fortinet

5 products listed

CVSS base

5.9

medium · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade to FortiOS version 7.6.2 or above Upgrade to FortiOS version 7.4.7 or above

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.

Federal deadline Aug 10, 2026 — passed 35 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Fortinet	FortiOS	7.6.0 to <= 7.6.1	Vulnerable
Fortinet	FortiOS	7.4.0 to <= 7.4.6	Vulnerable
Fortinet	FortiOS	7.2.0 to <= 7.2.13	Vulnerable
Fortinet	FortiOS	7.0.0 to <= 7.0.19	Vulnerable
Fortinet	FortiOS	6.4.0 to <= 6.4.16	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
5.9	CVSS 3.1	medium	2.2	3.6	Fortinet (CNA)
5.3	CVSS 3.1	medium	—	—	Fortinet (CNA)

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

Read Application Data::

Mitigation: Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.::

Weakness & attack patterns

CWE-200Exposure of Sensitive Information

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-116 · ExcavationCAPEC-285 · ICMP Echo Request PingCAPEC-287 · TCP SYN ScanCAPEC-13 · Subverting Environment Variable ValuesCAPEC-302 · TCP FIN ScanCAPEC-303 · TCP Xmas ScanCAPEC-169 · FootprintingCAPEC-304 · TCP Null ScanCAPEC-318 · IP 'ID' Echoed Byte-Order ProbeCAPEC-319 · IP (DF) 'Don't Fragment Bit' Echoing ProbeCAPEC-328 · TCP 'RST' Flag Checksum ProbeCAPEC-326 · TCP Initial Window Size Probe

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jul 27, 2026

Federal deadline

Aug 10, 2026

passed 35 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

17 more posts on this CVEShowing 5 of 22 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable FortiOS.
Monitor for scanner or exploit-pattern traffic after 8 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

ip206.72.242.16284
AbuseIPDB Hourly Update · Sep 19, 2024
ip8.19.75.21784
CINSscore · Apr 19, 2026
ip206.72.242.12481
AlienVault OTX Feeds · Sep 21, 2024

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 5.9 (AV:N)
Jul 28, 2026 · NVD
Added to CISA KEV catalog
Jul 27, 2026 · CISA
Initial · CVE published
Feb 10, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

15×SvrsFeb 11, 2026 – Aug 28, 2026 · SOCRadar CTI
8×TweetsFeb 11, 2026 – Aug 11, 2026 · SOCRadar CTI
4×ModifiedFeb 10, 2026 – Jul 28, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jul 28, 2026 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelFeb 13, 2026 · SOCRadar CTI

References

5 on the record

fortiguard.fortinet.com/psirt/FG-IR-25-934
Vendor Advisory, NIST, Mitre
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-68686
US Government Resource, NIST
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2025-68686
Vendor Advisory

Coverage

9 stories from the feeds we poll

4 more reports on this CVEShowing 5 of 9 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Fortinetevery CVE for this vendor
July 2026what else CISA listed
Info Disclosuresame class
CWE-200other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 3 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-68686 is Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability, a medium vulnerability affecting FortiOS from Fortinet. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 8 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 5.9 describes technical severity, while EPSS 29% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.