Fortinet white logo
Fortinet white logo

Resolved issues

Resolved issues

The following issues have been fixed in FortiAnalyzer Cloud version 7.6.2. To inquire about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID Description

1106056

Deleting a model device may result in the removal of the Logs folder under Storage. This issue occurs only if the model device never comes online and does not match a FortiGate.

Fabric View

Bug ID Description
1078817

The "FortiClient EMS Cloud" Fabric Connector (existing/newly added) may not function properly, causing FortiAnalyzer Cloud to potentially fail in establishing a successful connection with the "FortiClient EMS Cloud" due to this issue.

FortiView

Bug ID Description
922053 Mismatched Username Detected for the Same IP Address in IOC Compromised Hosts.
1050052 In some cases, the compromised host entry may display different FSSO users and source IPs than the actual users and source IPs on the drill-down page.

Log View

Bug ID Description

1058278

The Preview under the Chart Builder displays "No record found". Dataset is saved but chart is not saved.

Others

Bug ID Description
1060337

The log insertion might be interrupted if FortiAnalyzer Cloud is upgraded directly from version (7.4.0/7.4.1) to 7.6.2.

1062128

After upgrading to the latest available build, the FortiAnalyzer Cloud GUI displays the warning message: "A new firmware version is available".

System Settings

Bug ID Description
766197 An admin user limited to a device group can view all device's log.
1027547

In certain cases, the License Status on FortiAnalyzer Cloud may be incorrectly displayed as "Expired" despite the license being active in the account.

1058282

Remote administrators may be unable to review the Event Logs, as the GUI might display the following message: "Web Server Error 500."

Common Vulnerabilities and Exposures

Visit https://fortiguard.com/psirt for more information.

Bug ID CVE references

1125741

FortiAnalyzer Cloud 7.6.2 is no longer vulnerable to the following CVE Reference:

  • CVE-2025-24474

Resolved issues

Resolved issues

The following issues have been fixed in FortiAnalyzer Cloud version 7.6.2. To inquire about a particular bug, please contact Customer Service & Support.

Device Manager

Bug ID Description

1106056

Deleting a model device may result in the removal of the Logs folder under Storage. This issue occurs only if the model device never comes online and does not match a FortiGate.

Fabric View

Bug ID Description
1078817

The "FortiClient EMS Cloud" Fabric Connector (existing/newly added) may not function properly, causing FortiAnalyzer Cloud to potentially fail in establishing a successful connection with the "FortiClient EMS Cloud" due to this issue.

FortiView

Bug ID Description
922053 Mismatched Username Detected for the Same IP Address in IOC Compromised Hosts.
1050052 In some cases, the compromised host entry may display different FSSO users and source IPs than the actual users and source IPs on the drill-down page.

Log View

Bug ID Description

1058278

The Preview under the Chart Builder displays "No record found". Dataset is saved but chart is not saved.

Others

Bug ID Description
1060337

The log insertion might be interrupted if FortiAnalyzer Cloud is upgraded directly from version (7.4.0/7.4.1) to 7.6.2.

1062128

After upgrading to the latest available build, the FortiAnalyzer Cloud GUI displays the warning message: "A new firmware version is available".

System Settings

Bug ID Description
766197 An admin user limited to a device group can view all device's log.
1027547

In certain cases, the License Status on FortiAnalyzer Cloud may be incorrectly displayed as "Expired" despite the license being active in the account.

1058282

Remote administrators may be unable to review the Event Logs, as the GUI might display the following message: "Web Server Error 500."

Common Vulnerabilities and Exposures

Visit https://fortiguard.com/psirt for more information.

Bug ID CVE references

1125741

FortiAnalyzer Cloud 7.6.2 is no longer vulnerable to the following CVE Reference:

  • CVE-2025-24474