# CVE-2026-106171: Command injection in FortiManager

> Attackers can escalate privileges via OS command injection in FortiManager by sending specially crafted packets.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-27gm-32wm-96j2

## What is CVE-2026-106171?

CVE-2026-106171 is a medium-severity command injection vulnerability in Fortinet FortiManager, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiManager 8.0.0, FortiManager 7.6.0 through 7.6.6, FortiManager Cloud 7.6.2 through 7.6.6 may allow attacker to escalation of privilege via specially crafted packets

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-106171 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106171 is a medium-severity command injection vulnerability in Fortinet FortiManager, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106171 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-106171/ (Markdown: https://insights.sbomify.com/CVE-2026-106171/index.md)
```

## Sources

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

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