# CVE-2026-126218: Privilege escalation in FortiManager

> An authenticated admin can escalate to root on FortiManager via crafted HTTP requests; FortiManager operators should care.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-35c9-x69h-7h3g

## What is CVE-2026-126218?

CVE-2026-126218 is a high-severity privilege escalation vulnerability in Fortinet FortiManager, published on 11 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A authorization bypass through user-controlled key vulnerability in Fortinet FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11 may allow a remote authenticated attacker with admin permission to elevate their privileges to root via crafted HTTP requests.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-126218?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-126218?

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

## Is CVE-2026-126218 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126218 and fix it if it is affected.

What it is: CVE-2026-126218 is a high-severity privilege escalation vulnerability in Fortinet FortiManager, published on 11 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126218 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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-2026-126218/ (Markdown: https://insights.sbomify.com/CVE-2026-126218/index.md)
```

## Sources

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

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