# CVE-2024-26011: Missing authorization in FortiManager

> Attackers can execute unauthorized code or commands on Fortinet network devices by sending specially crafted packets due to missing authentication.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-gm6q-h79g-j9pf

## What is CVE-2024-26011?

CVE-2024-26011 is a medium-severity missing authorization vulnerability in Fortinet Fortimanager, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authentication for critical function vulnerability in Fortinet FortiManager 7.4.0 through 7.4.2, FortiManager 7.2.0 through 7.2.4, FortiManager 7.0.0 through 7.0.11, FortiManager 6.4.0 through 6.4.14, FortiOS 7.4.0 through 7.4.3, FortiOS 7.2.0 through 7.2.7, FortiOS 7.0.0 through 7.0.14, FortiOS 6.4 all versions, FortiOS 6.2 all versions, FortiOS 6.0 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiPortal 6.0.0 through 6.0.14, FortiPortal 5.3 all versions, FortiProxy 7.4.0 through 7.4.3, FortiProxy 7.2.0 through 7.2.9, FortiProxy 7.0.0 through 7.0.16, FortiProxy 2.0 all versions, FortiProxy 01.02 all versions, FortiProxy 1.2 all versions, FortiProxy 01.01 all versions, FortiProxy 1.1 all versions, FortiProxy 01.00 all versions, FortiSwitchManager 7.2.0 through 7.2.3, FortiSwitchManager 7.0.0 through 7.0.3 allows attacker to execute unauthorized code or commands via specially crafted packets.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-26011?

It affects 6 products.


Products: Fortinet Fortimanager, Fortinet Fortios, Fortinet Fortipam, Fortinet Fortiportal, Fortinet Fortiproxy, Fortinet Fortiswitchmanager.

## How do I fix CVE-2024-26011?

No fix has been published for CVE-2024-26011 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-26011 being exploited?

There is no known exploitation of CVE-2024-26011 in the wild and no public exploit code.

## Other vulnerabilities in Fortinet Fortimanager

- [CVE-2024-47575](https://insights.sbomify.com/CVE-2024-47575/): Fortinet FortiManager Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2015-3613](https://insights.sbomify.com/CVE-2015-3613/): Privilege escalation in n/a (critical 9.8)
- [CVE-2019-6695](https://insights.sbomify.com/CVE-2019-6695/): Security feature bypass in Fortinet FortiManager (critical 9.8)
- [CVE-2019-17654](https://insights.sbomify.com/CVE-2019-17654/): Cross-site request forgery in Fortinet FortiManager (high 8.8)
- [CVE-2015-3611](https://insights.sbomify.com/CVE-2015-3611/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26011 and fix it if it is affected.

What it is: CVE-2024-26011 is a medium-severity missing authorization vulnerability in Fortinet Fortimanager, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26011 in the wild and no public exploit code.

Affected product: Fortinet Fortimanager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26011/ (Markdown: https://insights.sbomify.com/CVE-2024-26011/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26011
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26011
- OSV: https://osv.dev/vulnerability/CVE-2024-26011

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26011/
Summaries are generated and may contain mistakes; the official description above is the record.