Retrospective for 2026-09-11, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.
What this advisory changes in your environment
The starting point is CERTFR-2026-AVI-1166, published on 2026-09-11. Its scope includes FortiSIEM, FortiMonitorOnSight, FortiSandbox, FortiSOAR on-premise, FortiSandbox PaaS, FortiManager, FortiManager Cloud, FortiPAM Chrome Extension, FortiPAM, FortiSandbox Cloud, FortiOS, FortiSOAR PaaS. Reported consequences are denial of service, remote code execution, data integrity compromise, security control bypass, loss of confidentiality, privilege escalation. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case contains 21 version entries; CVE identifier count: 11. Track remediation by component: a successful overall update does not demonstrate that FortiSIEM and FortiAnalyzer each received their respective fix.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-1166
- Source first published
- 2026-09-11
- Latest source revision available for this day
- 2026-09-11
- Named components
- FortiSIEM, FortiMonitorOnSight, FortiSandbox, FortiSOAR on-premise, FortiSandbox PaaS, FortiManager, FortiManager Cloud, FortiPAM Chrome Extension, FortiPAM, FortiSandbox Cloud, FortiOS, FortiSOAR PaaS, FortiProxy, FortiClientWindows, FortiAnalyzer
- CVE identifiers
- CVE-2026-22575, CVE-2026-84391, CVE-2026-84390, CVE-2026-84387, CVE-2026-84388, CVE-2026-84389, CVE-2026-84392, CVE-2026-84385, CVE-2026-84386, CVE-2026-26084, CVE-2026-84393
| Component | Published condition |
|---|---|
| FortiMonitorOnSight | 7.2.x : < 7.2.8 |
| FortiSandbox | 5.0.x : < 5.0.7 |
| FortiSandbox | 5.2.x : < 5.2.1 |
| FortiSandbox PaaS | 5.0.x : < 5.0.6 |
| FortiManager | < 7.4.11 |
| FortiManager Cloud | 7.6.x : < 7.6.5 |
| FortiPAM Chrome Extension | < 8.0.1.123 |
| FortiPAM | < 1.9.1 |
| FortiSandbox Cloud | 5.0.x : < 5.0.6 |
| FortiManager | 7.6.x : < 7.6.5 |
| FortiOS | 7.6.x : < 7.6.7 |
| FortiSandbox | 4.4.x : < 4.4.10 |
| FortiManager Cloud | < 7.4.11 |
| FortiSOAR PaaS | 7.6.x : < 7.6.7 |
| FortiSOAR on-premise | 7.6.x : < 7.6.7 |
| FortiClientWindows | < 7.4.7 |
| FortiAnalyzer | 7.6.x : < 7.6.7 |
For FortiMonitorOnSight, the published condition is “7.2.x : < 7.2.8”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of FortiSIEM, FortiMonitorOnSight does not close this case.
Mechanism and prerequisites
Code execution can give an attacker the permissions of the affected process. Check the service account and reachable network destinations. Component isolation can reduce lateral movement opportunities, but does not replace the fix.
The primary record CVE-2026-22575, published by fortinet, covers FortiManager, FortiManager Cloud. The retained revision is dated 2026-09-08. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-1166.
The published metric for CVE-2026-22575 is CVSS 3.1, 4.7/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C
- Attack vector
- network
- Prior privileges
- high
- User interaction
- none
- Complexity
- low
- Weakness
- CWE-284
Choose the appropriate intervention
- Locate FortiMonitorOnSight instances, running releases and service owners. Record condition 7.2.x : < 7.2.8 in the ticket alongside reference CERTFR-2026-AVI-1166.
- Compare the installed branch with the vendor’s FortiMonitorOnSight release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing FortiMonitorOnSight, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.
Verify the fix in a real workflow
Validation scenario to adapt for FortiSIEM, FortiMonitorOnSight: For FortiMonitorOnSight, test an authorised business flow from each zone reaching the service and confirm management restrictions. If a redundant pair exists, verify both nodes and rule persistence after failover during a planned maintenance window. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-1166: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.
Questions specific to this case
Which condition should be checked for FortiMonitorOnSight?
Advisory CERTFR-2026-AVI-1166 states: FortiMonitorOnSight — 7.2.x : < 7.2.8. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
Why not use one fix for FortiSIEM and FortiAnalyzer?
CERTFR-2026-AVI-1166 distinguishes these components within a scope containing 21 entries. Match each branch to its own update documentation and functional check.
Which prerequisites does record CVE-2026-22575 specify?
For CVE-2026-22575, the published vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C. Verify those conditions on FortiManager, FortiManager Cloud before applying them to an integration named in CERTFR-2026-AVI-1166.
Sources and related reading
- CERT-FR · CERTFR-2026-AVI-1166
- Vendor and remediation · www.fortiguard.com
- Vendor and remediation · www.fortiguard.com
- Vendor and remediation · www.fortiguard.com
- Vendor and remediation · www.fortiguard.com
- CVE-2026-22575 · CNA
Practical guide : Software inventory: prepare for end of support
Explore the decision addressed in this case
Complete source advisory inventory
The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.
Official source · CERTFR-2026-AVI-1166
Advisory revision : · Checked on :
Affected systems · 21
Original French wording is retained to avoid ambiguous translations of version conditions.
- FortiSIEM versions antérieure à 7.5.2
- FortiMonitorOnSight versions 7.2.x antérieures à 7.2.8
- FortiSandbox versions 5.0.x antérieures à 5.0.7
- FortiSOAR on-premise versions antérieure à 7.5.4
- FortiSandbox versions 5.2.x antérieures à 5.2.1
- FortiSandbox PaaS versions 5.0.x antérieures à 5.0.6
- FortiManager versions antérieures à 7.4.11
- FortiManager Cloud versions 7.6.x antérieures à 7.6.5
- FortiPAM Chrome Extension versions antérieures à 8.0.1.123
- FortiPAM versions antérieures à 1.9.1
- FortiSandbox Cloud versions 5.0.x antérieures à 5.0.6
- FortiManager versions 7.6.x antérieures à 7.6.5
- FortiOS versions 7.6.x antérieures à 7.6.7
- FortiSandbox versions 4.4.x antérieures à 4.4.10
- FortiSOAR PaaS versions antérieure à 7.5.4
- FortiProxy versions 7.6.x antérieures 7.6.7
- FortiManager Cloud versions antérieures à 7.4.11
- FortiSOAR PaaS versions 7.6.x antérieures à 7.6.7
- FortiSOAR on-premise versions 7.6.x antérieures à 7.6.7
- FortiClientWindows versions antérieures à 7.4.7
- FortiAnalyzer versions 7.6.x antérieures à 7.6.7