When connecting to FortiGate Cloud Sandbox, the connection status takes a long time to update and shows as unreachable.

Scanunit should no longer submit known infected files to FortiSandbox.

When the IPS engine specifies a secure protocol for the AV query, the per protocol fortisandbox setting is not checked correctly.

Users cannot download files more than 5MB in size using FPX when SSL deep inspection and DLP profiles are enabled.

When the DNS filter is enabled with external-ip-blocklist, the IPS Engine remains in D status for an extended period of time and the DNS session ends.

The WAD process does not function as expected due to a memory allocation issue.

Proxy policy match resolves IP to multiple internet service application IDs.

The GUI-explicit-proxy setting on the System > Feature Visibility page is not retained after a FortiGate reboot or upgrade.

FortiGate blocks pages when browsing websites though a transparent proxy-redirect policy on SD-WAN.

If explicit webproxy uses SAML authentication and the PAC file is enabled at the same time, the browser will report a too many redirects error when trying to visit any websites.

The proxy policy does not work as expected when the session-ttl value is greater than the global session-ttl value.

Files do not get uploaded on webmail applications with antivirus, app control, or IPS enabled on an explicit proxy policy.

On FortiGate, the diagnose netlink interface list command shows no traffic running through the policy, even with NP offload enabled or disabled.

On the NP7 platform, traffic is blocked when egress-shaping-profile and outbandwidth are enabled on a VLAN parent interface.

Traffic may continue to flow when only deny security policies are in effect until the Policy Match Engine (PME) determines the correct policy to enforce.

When connecting to realserver through an access proxy, if making multiple requests to the same realserver with svr-pool-multiplex enabled, the old connection will be re-used but the session context dstaddr is not updated.

The clock skew tolerance is not reflected.

FortiGate accepts the ha-mgmt-intf-only local-in policy from FortiManager, even though the ha-mgmt-status is not enabled.

For local out DNAT traffic, the best output route may not be found.

On an FG-3001F NP7 device, packet loss occurs even on local-in traffic.

FortiGate drops traffic on unrelated firewall policies when tcp-without-syn is enabled.

FortiGate creates dummy destination IP logs when pinging a FortiGate VIP.

On the Policy & Objects > Firewall Policy page, firewall policies with FQDN show as unresolved in the table.

The DHCPv6 client does not work with vcluster2.

On FortiGate 7000 models, the Power Supply status displays as Normal in the GUI when there is a logged power failure.

IPv6 ECMP is not supported for the FG-6000F and FG-7000E platforms. IPv6 ECMP is supported for the FG-7000F platform.

A permanent MAC address is used instead of an HA virtual MAC address during automation.

FortiGate encounters a CPU usage issue on all blades of the secondary chassis after a firmware upgrade due to a filtering issue in the cmdbsvr.

The Security Fabric > Physical Topology and Security Fabric > Logical Topology pages do not load properly in the GUI due to misread serial numbers in the REST API proxy request.

Under normal conditions, a FortiGate 6000 or 7000 may generate event log messages due to a known issue with a feature added to FortiOS 7.2 and 7.4. The feature is designed to create event log messages for certain DP channel traffic issues but also generates event log messages when the DP processor detects traffic anomalies that are part of normal traffic processing. This causes the event log messages to detect false positives that don't affect normal operation.

For example, DP channel 15 RX drop detected! messages can be created when a routine problem is detected with a packet that would normally cause the DP processor to drop the packet.

Similar discard message may also appear if the DP buffer is full.

When the outbandwidth of an interface is set to a high or max value, pinging out of the interface does not work as expected.

On FortiGate 6000 FPCs and FortiGate 7000 FPMs the node process may consume large amounts of CPU resources, possibly affecting FPC or FPM performance. (You can run the diagnose sys top command from an FPC or FPM CLI to view CPU usage.)

This problem may be caused by security rating result submission. You can work around the problem by using the following commands to disable automatic security rating results submission and to disable running scheduled security ratings checks:

config system global set security-rating-result-submission disable set security-rating-run-on-schedule disable end

Once you have entered these commands, use the following command to restart the node process:

diagnose nodejs process restart

Incorrect SLBC traffic-related statistics may be displayed on the FortiGate 6000 or FortiGate 7000 GUI (for example, in a dashboard widgets). This can occur if an FPC or FPM is not correctly registered for statistic collection during startup.

On FortiGate 6000 and 7000 models, interested traffic cannot trigger the IPsec tunnel.

IPv6 routes are not fully synchronized between HA primary and secondary units.

On the FortiGate 7000E platform, after upgrading firmware from 7.2.8 to 7.4.x, the CLI of the secondary FIM and the FPMs in the secondary chassis of an FGCP cluster may display This firmware failed signature validation. The firmware is valid and the FortiGate 7000E cluster will operate normally.

On FortiGate 7000E and 7000F models in an HA cluster, FortiGate experiences a split brain scenario between the primary and secondary units when the primary unit is rebooted.

On FortiGate 6000 models in an HA cluster, the secondary unit does not send out logs when an interface is configured.

FortiGate displays an erroneous error for high/low warning alarms. SFP data transfer functions as expected.

In an HA configuration, FortiGate does not respond to SNMP queries causing the device to display as being DOWN.

On FortiGate 6000 models in an HA cluster, the secondary unit does not send out automated stitch emails for certain events.

An SNMP query for policy statistics returns 0 on MBD.

When applying a script to a configuration, the updated configuration is applied to the FIM but is not fully synchronized on the FPCs.

The Automatic patch upgrades enabled notification displays on the System > Firmware & Registration page even if FortiManager is set up on FortiGate.

When changing administrator account settings, the trusthost10 setting is duplicated.

The category action change is not saved if the category number is the same as the existing entry ID.

Editing a policy route from the Routing Monitor widget redirects to a blank page.

When workspace configuration save mode is set to manual in the System > Settings, configuration changes made on the primary unit and then saved do not synchronize with the secondary unit when one of the cluster units are rebooted or shutdown after the change.

FortiGate in A-P HA mode with admin-restrict-local enabled allows the local administrator to log in to the passive host, even if LDAP is available.

When Configuration save mode is set to Manual, any firewall policy change will make the cluster out-of-sync.

SCTP traffic is not forwarded back to the session owner (FGSP asymmetric traffic with IPS , NAT mode, and SCTP).

After a reboot on the secondary unit, FortiGate encounters a HA split brain condition if ha failover-hold-time is used and one ha monitor interface disabled.

In HA mode, FortiGate uses ha-mgmt-interface as the portal for the DNS resolver, even if this port may not be able to reach the DNS server.

The vcluster2 on a Secondary HA unit does not use session-sync-dev to synchronize sessions to FGSP peer unit.

VXLAN traffic does not pass through after HA cluster failover.

A secondary HA unit may go into conserve mode when joining an HA cluster if the FortiGate's configuration is large.

The VMware SDN connector does not respect the ha-direct setting and uses the management interface, causing traffic to be dropped.

When downgrading to a 7.2.x firmware version, an error message regarding cluster history displays on the CLI of the primary HA device during every bootup.

Upgrading from 7.0.14 or 7.2.8 on the HA secondary device will fail with BIOS security level 2. The image is marked un-certified and the upgrade process is aborted. The HA cluster is not affected.

When upgrading a FortiGate VM Analyzer, a CPU usage issue causes the auto scale cluster to go out of synchronization.

A WAD processing issue causes the SNMP to not respond in an HA cluster.

In a FortiGate HA configuration, the tunnel connection to FortiManager is disrupted due to a mismatched serial number and local certificate issue.

In an FGSP cluster configuration running in TP mode, reply traffic in asymmetric flow is not offloaded to NP.

When creating a new VDOM in an HA configuration, FortiGate may not operate as expected due to an hasync issue.

Connections per second (CPS) performance of SIP sessions accepted by hyperscale firewall policies with EIM and EIF disabled that include overload with port block allocation (PBA) GCN IP pools is lower than expected.

When DoS policies are used and the system is under stress conditions, BGP might go down.

New primary can get stuck on failover with HTTP CC sessions.

When switching from a hyperscale to regular interface, the FortiGate encounters a kernel interruption during configuration.

In a Hyperscale VDOM, an interruption in the kernel occurs with set nat46-generate-ipv6-fragment-header enabled.

Harpin traffic may not work due to a rare situation caused by a race condition.

After FTP traffic passes, the npu-session stat does not display the accurate amount of actual sessions on FortiGate.

In rare cases, the IPS engine may not handle buffer overflow.

When applying an IPS profile with offloading enabled, WLAN authentication does not function as expected caused by EAP transaction timeouts.

HTTPS connections to a Virtual IP (VIP) on TCP port 8015 are incorrectly blocked by the firewall, displaying an IPS block page even when no packet from the outside to TCP port 8015 should reach the internal VIP address.

On the Security Profiles > Intrusion Prevention page, when a new IPS filter is created with no filter selected, the Details column of the IPS Signatures and Filters table is blank instead of All Attributes.

The IPS DB is not preserved when upgrading to 7.2.5 or later.

The IPS engine encounters a memory usage issue caused by many HTTP3 sessions.

FortiGate experiences a CPU usage issue which may lead to an interruption in the kernel when dos-policy is enabled.

Traffic cannot pass through policy-based routing when an S2S IPsec tunnel is established.

Policy route is not matching ESP traffic.

After a third-party router failover, traffic traversing the IPsec tunnel is lost.

IPsec phase 2 negotiation fails with failed to create dialup instance, error 22 error message.

Traffic loss is experienced on inter-region ADVPN tunnels after phase 2 rekey.

A peername conflict error occurs when users configure static tunnels and then dynamic tunnels. There is no conflict when done in the reverse order.

Using IPSec over back to back EMAC VLAN interfaces does not work as expected with NPU offload enabled.

The iked does not function as expected due to a misplaced object being created in the secondary HA during failover.

IPsec VPN tunnel phase 2 instability after upgrading to 7.4.2 on the NP6xlite platform.

On NP7 platforms that are used a hub in a hub and spoke configuration, traffic packets are dropped on IPsec tunnel spokes due to an anti-replay error.

When an ipip tunnel over IPsec is configured, the configuration may cause running traffic to access the deleted SA.

If there are more than 2000 dialup IPsec tunnel interfaces used in multiple FGT firewall polices, and IKE policy update may not able to complete before IKE watchdog timeout.

FortiGate sends two verification codes for IKEv2 with RADIUS user and two-factor authentication enabled.

A second IPsec tunnel cannot be added on different IP versions that use the same peerid.

IPsec interfaces created on 802.1ad + 802.3ad interfaces with NP offloading enabled do not work as expected after a firmware upgrade.

IPsec VPN traffic does not pass over the tunnel when the HA heartbeat cable is reconnected.

Destination interface in traffic log does not match the SD-WAN quality description in the log details.

Logs are not seen for traffic passing through the firewall caused by numerous simultaneous configuration changes.

The cli-cmd-audit option in the config log.tacacs+accounting.filter command does not display in the CLI.

FortiGate encounters a memory usage issue when the disk log has rolled or when searching logs in the GUI or CLI.

In the Local Logs tab on the Log & Report > Log Settings page, the Disk Usage displays free and used space incorrectly due to an issue with the daemon after a reboot.

An interruption may occur in the daemon locallogd when the system is in memory conserve mode.

The following intrusion was observed: in the alert mail refers to another field in the anomaly log.

On the Log & Report > Forward Traffic page, when running version 7.2.3 of FortiGate, log retrieval speed from FortiAnalyzer is slow.

The configuration attribute cfgattr="password[*]" does not appear in the log when password-policy is enabled.

FortiGate encounters a CPU usage issue after rebooting with multiple VDOMs configured.

After upgrading to version 7.0.14, the system event log generates false positives for individual ports that are not used in any configuration.

FortiOS may not function as expected when the miglogd application attempts to process logs.

When uploading the log file to the FTP server or FAZ, parts of the log files are not included in the upload when two segments are sent in the same second.

On the Log & Report > System Events page, the log displays an FortiGate has experienced an unexpected power off error message when an interruption occurs in the kernel.

The miglogd does not forward log packages to FortiAnalyzer due to a memory usage issue.

User equipment IP addresses are not visible in traffic logs.

A memory usage issue in the fgtlogd daemon causes FortiGate to enter into conserve mode.

On FortiGate, a CPU usage issue occurs in the locallogd.

FortiGate 90G and 120G models display the incorrect log disk types.

The first character User-Agent information is not included in the web filter log.

A replacement message is not provided to the client when traffic is blocked by a DPI-enabled proxy mode firewall policy with application control enabled.

When the kernel API tries to access the command buffer, the device enters D state due to a kernel interruption.

DNS proxy may resolve with an IPv4 address, even when pref-dns-result is set to IPv6, if the IPv4 response comes first and there is no DNS cache.

CPU usage issue in WAD caused by source port exhaustion when using WAN optimization.

When a forward server with proxy authorization is configured with certain traffic, a memory usage issue in the WAD process interrupts the operation of FortiGate.

On FortiGate, a memory usage issue in the WAD may cause the unit to enter into conserve mode.

On FortiGate 6000 models, when an explicit proxy is configured, the TCP 3-way handshake does complete as expected.

After an upgrade, FortiOS encounters an error condition in the application daemon wad caused by an SSL cache error.

After upgrading from version 6.4.13 to version 7.0.12 or 7.0.13, FortiGate experiences a memory usage issue.

FortiGate encounters a CPU usage issue after configuration updates due to an issue in the WAD process.

On FortiGate, the WAD daemon does not work as expected due to a NULL pointer issue.

SSL Logs show certificate-probe-failed error when web profile is enabled.

Changes in the proxy-address for firewall proxy-policy can not be applied correctly.

TCP connections are not distributed properly when src-affinity-exempt is enabled.

FortiGate may not work as expected due to an error condition in the daemon WAD.

When downgrading to a previous firmware version, the restoration of IoT device information results in an out of bound access interruption due to newly added iot attributes.

An HTTP2 stream issue causes an error condition in the WAD.

In an HA setup with vCluster, a CMDB API request to the primary cluster does not synchronize the configuration to the secondary cluster.

The default route is not displayed correctly using BGP when configured using route-map and default-originate-routemap.

Make OSPFv3 update the translator role and translated Type-5 LSA when the ASBR table is updated.

FortiOS is limited to 31 interfaces for Multicast Routing using PIM-SM.

Router information in the BGP summary still shows removed BGP neighbor/peer configuration.

On FortiGate 40F-3G4G models, the LTE dynamic route not being added to route table when the IP address is changed.

BGP advertisement and Route-Reflector advertisement do not advertise additional routes after first table is announced and encoded.

The link-down-failover command does not bring the BGP peering down when the IPsec tunnel is brought down on the peer FortiGate.

The ICMP_TIME_EXCEEDED packet does not follow the original ICMP path displays the incorrect traceroute from the user.

FortiGate does not remove the BGP community list when using regex.

On FortiGate 1800F models, the VXLAN tunnel on a Loopback interface does not match SD-WAN rules.

VXLAN does not match SD-WAN rule when a service is specified.

BGP Stale routes do not function as expected in an HA configuration.

When creating a rule on the Network > Routing Objects page, the Prefix-list is set to 0.0.0.0 0.0.0.0 when an incorrect format is entered in the Prefix field.

FortiGate routes traffic to an interface with a physical status of DOWN.

OSPF logs for neighbor status are not generated when using multiple VRFs.

The OSPF daemon does not function as expected causing routing to stop working after an HA cluster failover.

FortiGate does not advertise default route to its EBGP neighbor when capability-default-originate is enabled.

The gateway attribute is skipped in the configuration when in load-balance mode after an upgrade.

In a hub and spoke configuration, the IPsec SA MTU calculation does not match with the vpn-id-ipip encapsulation resulting in a fragmentation issue.

SD-WAN SLA shows intermittent disruptions of packet loss on all links simultaneously, even though there is no actual packet loss.

Creating a BGP IPv4 network prefix or neighbor in the GUI unintentionally creates an empty IPv6 network prefix.

After enabling route-reflector-client-vpnv4 under a BGP neighbor-group, the BGP connection is flapping on the spoke and generates an error.

On the Security Fabric > Automation page, the webhook request header does not contain Content-type: application/json when using the JSON format. This causes Microsoft Teams to reject the request.

An Azure SDN connector API failure may cause a dynamic object to be purged and re-added, leading to potentia network interruptions.

When automation stitch is configured with the once schedule, the stitch is not synchronized to the downstream FortiGates.

The System > Fabric Management page may not load properly after an unsuccessful federated upgrade.

Cannot test an automation stitch that uses the Schedule trigger from the GUI.

The csfd and node daemons cause a CPU usage issue on large network topologies with many FortiAPs and/or FortiSwitches configured.

FortiGate does not identify users on SSL VPN as 2FA users if the user and token are put together in the same field (concatenated).

The SSL VPN schedule is incorrect by 1 hour when a daylight savings timezone is enabled.

Intermittent behavior in samld due to an absent crucial parameter in the SP login response may lead to SSL VPN users experiencing disconnections.

On the VPN > SSL-VPN Settings page, when renaming a selected Restrict Access Host object, the object is deselected.

Application sslvpnd *** code requested backtrace *** was observed during graceful upgrade.

SSL VPN web setup rate performance is reduced due to a high frequency of database updates.

During an upgrade, function traces caused by sslvpn watchdog timeout are observed in system logs.

FortiGate does not execute the radius disconnect request from FortiAuthenticator.

The two-factor-fac-expiry command is not working as expected for remote RADIUS users with a remote token set in FortiAuthenticator.

When the GUI tries to write a QR code for the SSL VPN configuration to the file system to send in an email, it tries to write it in a read-only folder.

When changing SSL VPN access in the Restrict Access field to Allow access from any host and enabling the Negate Source option on the VPN > SSL VPN page, the changes made in the GUI are not reflected in the CLI.

When RDP is accessed through SSL VPN web mode, keyboard strokes on-screen lag behind what is being typed by users.

FortiGate does not respond to ARP packets related to SSL VPN client IP addresses.

A CPU usage issue occurs in the tvc daemon when the vpn server cannot be reached.

SAMLD encounters a memory usage issue, preventing successful login attempts on SSL VPN.

The SSL VPN IP pool may get exhausted when tunnel-connect-without-reauth is enabled.

OneLogin SAML does not work with SSL VPN after upgrading to 7.0.15 or 7.4.3.

Duplicate log entries are created for SSL VPN sessions when the tunnel goes up or down.

A non-default LLDP profile with a configured med-network-policy cannot be applied on a switch port.

On the WiFi & Switch Controller > FortiSwitch Ports page, dynamic/NAC checks are missing from the Dynamic VLAN column.

The access-mode and storm control policy commands are not visible in FortiGate clusters causing them to go out of synchronization and does not send updated configurations to the FortiSwitch.

The switch-controller managed-switch ports' configurations are getting removed after each reboot.

FortiGate does not work as expected due an issue with a null variable in the cu_acd.

Ports 33-35 constantly show suspect messaging in the transceiver output. Affected platforms: FG-2600F and FG-2601F.

VIP traffic access to the EMAC VLAN interface uses incorrect MAC address on NP7 platform.

FortiGate cannot build a 3-way handshake in TP mode using an IPv6 route.

execute ping-option interface cannot specific an interface name of a.

FortiGate devices configured behind a proxy may not connect to the FortiToken Mobile server, leading to errors when provisioning tokens.

When a FortiGate snmp community has VDOM settings and it receives an SNMP query for OID belonging to other VDOMs, the snmpd watchdog timeout may not work as expected.

On the NP7 platform, some applications do not work as expected when nTurbo is enabled.

FortiGate enters into conserve mode due to a memory usage issue.

FortiGate encounters a CPU usage issue caused by the IPv6 FQDN check.

On FortiGate, support is only provided for a single host-key ssh-ed25519 when ssh-rsa is disabled.

The diag traffictest command does work as expected due to a UDP connection issue.

Status light is not showing on the FortiGate 60F or 100F after a cold and warm reboot.

GRE traffic through npu_vlink is not offloaded even with npu_offload enabled.

In a certain edge case, traffic directed towards a VLAN interface could cause a kernel interruption.

On FortiGate, kernel 4.19 does not adjust packets when it receives fragments needed while in proxy mode and pmtu-discovery disabled.

On FortiGate, the WWAN connection is not always stable due to a source IP issue with the VZW.

SSH users cannot access FortiGate in FIPS mode due to missing algorithms.

Some LTE modems are not activated automatically and need to be rebooted manually using the CLI in order to be activated.

GRE traffic is still allowed to flow through when the GRE interface is disabled.

A Signal 7 interruption occurs in the cmdbsvr daemon, causing FortiGate to enter conserve mode.

When cloud-communication under the global setting and include-default-servers under the central-management setting are disabled in the CLI, FortiGate still directs traffic to the public server.

On the Network > Interfaces page, hardware and software switches show VLAN interfaces as down instead of up. The actual status of the VLAN interface can be verified using the command line.

FortiWiFi-81F-2R-POE stp state is not correct after bootup with self loop topology.

Possible infinite loop can cause FortiOS to become unresponsive until the FortiGate goes through a power cycle.

The cmdbsvr could not secure the var_zone lock due to another process holding it indefinitely.

A memory usage issue occurs when multiple threads try to access VLAN group.

SNMP walk of the entire MIB fails when the configuration has split-port and a large number of interfaces.

On FortiGate, Forticron does not work as expected due to a null pointer access issue.

When an EMAC VLAN interface is set up on top of a redundant interface, the kernel may encounter an error when rebooting.

SNMP does not respond if a VRF is set on the interface.

EMAC VLAN interface uses two MAC addresses when it should only use an internally generated MAC address.

Traffic forwarding on Dialup VPN IPsec does not work as expected when npu-offload is enabled.

On NP7 platforms, egress shaping on a physical interface is not enforced on traffic according to the shaping profile definition.

On FortiGate 401F and 601F models, the CR mediatype option on x5-x8 ports is not available.

DAC cable between FortiGate and FortiSwitch stops working after upgrading from 7.2.6 to 7.2.7.

When a different transceiver type is added to FortiGate, the new transceiver information does not update in the GUI or CLI.

Memory configuration checks do not work as expected when using the diag hardware test system command due to a memory threshold issue.

FortiGate 2600F does not set 10G ports to 100G.

After upgrading FortiGate and not changing any configuration details, the output of s_duplex in get hardware nic port command displays Half instead of Full. This is purely a display issue and does not affect system operation.

FortiGate experiences packet drop when egress-shaping-profile is applied to a LAG interface.

When a FortiGate is added to FortiManager in backup mode, the ability to enable or disable auto-firmware-update on FortiGuard does not function as expected. This generates an error indicating the FortiGate is managed by FortiManager, despite backup mode suggesting otherwise.

The ipmcsensord does not work as expected when executing sensor-related commands before the high-end device sensor finishes booting up.

The SNMP OID session count for NP6 and NP7 is not displayed.

A CPU usage issue occurs and a CpuHigh SNMP trap is sent when adding a firewall policy on systems with numerous existing policies, causing issues with performance.

FortiGate does not show additional speed options outside of auto on a WAN interface.

After an upgrade on FortiOS, the kernel operation is interrupted and reboots due to a switch command issue.

The locallogd process may cause a CPU usage issue on FortiGate.

The EMAC VLAN, with a vlanid over a physical interface and a VIP configuration, has the incorrect mac address once traffic is offloaded.

FortiGate may generate a Power Redundancy Alarm error when there is no power loss. The error also does not show up in the system log.

SNMP OID .1.3.6.1.4.1.12356.101.21.2.1.1.2.4 does not return the correct value due to the device status being removed during refactoring.

When the FortiGate 100F and 101F model firmware is upgraded, the interface speed on ports 17-20 changes from auto to 1000 full.

SNMP ifSpeed OID show values as zero on VLAN interfaces in hardware switches.

FortiGate 100 models may become unresponsive and prevent access to the GUI, requiring a reboot to regain access due to an issue with the SOC3.

FortiGate does not show QoS statistics in the diagnose netlink interface list command when offloading is disabled in a firewall policy and IPsec phase 1 tunnel on NP7 platforms.

SCM tools prevent users from logging into FortiGate using SSH after an upgrade.

After an upgrade, FortiGate receives a PSU RPS LOST traps error despite not having any RPS connected.

A kernel interruption on FortiGate prevents it from rebooting after an upgrade with a specific configuration.

VLAN/EMAC VLAN traffic is unexpectedly blocked under certain conditions.

Support Kazakhstan time zone change to a single time zone, UTC+5.

After restoring a configuration on FortiGate with the interface changed from aggregate to physical, the interface switches back to aggregate and cannot be changed back to physical.

On SoC3/SoC4 platforms, a kernel interruption may occur when running WAD monitoring scripts.

FortiGate running firmware 7.2.7, the device encounters an error condition in the application daemon.

FortiGate incorrectly sends set csr instead of set certificate to FortiManager after auto enrolling a certificate using SCEP.

Administrator accounts using an admin profile with only FortiGuard Updates read-write permissions cannot open the FortiGuard page.

When a different transceiver type is added to FortiGate, the new transceiver information does not update in the GUI or CLI.

FortiGate may encounter a memory usage issue on the flpold process, causing the primary and secondary units to go out of synchronization.

The I2C bus become stuck during an upgrade due to an error in the switch-config-init command.

Traffic does not hit a new policy created in the GUI or CLI due to an auto-script command issue.

In the PSU section of the diagnose hardware test system firmware command, some information is missing.

Outgoing traffic from EMAC-VLAN uses default cos tag when traffic is not offloaded.

Fgfmsd does not function as expected when the type is set as fortimanager in system-central management but has no route to FortiManager.

On FortiGate, a slab memory usage issue causes the device to enter into conserve mode.

Some FortiGate models on NP6/NP6Lite/NP6xLite platforms experience unexpected behavior due to certain traffic conditions after upgrading to 7.2.8. Traffic may be interrupted momentarily.

On the FortiGate 1800F, the 40G interface's status is DOWN after upgrading to 7.2.8.

On a VDOM, running sudo global show does not return any system interfaces information.

FortiGate encounters a CPU usage issue when there are a high volume of traffic and scripts running on the device which could lead to an issue with performance.

FortiGate reboots twice after a factory reset when gtp-enchanced-mode is enabled.

FortiGate may experience intermittent traffic loss on an LACP interface in a virtual wire pair with l2forward enabled.

FortiGate experiences a CPU usage issue when dedicated-management-cpu is enabled.

On FortiGate, the 100G fiber cap does not include a CR4 option.

The OPC VM does not boot up when in native mode.

The SFP+ port LED does not illuminate and displays a speed 10Mbps even though the link status up and speed is set to 1000Mbps.

FortiGate does not auto negotiate to Full duplex when connecting to FortiSwitch due to a duplication error.

On FortiGate, an interruption occurs in the kernel when running WAD process monitoring scripts.

FortiGate reboots due to the maximum buffer length difference between nTurbo and NPU HW.

The kernel 4.19 cannot concurrently reassemble IPv4 fragments for a source IP with more than 64 destination IP addresses.

On the Network > Diagnostics > Packet Capture page, the timeline graph is removed from the packet viewer.

The node daemon causes a CPU usage and memory usage issue when many interfaces are being edited or created at once.

FortiGate encounters an interruption in the kernel due to a NULL pointer issue.

FortiGate encounters a memory usage issue when there is no traffic running and the configuration is not fully loaded.

When upgrading multiple firmware versions in the GUI, the Follow upgrade path option does not respect the recommended upgrade path.

Upgrading FortiOS is unsuccessful due to unmount shared data partition failed error.

When auto-upgrade is disabled, scheduled upgrades on FortiGate are not automatically canceled. To cancel any scheduled upgrades, exec federated-upgrade cancel must be done manually.

After the FortiGate in an HA environment is upgraded using the Fabric upgrade feature, the GUI might incorrectly show the status Downgrade to 7.2.X shortly, even though the upgrade has completed.

On FortiGate, an interruption occurs in the kernel in both HA FortiGates when an HA cluster's firmware is upgraded.

2FA push for FAC token and FTC will not start the push notification process without user input on the browser.

FortiGate does not generate any request to the CMP server if it uses HTTPS.

The FortiGate does not send the user's IP address to the TACACS+ server during an authorization request.

Global DH parameter does not modify the SSH connection key exchange.

After the authentication timeout setting value is reached, the Time Left value on the Firewall User Monitor > Firewall Users > Time Left page increases to thousands of days.

When using the local-in firewall authentication with SAML method, SAML users cannot get access using the authentication portal.

When rsso user groups are updated, the session table is not cleared of old sessions and traffic still hits the old policy.

Users are unable to use passwords that contain the ñ character for authentication.

When there are over 5000 firewall users, the minimized Firewall Users widget on the Dashboard does not display the donut chart or the number of users. Expanding the widget to full screen displays all users.

Client IP addresses are sent in an invalid format which some servers cannot accept.

Users are unable to use passwords that contain Polish characters ńżźćłśąó for RADIUS authentication.

If Azure accelerated networking is enabled, IPsec traffic cannot be redistributed using round-robin. This results in a CPU usage issue.

FortiGate-VM does not send LACP frames on the FortiLink interface toward FortiSwitch.

IPsec tunnels on AWS have TX errors incremented every 30 seconds.

The VMware SDN Connector does not resolve the hostname when retrieving tags and generates an error.

VPN tunnels go down due to IKE authentication loss after a firmware upgrade on the VM.

After rebooting, DPDK mode is disabled on a VLAN interface and traffic stops.

When a intended policy is configured for interesting traffic subnets, traffic flow hits the implicit deny rule instead of the configured policy.

In an HA configuration, the secondary unit heartbeat port is accessible even though access to the interface is not allowed on that unit.

Custom images do not display on the Web Filter block replacement page for HTTP traffic in flow mode.

Web filtering does not update rating servers if there is a FortiGuard DNS change.

802.11r (FT) roaming does not work in an HA setup.

In an HA setup, after disconnecting a client from an AP, the client is removed from the primary AC but remains listed on the secondary AC.

Excessive MEM POOLuse_up_cnt observed on secondary unit in an HA environment.

After upgrading from version 7.2.5, the wpad_ac does not operate as expected.

Intermittent traffic disruption observed in cw_acd caused by a rare error condition.

A kernel interruption occurs on FWF-40F/60F models when WiFi stations connect to SSID on the local radio.

A memory usage on the secondary firewall causes FortiGate to enter conserve mode.

FortiGate cannot access FAP-U devices using an SSH connection.

On the Clients By FortiAP widget on the Dashboard > WiFi page, the SSID column does not display the proper name of the downstream device.

FortiWiFi reboots or becomes unresponsive when connecting to SSID after upgrading to 7.0.14.

On FortiGate, the sta count is not accurate when some wireless clients connect to APs managed by FortiGate.

Unable to manage FortiAP from FortiGate.

FortiWiFi cannot access internal FAP consoles due to a login prompt issue in diagnose sys modem com.

Traffic does not match a simple ZTNA firewall policy when the external interface configured on a ZTNA server is a member of a SD-WAN zone being used in the same ZTNA firewall policy.

FortiGate does not use data from FortiClient to send the VPN snapshot to EMS.

When first connecting to the ZTNA server, the EMS websocket can become stuck and an error displays ZTNA Access Denied - Policy restriction!.

When ZTNA is enabled, the WAD process might encounter a memory usage issue in a rare condition.

FortiOS 7.2.9 is no longer vulnerable to the following CVE Reference:

• CVE-2024-21754