A incorrect authorization vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer…

Check whether my systems are affected by CVE-2026-126215 (A incorrect authorization vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer…), 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-126215 (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 8.0.0, through 8.0.1; 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 8.0.0, through 8.0.1; 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: 8.0.2.
Conditions (all must be true for the bug to be hit):
- Affected FortiManager, FortiAnalyzer, FortiManager Cloud and FortiAnalyzer Cloud versions in the listed ranges, such as 8.0.0 through 8.0.1, 7.6.0 through 7.6.7, 7.4.0 through 7.4.11 and 7.2.0 through 7.2.12. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-234)
- The bug is reached via requests to the product's GUI. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-234)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-126215 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126215 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-234
- https://www.cve.org/CVERecord?id=CVE-2026-126215
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-126215
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-126215"}.