dbcve.org
ForticlientApplication · Fortinet

CVE-2025-46774

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 7.2.10 / 7.4.4 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Improper Verification of Cryptographic Signature vulnerability [CWE-347] in FortiClient MacOS installer version 7.4.2 and below, version 7.2.9 and below, 7.0 all versions may allow a local user to escalate their privileges via FortiClient related executables.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

FortiClient MacOS installer versions 7.4.2 and below, 7.2.9 and below, and 7.0 all versions contain an improper cryptographic signature verification vulnerability (CWE-347) that allows a local unprivileged user to escalate privileges by manipulating FortiClient related executables.

MitigationUpgrade FortiClient MacOS installer to a patched version beyond 7.4.2, 7.2.9, or 7.0 as specified in Fortinet's security advisory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ForticlientApplication
Affected:>= 7.0.0, < 7.2.10>= 7.4.0, < 7.4.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify FortiClient is installed on the Mac
    Check if /Applications/FortiClient.app exists. You can use Finder or run: ls -la /Applications/ | grep -i forticlient
    Affected if FortiClient is not installed on the system
  2. Determine the installed FortiClient version
    Run: defaults read "/Applications/FortiClient.app/Contents/Info.plist" CFBundleShortVersionString or view the Info.plist file and locate CFBundleShortVersionString
    Affected if Unable to read the version information from the FortiClient application bundle
  3. Compare your version against the affected ranges
    Check if your installed version falls into: 7.0.x (any 7.0.x), 7.2.x where x is 0-9 (less than 7.2.10), or 7.4.x where x is 0-2 (less than 7.4.4). The affected ranges are: >= 7.0.0, < 7.2.10 OR >= 7.4.0, < 7.4.4
    Affected if Your FortiClient version is 7.0.x, 7.2.0 through 7.2.9, or 7.4.0 through 7.4.2

You are affected if FortiClient for MacOS is installed and its version is 7.0.x, 7.2.x below 7.2.10, or 7.4.x below 7.4.4.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.2.10 / 7.4.4 or later
Fixed in 7.2.107.4.4
Interim mitigation

Upgrade FortiClient MacOS installer to a patched version beyond 7.4.2, 7.2.9, or 7.0 as specified in Fortinet's security advisory.

Recommended fix High confidence

FortiClient 7.2.10 or later for 7.2.x branch; FortiClient 7.4.4 or later for 7.4.x branch (7.0.x is end-of-life)

  1. 1. Identify the currently installed FortiClient version on the MacOS system
  2. 2. If running FortiClient 7.0.x, note that this version line is end-of-life and requires migration to a supported version branch
  3. 3. If running FortiClient 7.2.x, upgrade to version 7.2.10 or later
  4. 4. If running FortiClient 7.4.x, upgrade to version 7.4.4 or later
  5. 5. Download the updated FortiClient installer from the official Fortinet support portal (support.fortinet.com) or FortiGuard
  6. 6. Uninstall the current FortiClient version following Fortinet's documented removal procedures
  7. 7. Install the upgraded FortiClient version
  8. 8. Verify the signature verification vulnerability is resolved by confirming the installed version
Caveat Users on FortiClient 7.0.x must migrate to 7.2.x or 7.4.x as 7.0.x is end-of-life with no patch available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Forticlient Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46774 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data