Koffei

CVE-2026-126229

🟠 Medium

The two sources disagree outright: securityonline says FortiManager, FortiAnalyzer and their Cloud versions, cybersecuritynews says FortiOS VDOM access. These are different products and the difference changes who is affected · General branch guidance from the coverage, since no per-id range is published: FortiOS affected 7.2.0 to 7.2.13, 7.4.0 to 7.4.12, 7.6.0 to 7.6.7 and 8.0.0 to 8.0.1, fixed in 7.2.14, 7.4.13, 7.6.8 and 8.0.2 ; FortiManager and FortiAnalyzer across the 7.2, 7.4, 7.6 and 8.0 branches, fixed in 7.2.13, 7.4.12, 7.6.8 and 8.0.2 depending on the advisory, with FortiManager 8.0.3 listed as upcoming

CVSS (Koffei note)
9.1
CVSS (v3.1, CVE List)
9.1
EPSS (2026-11-18)
0.630%
50.91th percentile

Exploitation

No — no exploitation confirmed. Fortinet reports no attacks and none of the eight is in CISA KEV. The record for this id is absent from both cvelistV5 and the MITRE CVE API, so there is no CISA-ADP container, no SSVC triage and no kev block to read, and every field in this row comes from the press coverage of the advisories rather than from a record. On proof of concept the sources are unhelpful: securityonline notes that Fortinet's own scoring marks several of the eight as having proof-of-concept or functional exploit code but names none of them, and the one record that is available, for CVE-2026-126261, carries E:U (unproven). No PoC is claimed for this id either way. CISA KEV itself could not be reached this run, so the KEV line rests on the records and on the coverage cited

Timeline

  1. 11/11/2026CVE record published (CVE List)

Risk

9.1 Critical (v3.1, Fortinet CNA) — vector not published by Fortinet in any reachable source, EPSS: no entry (not in the EPSS data set, published 10/11/2026) (CWE-639 : an authorization bypass. Given the conflict above, treat both FortiManager/FortiAnalyzer and FortiOS VDOM separation as in scope until Fortinet's own advisory is read)

Fix

Yes — FG-IR number not published in any source read

Official description

A authorization bypass through user-controlled key vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2.0 through 7.2.12, FortiAnalyzer 7.0 all versions, FortiAnalyzer Cloud 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2.1 through 7.2.12, FortiAnalyzer Cloud 7.0 all versions, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2.0 through 7.2.12, FortiManager 7.0 all versions, FortiManager Cloud 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2.1 through 7.2.12, FortiManager Cloud 7.0 all versions may allow an authenticated administrator to access to other VDOMs via specially crafted HTTP requests.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C

CWE-639