CVE-2024-50571: A heap-based buffer overflow vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.2, FortiAnalyzer 7.4.0

Routine

HIGH 7.2UPGRADEUPGRADEUPGRADE

CVE-2024-50571 is a high-severity flaw (CVSS 7.2) affecting fortianalyzer, fortianalyzer cloud, fortimanager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A heap-based buffer overflow vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.2, FortiAnalyzer 7.4.0 through 7.4.5, FortiAnalyzer 7.2.0 through 7.2.9, FortiAnalyzer 7.0.0 through 7.0.13, FortiAnalyzer 6.4 all versions, FortiAnalyzer 6.2 all versions, FortiAnalyzer 6.0 all versions, FortiAnalyzer Cloud 7.4.1 through 7.4.5, FortiAnalyzer Cloud 7.2.1 through 7.2.9, FortiAnalyzer Cloud 7.0.1 through 7.0.13, FortiAnalyzer Cloud 6.4 all versio

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-122
Published	2025-10-14
Last modified	2026-10-27

Publisher (CNA): Fortinet, Inc. · Vendor: fortinet

Last updated 2026-10-27 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-10-14 16:15 UTCPublished CVE record published
2026-10-27 23:10 UTCUpdated Record last modified

fortinet fortianalyzer UPGRADE

Affected: >= 7.0.0 and < 7.0.14 · >= 7.2.0 and < 7.2.10 · >= 7.4.0 and < 7.4.6 · >= 7.6.0 and < 7.6.3

Fixed in: 7.0.14, 7.2.10, 7.4.6, 7.6.3

Safe to downgrade to: a release before 7.0.0

1. Check installed version

apt-cache policy fortianalyzer || rpm -q fortianalyzer || fortianalyzer --version

2. UPGRADE to 7.0.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fortianalyzer

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fortianalyzer

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 7.0.0 (Debian / Ubuntu)

apt-cache madison fortianalyzer sudo apt install fortianalyzer=<VERSION_BEFORE_7.0.0> sudo apt-mark hold fortianalyzer

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list fortianalyzer sudo dnf downgrade fortianalyzer-<VERSION_BEFORE_7.0.0> sudo dnf versionlock add fortianalyzer

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

fortinet fortianalyzer cloud UPGRADE

Affected: >= 6.4.1 and < 7.0.14 · >= 7.2.1 and < 7.2.10 · >= 7.4.1 and < 7.4.6

Fixed in: 7.0.14, 7.2.10, 7.4.6

Safe to downgrade to: a release before 6.4.1

1. Check installed version

apt-cache policy fortianalyzer-cloud || rpm -q fortianalyzer-cloud || fortianalyzer-cloud --version

2. UPGRADE to 7.0.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fortianalyzer-cloud

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fortianalyzer-cloud

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.4.1 (Debian / Ubuntu)

apt-cache madison fortianalyzer-cloud sudo apt install fortianalyzer-cloud=<VERSION_BEFORE_6.4.1> sudo apt-mark hold fortianalyzer-cloud

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list fortianalyzer-cloud sudo dnf downgrade fortianalyzer-cloud-<VERSION_BEFORE_6.4.1> sudo dnf versionlock add fortianalyzer-cloud

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

fortinet fortimanager UPGRADE

Affected: >= 6.0.0 and < 7.0.14 · >= 7.2.0 and < 7.2.10 · >= 7.4.0 and < 7.4.6 · >= 7.6.0 and < 7.6.2

Fixed in: 7.0.14, 7.2.10, 7.4.6, 7.6.2

Safe to downgrade to: a release before 6.0.0

1. Check installed version

apt-cache policy fortimanager || rpm -q fortimanager || fortimanager --version

2. UPGRADE to 7.0.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fortimanager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fortimanager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)

apt-cache madison fortimanager sudo apt install fortimanager=<VERSION_BEFORE_6.0.0> sudo apt-mark hold fortimanager

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list fortimanager sudo dnf downgrade fortimanager-<VERSION_BEFORE_6.0.0> sudo dnf versionlock add fortimanager

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

fortinet fortimanager cloud UPGRADE

Affected: >= 6.4.1 and < 7.0.14 · >= 7.2.1 and < 7.2.10 · >= 7.4.1 and < 7.4.6 · 7.6.2

Fixed in: 7.0.14, 7.2.10, 7.4.6

Safe to downgrade to: a release before 6.4.1

1. Check installed version

apt-cache policy fortimanager-cloud || rpm -q fortimanager-cloud || fortimanager-cloud --version

2. UPGRADE to 7.0.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fortimanager-cloud

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fortimanager-cloud

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.4.1 (Debian / Ubuntu)

apt-cache madison fortimanager-cloud sudo apt install fortimanager-cloud=<VERSION_BEFORE_6.4.1> sudo apt-mark hold fortimanager-cloud

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list fortimanager-cloud sudo dnf downgrade fortimanager-cloud-<VERSION_BEFORE_6.4.1> sudo dnf versionlock add fortimanager-cloud

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

fortinet fortios UPGRADE

Affected: >= 6.2.0 and < 6.4.16 · >= 7.0.0 and < 7.0.17 · >= 7.2.0 and < 7.2.11 · >= 7.4.0 and < 7.4.7 · >= 7.6.0 and < 7.6.3

Fixed in: 6.4.16, 7.0.17, 7.2.11, 7.4.7, 7.6.3

Safe to downgrade to: a release before 6.2.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

fortinet fortiproxy UPGRADE

Affected: >= 1.0.0 and < 7.0.20 · >= 7.2.0 and < 7.2.13 · >= 7.4.0 and < 7.4.8 · 7.6.0

Fixed in: 7.0.20, 7.2.13, 7.4.8

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy fortiproxy || rpm -q fortiproxy || fortiproxy --version

2. UPGRADE to 7.0.20 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fortiproxy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fortiproxy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison fortiproxy sudo apt install fortiproxy=<VERSION_BEFORE_1.0.0> sudo apt-mark hold fortiproxy

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list fortiproxy sudo dnf downgrade fortiproxy-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add fortiproxy

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-50571?

fortianalyzer: upgrade to 7.0.14, 7.2.10, 7.4.6, 7.6.3; fortianalyzer cloud: upgrade to 7.0.14, 7.2.10, 7.4.6; fortimanager: upgrade to 7.0.14, 7.2.10, 7.4.6, 7.6.2. Exact commands for each OS are on this page.

Is CVE-2024-50571 being exploited?

CVE-2024-50571 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-50571 affect?

CVE-2024-50571 affects fortianalyzer, fortianalyzer cloud, fortimanager. Severity is high (CVSS 7.2). A heap-based buffer overflow vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.2, FortiAnalyzer 7.4.0 through 7.4.5, FortiAnalyzer 7.2.0 through 7.2.9, FortiAnalyzer 7.0.0 through 7.0.13, FortiAnalyzer 6.4 all versions, FortiAnalyze

How urgent is CVE-2024-50571?

Priority 36/100. High severity

Software pages

Fortinet FortiOS vulnerabilities · Fortinet vulnerabilities

Related CVEs

CVE-2025-61848 HIGH 7.2 UPGRADE UPGRADE An improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Forti
CVE-2025-68649 MEDIUM 6.0 UPGRADE UPGRADE An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet Fo
CVE-2025-67604 MEDIUM 5.3 UPGRADE UPGRADE A use of potentially dangerous function vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnal

References

← Back to latest CVEs