Automated Threat Modeling

Brief Summary: FortiManager CVE-2026-126183 Authorization Bypass Through User Controlled Key in the JSON API

A brief summary of CVE-2026-126183, an authenticated authorization bypass (CWE-639) in FortiManager, FortiManager Cloud and FortiSASE-Sovereign. When the JSON API is enabled, a privileged administrator can send a crafted HTTP request and run commands outside the expected scope. Covers affected versions, Fortinet's fixed releases and the workaround.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: FortiManager CVE-2026-126183 Authorization Bypass Through User Controlled Key in the JSON API

Introduction

FortiManager sits at the center of many Fortinet deployments, pushing policy, objects and configuration to fleets of managed devices from a single console, so a flaw in how it authorizes administrative actions matters even when the attacker must already be logged in. Fortinet's advisory FG-IR-26-228, published November 10, 2026, describes that kind of flaw. An authenticated, highly privileged administrator can send a crafted HTTP request and run commands outside the scope their admin profile is supposed to permit.

The issue is tracked as CVE-2026-126183, classified as CWE-639 (Authorization Bypass Through User Controlled Key), and scored 8.7 High under CVSS v3.1. It affects FortiManager, FortiManager Cloud and FortiSASE-Sovereign. Fortinet says the vulnerability impacts the JSON API when enabled, and that API is disabled by default. Fortinet's Product Security team found the bug internally, and Fortinet reports no known exploitation. Fixed FortiManager builds are 8.0.2, 7.6.8, 7.4.12 and 7.2.13. The cloud and Sovereign products come with caveats, covered below.

The CVSS vector requires high privileges, so this is not an unauthenticated login bypass. Teams should weigh that when they prioritize it.

Technical information

Root cause: trusting a client-supplied key

CWE-639 describes authorization logic that lets a user reach another user's data or record simply by changing an identifying key in the request. MITRE notes that authentication can succeed while the later authorization check fails to enforce the user's actual entitlements. The server makes its access decision using an identifier the client controls, instead of deriving permissions from the role and scope tied to the authenticated session.

Fortinet's advisory is titled "Authorization bypass through user controlled key in GUI" and lists the affected component as API. Its CSAF document describes the issue as "IDOR in multiple products." The workaround section narrows the relevant exposure to an enabled JSON API. Taken together, these point to an administrative request path where a key supplied in the HTTP request influences which operations are permitted, allowing an administrator to reach commands beyond what their admin profile grants.

A fix for this class has to make the server recompute and enforce the caller's permissions itself rather than trusting the key in the request. FortiManager is closed source and Fortinet has not published how it implemented the change, so there is no vulnerable code or diff to show here.

What the public material does not say

The published material does not identify:

  • the specific key or parameter involved
  • the endpoint or HTTP method
  • a request body or command example
  • the exact authorization boundary that is crossed

The evidence supports an authorization boundary violation with potentially serious integrity and availability consequences. It does not establish unrestricted operating system command execution, root access, or a specific cross-tenant path. Fortinet's stated impact is improper access control, and the description limits the outcome to commands outside the expected scope.

Scoring breakdown

NVD reproduces Fortinet's CNA vector (no separate NIST assessment was present in the retrieved record):

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H
  • AV:N: network
  • AC:L: low complexity
  • PR:H: high privileges required
  • UI:N: no user interaction
  • S:C: scope changed
  • C:N: no confidentiality impact assigned
  • I:H: high integrity impact
  • A:H: high availability impact

The changed scope combined with high integrity and availability impact explains the 8.7 base score despite the PR:H requirement. Network reachability does not remove the authentication and high-privilege prerequisites.

Fortinet also publishes a temporal suffix of E:P/RL:O/RC:C with a temporal score of 8.2. Per FIRST:

  • E:P means proof-of-concept code or an attack demonstration exists that is not practical for most systems and may need substantial modification.
  • RL:O means an official fix exists.
  • RC:C means the vulnerability is confirmed.

E:P rates exploit maturity. It is not a report of observed attacks, and it does not imply a public exploit is circulating.

Attack flow

Based on the advisory, exploitation looks like this at a high level:

  1. The target is a FortiManager, FortiManager Cloud or FortiSASE-Sovereign instance on an affected version.
  2. The JSON API is enabled on at least one administrator profile (it is off by default).
  3. The attacker holds valid credentials for a highly privileged administrative account.
  4. The attacker sends a specially crafted HTTP request in which a user-controlled key influences the server's authorization decision.
  5. The server trusts that key instead of enforcing the permissions bound to the session, and executes commands outside the expected scope of the attacker's admin profile.

Because FortiManager administers downstream Fortinet devices, an administrator escaping their intended profile scope is the core concern. The exact reach of such commands has not been published.

Patch information

Fortinet fixed CVE-2026-126183 with firmware updates. There is no public source diff, commit or code-level description of the change. What we know comes from advisory FG-IR-26-228 and the CNA solutions field in the CVE record.

Fixed releases: FortiManager (on premises)

  • 8.0 branch: 8.0.0 through 8.0.1 vulnerable, fixed in 8.0.2
  • 7.6 branch: 7.6.0 through 7.6.7 vulnerable, fixed in 7.6.8
  • 7.4 branch: 7.4.0 through 7.4.11 vulnerable, fixed in 7.4.12
  • 7.2 branch: 7.2.0 through 7.2.12 vulnerable, fixed in 7.2.13

FortiManager Cloud and FortiSASE-Sovereign

  • FortiManager Cloud 8.0.1: upgrade to 8.0.2.
  • FortiManager Cloud 7.6.0 through 7.6.7: upgrade to 7.6.8.
  • FortiManager Cloud 7.4.1 through 7.4.11: no fixed build exists yet. The advisory points to an upcoming 7.4.13. This threshold differs from on-premises FortiManager 7.4.12, and the two are not interchangeable.
  • FortiManager Cloud 7.2.x: no patch for this branch. Customers must migrate to a fixed release.
  • FortiSASE-Sovereign 26.2: Fortinet fixed the issue before 26.2 shipped, and customers do not need to take any action.
  • FortiSASE-Sovereign 25, 25.3 and 25.4: no in-branch fix. Migrate to a fixed release.

Timeline: a quiet fix

Fixed builds were available roughly three weeks before disclosure. The FortiManager 8.0.2 change log shows its first release on October 22, 2026, and the advisory followed on November 10, 2026. The 8.0.2 Resolved issues page does not list this CVE, so the fix shipped quietly. If you upgraded to 8.0.2, 7.6.8, 7.4.12 or 7.2.13 at any point after release, you already have the fix whether or not you saw the advisory.

No virtual patch

The advisory states "Virtual Patch: No". No FortiGuard IPS signature blocks the crafted request in transit. Upgrading the firmware is the only vendor fix.

Workaround: disable the JSON API

Where the JSON API has been enabled on an administrator profile, Fortinet's CSAF workaround disables it:

config system admin profile edit <profile name> set rpc-permit none end

This is a configuration workaround, separate from the upgrade and migration remedies.

Upgrade preparation

Fortinet's upgrade documentation calls for:

  1. Backing up the configuration and license file, and verifying the integrity of the backup.
  2. Following the tested upgrade path in order without skipping required hops, and reviewing release notes for each hop.
  3. Checking managed device readiness: appropriate managed device firmware, pending configurations installed, and a Synchronized status before starting.
  4. Planning a maintenance window and, where possible, testing the upgrade in an environment that can surface adverse effects on the network or managed devices.

A note on conflicting upstream data

One upstream summary claimed FortiOS and FortiAnalyzer also require 8.0.2 to fix this CVE. Neither FG-IR-26-228 nor the CVE record lists those products, and that summary's other citations concerned unrelated CVEs. The only affected products are FortiManager, FortiManager Cloud and FortiSASE-Sovereign.

Affected systems and versions

FortiManager

  • 8.0.0 through 8.0.1
  • 7.6.0 through 7.6.7
  • 7.4.0 through 7.4.11
  • 7.2.0 through 7.2.12

FortiManager Cloud

  • 8.0.1
  • 7.6.0 through 7.6.7
  • 7.4.1 through 7.4.11
  • 7.2.1 through 7.2.12

FortiSASE-Sovereign

  • All 26.2 versions (remediated before release, no customer action required)
  • All 25.4 versions
  • All 25.3 versions
  • All 25 versions

Vulnerable configuration: Fortinet states the vulnerability impacts the JSON API when it is enabled on an administrator profile. The JSON API is disabled by default. Exploitation requires an authenticated attacker with high privileges.

Vendor security history

FortiManager has a documented history of exploited management-plane vulnerabilities. The most relevant is CVE-2024-47575, a separate missing-authentication flaw. In October 2024, Mandiant investigated mass exploitation involving more than 50 potentially compromised FortiManager devices across multiple industries, tracked the activity as UNC5820, and reported exploitation as early as June 27, 2024. The actor staged and exfiltrated configuration data from FortiGate devices managed by the exploited FortiManager, including appliance configurations, users and FortiOS256 hashed passwords. Mandiant reported no evidence that the stolen data was subsequently used for lateral movement in the investigated environments. CISA added CVE-2024-47575 to its Known Exploited Vulnerabilities Catalog based on exploitation confirmed by Fortinet.

That incident shows why management product security deserves attention, but it does not transfer to CVE-2026-126183. Nothing in the reviewed sources supports attributing this CVE to UNC5820 or assuming a similar data theft outcome.

For the current issue, the response signals are comparatively positive. Fortinet discovered the bug internally, crediting Loic Pantano of the Fortinet Product Security team with use of the Claude Mythos frontier AI model, and published branch-specific fixes, migration direction, a configuration workaround and machine-readable CSAF data. Fortinet marks the CVE as Known Exploited: No, and the MS-ISAC bulletin published November 11, 2026 reported no exploitation in the wild for the group of Fortinet vulnerabilities it covered. No actor attribution or CVE-specific indicators of compromise have been published.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization