# CVE-2026-22575: Missing authorization in FortiManager

> Administrators can bypass workflow session approval processes in FortiManager via crafted HTTP requests, undermining change management controls.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N/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
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-3rr3-vjw9-5q79

## What is CVE-2026-22575?

CVE-2026-22575 is a medium-severity missing authorization vulnerability in Fortinet FortiManager, published on 8 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An improper access control vulnerability in Fortinet FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.10, FortiManager 7.2 all versions, FortiManager Cloud 7.6.2 through 7.6.4, FortiManager Cloud 7.4.1 through 7.4.10, FortiManager Cloud 7.2 all versions may allow an administrator to bypass the approval process for workflow sessions via crafted HTTP or HTTPs requests.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-22575 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22575 is a medium-severity missing authorization vulnerability in Fortinet FortiManager, published on 8 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22575 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-2026-22575/ (Markdown: https://insights.sbomify.com/CVE-2026-22575/index.md)
```

## Sources

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

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