critical
9.8
CWE
306
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2024-26011: FortiOS - Improper authentication in fgfmd

First published: Tue Nov 12 2024(Updated: )

A missing authentication for critical function in Fortinet FortiManager version 7.4.0 through 7.4.2, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.14, FortiPAM version 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiProxy version 7.4.0 through 7.4.2, 7.2.0 through 7.2.9, 7.0.0 through 7.0.17, 2.0.0 through 2.0.14, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7, FortiSwitchManager version 7.2.0 through 7.2.3, 7.0.0 through 7.0.3, FortiPortal version 6.0.0 through 6.0.14, FortiOS version 7.4.0 through 7.4.3, 7.2.0 through 7.2.7, 7.0.0 through 7.0.14, 6.4.0 through 6.4.15, 6.2.0 through 6.2.16, 6.0.0 through 6.0.18 allows attacker to execute unauthorized code or commands via specially crafted packets.

Credit: psirt@fortinet.com

Affected SoftwareAffected VersionHow to fix
Fortinet FortiManager>=7.4.0<=7.4.2
Fortinet FortiManager>=7.2.0<=7.2.4
Fortinet FortiManager>=7.0.0<=7.0.11
Fortinet FortiManager>=6.4.0<=6.4.14
FortiOS>=7.4.0<=7.4.3
FortiOS>=7.2.0<=7.2.7
FortiOS>=7.0.0<=7.0.14
FortiOS>=6.4
FortiOS>=6.2
FortiOS>=6.0
FortiGuard FortiPAM>=1.2
FortiGuard FortiPAM>=1.1
FortiGuard FortiPAM>=1.0
Fortinet FortiPortal>=6.0.0<=6.0.14
Fortinet FortiPortal>=5.3
Fortinet FortiProxy>=7.4.0<=7.4.3
Fortinet FortiProxy>=7.2.0<=7.2.9
Fortinet FortiProxy>=7.0.0<=7.0.16
Fortinet FortiProxy>=2.0
Fortinet FortiProxy>=1.2
Fortinet FortiProxy>=1.1
Fortinet FortiProxy>=1.0
Fortinet FortiSwitchManager>=7.2.0<=7.2.3
Fortinet FortiSwitchManager>=7.0.0<=7.0.3
FortiOS>=6.0.0<7.0.15
FortiOS>=7.2.0<7.2.8
FortiOS>=7.4.0<7.4.4
FortiGuard FortiPAM>=1.0.0<1.3.0
Fortinet FortiProxy>=1.0.0<7.0.17
Fortinet FortiProxy>=7.2.0<7.2.10
Fortinet FortiProxy>=7.4.0<7.4.4
Fortinet FortiManager>=6.4.0<6.4.15
Fortinet FortiManager>=7.0.0<7.0.12
Fortinet FortiManager>=7.2.0<7.2.5
Fortinet FortiManager>=7.4.0<7.4.3
Fortinet FortiSwitchManager>=7.0.0<7.0.4
Fortinet FortiSwitchManager>=7.2.0<7.2.4
Fortinet FortiPortal>=5.3.0<6.0.15

Remedy

Please upgrade to FortiManager version 7.4.3 or above Please upgrade to FortiManager version 7.2.5 or above Please upgrade to FortiManager version 7.0.12 or above Please upgrade to FortiManager version 6.4.15 or above Please upgrade to FortiVoice version 7.0.2 or above Please upgrade to FortiVoice version 6.4.9 or above Please upgrade to FortiSwitchManager version 7.2.4 or above Please upgrade to FortiSwitchManager version 7.0.4 or above Please upgrade to FortiWeb version 7.6.0 or above Please upgrade to FortiWeb version 7.4.3 or above Please upgrade to FortiPAM version 1.3.0 or above Please upgrade to FortiAuthenticator version 7.0.0 or above Please upgrade to FortiProxy version 7.4.4 or above Please upgrade to FortiProxy version 7.2.10 or above Please upgrade to FortiPortal version 6.0.15 or above Please upgrade to FortiOS version 7.6.0 or above Please upgrade to FortiOS version 7.4.4 or above Please upgrade to FortiOS version 7.2.8 or above Please upgrade to FortiOS version 7.0.15 or above

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-26011?

    The severity of CVE-2024-26011 is critical due to the missing authentication for critical functions.

  • How do I fix CVE-2024-26011?

    To fix CVE-2024-26011, upgrade FortiManager to version 7.4.3 or later, FortiOS to 7.4.4 or later, or FortiProxy to version 7.4.4 or later.

  • Which versions of Fortinet products are affected by CVE-2024-26011?

    CVE-2024-26011 affects multiple versions of FortiManager, FortiPAM, FortiProxy, and FortiOS between specific version ranges.

  • How can I determine if my Fortinet product is vulnerable to CVE-2024-26011?

    You can determine vulnerability by checking if your Fortinet product version matches any of the affected versions listed in CVE-2024-26011.

  • Are there any workarounds for CVE-2024-26011 before patching?

    There are no known workarounds for CVE-2024-26011, so upgrading to the latest version is recommended as the only mitigation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203