# CVE-2026-126170: Code injection in FortiAnalyzer

> Unauthenticated attackers can execute unauthorized code or commands on FortiAnalyzer and FortiManager via crafted HTTP requests.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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:** 11 Nov 2026
- **Also known as:** GHSA-rm98-fc32-9ggj

## What is CVE-2026-126170?

CVE-2026-126170 is a critical code injection vulnerability in Fortinet FortiAnalyzer, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A improper encoding or escaping of output vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.2, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer Cloud 8.0.1 through 8.0.2, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer-BigData 7.6.0 through 7.6.2, FortiManager 8.0.0 through 8.0.2, FortiManager 7.6.0 through 7.6.7, FortiManager Cloud 8.0.1 through 8.0.2, FortiManager Cloud 7.6.0 through 7.6.7 may allow an unauthenticated attacker to execute unauthorized code or commands via a specially crafted HTTP request

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

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


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

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

## Is CVE-2026-126170 being exploited?

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

Public exploit code:

- CVE-2026-126170 - FortiManager JSON-RPC RCE (CVSS 9.8) (github_poc): https://github.com/Ghost-Bx1/cve-2026-126170-fortimanager-jsonrpc-rce
- Containerised PoC for CVE-2026-126170 (Fortinet FG-IR-26-219): a JSON injection (CWE-116) in the FortiManager/FortiAnalyzer JRPC API lets an unauthenticated crafted request reach command execution and injects keys into the response document. Differential 7.6.7 vs 7.6.8 plus a 72-case sweep. (github_poc): https://github.com/googlesky/CVE-2026-126170
- Detection-only triage for the Fortinet November 2026 PSIRT batch: CVE-2026-126170 (9.8), CVE-2026-126254 (9.6), CVE-2026-126253 (9.3), CVE-2026-126262 (9.3), CVE-2026-126229 (9.1), CVE-2026-126261 (9.0), CVE-2026-126260 (9.0), CVE-2026-126259 (9.0). FortiOS, FortiManager, FortiAnalyzer version grading, no payloads. (github_poc): https://github.com/foxcornlab/fortinet-scanner

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126170 is a critical code injection vulnerability in Fortinet FortiAnalyzer, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126170 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 FortiAnalyzer. 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-126170/ (Markdown: https://insights.sbomify.com/CVE-2026-126170/index.md)
```

## Sources

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

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