dbcve.org
FortisaseApplication · Fortinet

CVE-2025-24471

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 7.4.8 / 7.6.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Certificate Validation vulnerability [CWE-295] in FortiOS version 7.6.1 and below, version 7.4.7 and below may allow an EAP verified remote user to connect from FortiClient via revoked certificate.

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 · high confidence

This is an Improper Certificate Validation (CWE-295) vulnerability in FortiOS where the system fails to properly check certificate revocation status during EAP authentication. An attacker possessing a revoked certificate can successfully authenticate through FortiClient, bypassing the revocation check that should deny access.

MitigationUpgrade FortiOS to version 7.4.8 or 7.6.2 or later to address the certificate validation flaw. Verify that CRL/OCSP checking is properly enabled in the configuration.

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
FortisaseApplication
Affected:= 25.1.39
FortiosOperating system
Affected:>= 7.4.0, < 7.4.8>= 7.6.0, < 7.6.2

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Check FortiOS version
    Run 'get system status' or 'fnsysctl get system status' via CLI to retrieve the installed FortiOS version
    Affected if Version is 7.4.0 through 7.4.7, or 7.6.0 through 7.6.1, or the FortiSASE version is exactly 25.1.39
  2. Identify EAP authentication configuration
    Run 'get vpn ssl settings' and look for 'eap-auth' or related EAP settings in the SSL-VPN configuration
    Affected if EAP authentication is enabled for SSL-VPN or certificate-based authentication is in use
  3. Verify certificate revocation checking is configured
    Run 'get vpn certificate setting' to examine CRL and OCSP configuration options, and check if 'revocation-check' is set to a valid method (crl, ocsp, or both)
    Affected if CRL/OCSP revocation checking is disabled, not configured, or set to 'none' for the SSL-VPN or EAP authentication context

You are affected if your FortiOS version falls within the vulnerable ranges AND EAP or certificate-based authentication is enabled with revocation checking disabled or improperly configured.

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.4.8 / 7.6.2 or later
Fixed in 7.4.87.6.2
Interim mitigation

Upgrade FortiOS to version 7.4.8 or 7.6.2 or later to address the certificate validation flaw. Verify that CRL/OCSP checking is properly enabled in the configuration.

Recommended fix High confidence

FortiOS 7.4.8+ or FortiOS 7.6.2+

  1. 1. Identify current FortiOS version via FortiGate web UI (System > Firmware) or CLI (get system status)
  2. 2. For FortiOS 7.4.x: Plan upgrade to version 7.4.8 or later (7.4.8+ contains the fix)
  3. 3. For FortiOS 7.6.x: Plan upgrade to version 7.6.2 or later (7.6.2+ contains the fix)
  4. 4. Download the appropriate firmware from Fortinet Customer Support portal
  5. 5. Back up the current FortiGate configuration
  6. 6. Upload and install the new firmware via web UI or CLI (execute firmware upgrade)
  7. 7. After reboot, verify the new version is running: get system status
  8. 8. Test FortiClient VPN connections to confirm functionality
Caveat Review Fortinet release notes for 7.4.8 and 7.6.2 for any configuration or behavioral changes; always test in non-production first

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

Fix this in Fortisase Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24471 — 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-24471 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