Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Exposed IOCTL with Insufficient Access Control in FortiClient Windows fortips driver

IdentifiersCVE-2025-47761CWE-782· Exposed IOCTL with Insufficient…

CVE-2025-47761 is an exposed IOCTL with insufficient access control vulnerability in Fortinet FortiClient Windows affecting versions 7.4.0 through 7.4.3 and 7.2.0 through 7.2.9. The flaw is in the fortips driver, which exposes IOCTL functionality to an authenticated local user without sufficient access restrictions. Under the required conditions, a local attacker can abuse the driver interface to execute unauthorized code. The vendor notes that successful exploitation also requires bypassing Windows memory protections such as heap integrity and HSP, and that a valid, active VPN IPSec connection must be present.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow an authenticated local user to execute unauthorized code or commands via the vulnerable fortips driver. This can lead to local privilege escalation and broader system compromise, including the ability to run attacker-controlled actions in a more privileged context on the affected Windows host.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict local access to trusted users only, monitor affected endpoints for suspicious local activity involving FortiClient and the fortips driver, and limit or disable VPN IPSec functionality where operationally feasible. Because exploitation requires a valid running VPN IPSec connection, reducing exposure of that feature can lower risk until upgrades are completed.

Remediation

Patch, then assume compromise.

Upgrade FortiClient Windows to a fixed release. Fortinet advises upgrading to version 7.4.4 or later for the 7.4 branch, or 7.2.10 or later for the 7.2 branch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetForticlientapplication
FortinetForticlientwindowsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.