A unintended proxy or intermediary ('confused deputy') vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0…

Check whether my systems are affected by CVE-2026-126227 (A unintended proxy or intermediary ('confused deputy') vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0…), 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-126227 (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 FortiAnalyzer: 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
- Fortinet FortiAnalyzer 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: none listed yet.
Conditions (all must be true for the bug to be hit):
- Product is FortiAnalyzer, FortiManager, FortiAnalyzer Cloud or FortiManager Cloud in the listed affected versions (source: https://www.cve.org/CVERecord?id=CVE-2026-126227)
- The JSON API must be enabled on the admin profile (rpc-permit set to a value other than none) (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-242)
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: Disable the JSON API for the profile by setting rpc-permit to none in config system admin profile (source: https://www.cve.org/CVERecord?id=CVE-2026-126227)
CISA KEV: CVE-2026-126227 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126227 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-242
- https://www.cve.org/CVERecord?id=CVE-2026-126227
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-126227
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-126227"}.