The Anti-Spam Block/Allow List Entry dialog page is not showing the proper Type values in the dropdown.

CDR archived files are deleted at random times and not retained.

FortiGate may enter conserve mode while performing Content Disarm and Reconstruction (CDR) parsing on certain MS Office documents with a .tmp extension.

Nothing is displayed in the Advanced Threat Protection Statistics dashboard widget.

Scanunit displays unclear warnings when AV package validation fails.

FortiGate sends too many unnecessary requests to FortiSandbox and causes high resource usage.

DNS UTM log still presents unknown FortiGuard category even when the DNS proxy received a rating value.

Client gets 304 response if a cached object has varying headers and is expired.

Random websites are not accessible with proxy policy after upgrading to 6.4.10.

Multipart boundary parsing failed with CRLF before the end of boundary 1.

The proxy-re-authentication-mode option has been removed in 7.2.4 and is replaced with proxy-keep-alive-mode re-authentication. The new proxy-re-authentication-time timer is associated with this re-authentication mode. There are two unresolved issues:

• After upgrading, the previously configured proxy-auth-timeout value for the absolute re-authentication mode is not preserved in the new proxy-re-authentication-time.
• The new proxy-re-authentication-time is currently configured in seconds, but it should be configured in minutes to be consistent with other related authentication timers (such as proxy-auth-timeout).

Transparent web proxy policy has no match if the source or destination interface is the same and member of SD-WAN.

Unexpected behavior in WAD caused by deploying virtual servers in non-server pool mode.

On the Policy & Objects > Firewall Policy page in 6.4.0 onwards, the IPv4 and IPv6 policy tables are combined but the custom section name (global label) is not automatically checked for duplicates. If there is a duplicate custom section name, the policy list may show empty for that section. This is a display issue only and does not impact policy traffic.

Within the Policy & Objects menu, the firewall, DoS, and traffic shaping policy pages take around five seconds to load when the FortiGate cannot reach the FortiGuard DNS servers.

An httpsd signal 6 crash occurs due to /api/v2/monitor/license/forticare-resllers.

The set sub-type ems-tag option is blocked in HA diff installation.

Inaccurate sFlow interface data reported to PRTG after upgrading to 7.0.

Virtual server aborts connection when ssl-max-version is set to tls-1.3.

NPD failed to parse zone in the source interface of a DoS/ACL policy and failed to offload.

After traffic flow changes to FGSP peer from owner, iprope information for synchronized sessions does not update on the peer side.

Full cone NAT (permit-any-host enable) causes TCP session clash.

Explicit FTPS stops working with IP pool after upgrading.

FG-3000D cluster kernel panic occurs when upgrading from 7.0.5 to 7.0.6 and later.

Traffic drops between two back-to-back EMAC VLAN interfaces.

Increased CPU usage in softirq after upgrading from 7.0.5 to 7.0.6.

When the service protocol is an IP with no specific port, it is skipped to be cached and causes a protocol/port service name in the log.

Standard and full ISDB sizes are not configurable on FG-101F.

Packets are not matching the existing session in transparent mode.

The policy or other cache lists are sometimes not freed in time. This may cause unexpected policies to be stored in the cache list.

Unexpected behavior in WAD caused by enabling HTTP/2 while using virtual servers.

Intermittent behavior in WAD during SSL renegotiation while using virtual servers.

Firewall Policy list may show empty sequence grouping sections if multiple policies are sharing the same global-label.

Merge FortiGate 6000 and 7000 series platforms.

The FortiGate 7000E and 7000F platforms do not support GTP and PFCP load balancing.

Unable to select a management interface LAG to be the direct SLBC logging interface.

On a FortiGate 6000 or 7000, the active worker count returned by the output of diagnose sys ha dump-by group can be incorrect after an FPC or FPM goes down.

The FortiView Sessions monitor displays VDOM sessions from other VDOMs.

On the System > FortiGuard page, the override FortiGuard server for AntiVirus & IPS Updates shows an Unknown status, even if the server is working correctly. This is a display issue only; the override feature is working properly.

On the Network > Interfaces page when VDOM mode is enabled, the Global view incorrectly shows the status of IPsec tunnel interfaces from non-management VDOMs as up. The VDOM view shows the correct status.

When an administrator ends a session by closing the browser, the administrator timeout event is not logged until the next time the administrator logs in.

When a FortiGate local administrator is assigned to more than two VDOMs and tries logging in to the GUI console, they get a command parse error when entering VDOM configuration mode.

Incorrect shortcut name shown on the Network > SD-WAN > Performance SLAs page.

High iowait CPU usage and memory consumption issues caused by report runner.

On the Policy & Objects > Schedules page, when the end date of a one-time schedule is set to the 31st of a month, it gets reset to the 1st of the same month.

Workaround: use CLI to set schedules with an end date of 31st.

Security Fabric root FortiGate is unable to resolve firewall object conflicts in the GUI.

Log & Report > Forward Traffic logs do not show the Policy ID if there is no Policy Name.

On the Log & Report > Forward Traffic page, using the filter Result : Deny(all) does not work as expected.

Security rating test for FortiCare Support fails when connected to FortiManager Cloud or FortiAnalyzer Cloud.

Incorrect information is being displayed for the HA role on the System > HA page.

Unable to load the Network > SD-WAN > SD-WAN Rules table sometimes due to a JavaScript error.

On the WiFi & Switch Controller > SSIDs page, multiple DHCP servers for the same range can be configured on an interface if the interface name contains a comma (,) character.

Unable to delete the LAN interface's addresses without switching it back to a none-LAN role.

On the System > HA page, a Failed to retrieve info caution message appears when hovering over the secondary unit's Hostname. The same issue is observed on the Dashboard > Status > Security Fabric widget.

On G-model profiles, changing the platform mode change from single 5G (dedicated scan enabled) to dual 5G is not taking effect.

Policy and dashboard widgets do not load when the FortiGate manages a FortiSwitch with tenant ports (exported from root to other VDOM).

The local standalone mode in a VAP configuration is disabled when viewing or updating its settings in the GUI.

The Active Administrator Sessions widget shows the incorrect interface when accessing the firewall through the GUI.

IPsec tunnel interface Bandwidth widget inbound is zero and outbound value is lower than the binding interface.

On the Network > Policy Routes page, entries cannot be copied and pasted above or below.

System > Firmware & Registration menu is not visible for administrator accounts without read-write permissions for the sysgrp-permission category.

GUI always displays Access denied error after logging in.

Unable to select addresses in FortiView monitors.

An httpsd crash occurs when the GUI fails to get the disk log settings from the FortiGate.

CLI console in GUI reports Connection lost. when the administrator has more than 100 VDOMs assigned.

An access privilege prompt is not displayed when logging in to the GUI of a FortiGate managed by a FortiManager with post-login-banner enabled. The user is logged in with read-only permissions.

On the Network > Routing Objects page, editing a prefix list with a large number of rule entries fails with an error notification that The integer value is not within valid range.

CLI console disconnects and has '/tmp/daemon_debug/node_...' crash.

Node.JS boots earlier than autod, which leads to a Node.JS crash.

GUI being exposed to port 80 on the interfaces defined in the ACME settings, even if administrative access is disabled on the interface.

When remotely accessing the FortiGate from FortiGate Cloud, the web GUI console displays Connection lost. Press Enter to start a new session.

On rare occasions, the GUI may display blank pages when the user navigates from one menu to another if there is a managed FortiSwitch present.

Long lasting sessions are expired on HA secondary device with a 10G interface.

The execute reboot script does not work in HA due to a HA failover before the script running is done.

DHCP over IPsec is not working in an FGSP cluster.

HA A-P virtual cluster information is not correctly presented in the GUI and CLI.

New factory reset box failed to synchronize with primary, which was upgraded from 7.0.

The administrator password-expire calculation on the primary and secondary returns a one-second diff, and causes HA to be out-of-sync.

When adding or removing an HA monitor interface, the link failure value is not updated.

In an HA A-P environment, an old administrator user still exists in the system after restoring the backup.

Telnet connection running ping fails during FGSP failover for virtual wire pair with VLAN traffic.

FG-500E interface stops sending IPv6 RAs after upgrading from 7.0.5 to 7.0.7.

Unable to synchronize IPsec SA between FGCP members after upgrading.

Output of diagnose sys ntp status is misleading when run on a secondary cluster member.

FG-2600F kernel panic occurs after a failover on both members of the cluster.

The session is not synchronized after HA failover by detecting monitored interface as down.

Upgrading or re-uploading an image to the HA secondary node causes the OS to be un-certified.

FGCP A-P devices get out of HA synchronization periodically due to FortiTokens being added and deleted.

Primary FortiGate synchronizes the changing HA command to the secondary.

FGSP session-sync-dev ports do not use L2 Ethernet frames but always use UDP, which reduces the performance.

hasync crashing with signal 6 after upgrading to 7.2.3 from 7.0.7.

When downloading the speed test server list, the HA cluster gets and stays out-of-sync.

Unexpected failover occurs due to uptime, even if the uptime difference is less than the ha-uptime-diff-margin.

After changing hyperscale firewall policies, it may take longer than expected for the policy changes to be applied to traffic. The delay occurs because the hyperscale firewall policy engine enhancements added to FortiOS may cause the FortiGate to take extra time to compile firewall policy changes and generate a new policy set that can be applied to traffic by NP7 processors. The delay is affected by hyperscale policy set complexity, the total number of established sessions to be re-evaluated, and the rate of receiving new sessions.

On NP7 platforms the config system npu option for nat46-force-ipv4-packet-forwarding is missing.

Unrelated background traffic gets impacted when changing a policy where a hyperscale license is used.

IPv6 traffic continues to pass through a multi-VDOM setup, even when the static route is deleted.

Timeouts occur when accessing the Migros Bank e-banking application and https://www.gs***.ch/ when the session is offloaded.

Interface routes under DHCP mode remain in LPMD after moving the interface to another VDOM.

Allowing intra-zone traffic is now supported in hyperscale firewall VDOMs. Options to block or allow intra-zone traffic are available in the GUI and CLI.

On FortiGates licensed for hyperscale firewall features, the config system setting options nat46-force-ipv4-packet-forwarding and nat64-force-ipv6-packet-forwarding now also apply to NP7-offloaded traffic. The config system npu option nat46-force-ipv4-packet-forwarding has been removed.

The number of IPS sessions is higher than kernel sessions, which causes the FortiGate to enter conserve mode.

Improvements to IPS engine monitor to resolve an error condition during periods of heavy traffic loads.

Improvements to IPS engine to optimize CPU usage when a decrypted traffic mirror profile is applied to policies in flow mode.

Improvements to IPS engine to optimize memory usage when flow mode antivirus is applied.

Under config ips global, configuring set exclude-signatures none does not save to backup configuration.

IPsec aggregate shows down status on Interfaces, Firewall Policy, and Static Routes configuration pages.

IPsec server with NP offloading drops packets with an invalid SPI during rekey.

IPsec VPN Interface shows incorrect TX/RX counter.

Users cannot define an MTU value for the aggregate VPN.

FortiGate is unable to install SA (failed to add SA, error 22) when there is an overlap in configured selectors.

IPsec static router gateway IP is set to the gateway of the tunnel interface when it is not specified.

ASCII-encoded byte code of remote gateway IP is displayed in the GUI and CLI when a VPN tunnel is formed using IKEv1 or v2 if the peer-id is not configured.

iked signal 11 crash occurs once when running a VPN test script.

If mode-cfg is used, a race condition can result in an IP conflict and sporadic routing problems in an ADVPN/SD-WAN network. Connectivity can only be restored by manually flushing the IPsec tunnels on affected spokes.

ESP tunnel traffic hopping from VRF.

ADVPN dynamic tunnel is picking a tunnel ID that is within another VPN interface IP range.

Issues with synchronization of the route information (using add-route option) on spokes during HA failover that connect to dialup VPN.

NAT detection in shortcut tunnel sometimes goes wrong.

FortiGate IPsec tunnel role could be incorrect after rebooting or upgrading, and causes negotiation to be stuck when it comes up.

When upgrading from 6.4.9 to 7.0.6 or 7.0.8, the traffic is not working between the spokes on the ADVPN environment.

Native IPsec iOS authentication failure using LDAP account with two-factor authentication.

IPsec phase 2 fails when both HA cluster members reboot at the same time.

In IPsec VPN, the fnbamd process crashes when the password and one-time password are entered in the same Password field of the VPN client.

IPsec tunnel does not coming up after the upgrading firmware on the branch FortiGate (FG-61E).

Phase 2 not initiating the rekey at soft limit timeout on new kernel platforms.

RADIUS server will reject new authentication if a previous session is missing ACCT-STOP to terminate the session, which causes the VPN connection to fail.

ADVPN spoke does not delete the BGP route entry to another spoke over IPsec when the IPsec VPN tunnel is down.

If a tunnel in an IPsec aggregate is down but its DPD link is on, the IPsec aggregate interface may still forward traffic to a down tunnel causing traffic to drop.

In an L2TP configuration, set enforce-ipsec enable is not working as expected after upgrading.

The Peer ID field in the IPsec widget should not show a warning message that Two-factor authentication is not enabled.

In an HA cluster, static routes via the IPsec tunnel interface are not inactive in the routing table when the tunnel is down.

IPsec dialup tunnel interface does not appear in the Interface dropdown of a Dashboard > Status > Interface Bandwidth widget.

Unable to view or download generated reports in the GUI if the report layout is custom.

Local out DNS traffic is generating forward traffic logs with srcintf "unknown-0".

FortiGates are showing Logs Queued in the GUI after a FortiAnalyzer reboot, even tough the queued logs were actually all uploaded to FortiAnalyzer and cleared when the connection restores.

Archived Data tab is missing from intrusion prevention and application control log Details pane once log-packet is enabled.

Policy ID filter is not working as expected.

On the Log & Report > ZTNA Traffic page, the client's Device ID is shown as [object Object]. The Log Details pane show the correct ID information.

Packet captured by firewall policy cannot be downloaded.

A deny policy with log traffic disabled is generating logs.

When log pages are scrolled down, no logs are displayed after 500 lines of logs.

Log & Report > Forward Traffic logs do not return matching results when filtered with !<application name>.

Log filter with negation of destination IP display all logs.

When FortiGate Cloud logging is enabled, the option to display 7 days of logs is not visible on the Dashboard > FortiView pages.

Unable to download more than 500 logs from the FortiGate GUI.

Syslog did not update the time after daylight saving time (DST) adjustment.

The miglogd process may send empty logs to other logging devices.

Unable to back up logs (FG-201E).

Incorrect time and time zone appear in the forward traffic log when timezone is set to 18 (GMT-3 Brasilia).

In A-P mode, when the link monitor fails, the event log displays a description of ha state is changed from 0 to 1.

A miglogd crash occurs when creating a dynamic interface cache on an ADVPN environment.

On the Log & Report > Log Settings > Local Logs page, the Local reports and Historical FortiView settings cannot be enabled.

FortiGate cannot retrieve logs from FortiAnalyzer Cloud. Results are shown rarely.

High memory usage from miglogd processes even without traffic.

FortiAnalyzer override settings are not taking effect when ha-direct is enabled.

Free-style filter not working as defined under config fortianalyzer override-filter.

The video filter does not display the proper replacement message when the user redirects to a blocked video from the YouTube homepage or video recommendation list.

Error condition in WAD occurs during traffic scans in proxy mode.

Video filter FortiGuard category takes precedence over allowed channel ID exception in the same category.

Intermittent traffic disruption caused by race condition in WAD.

When a server sends a connection close response too early, traffic from the client may be interrupted inadvertently before the request is completed.

An error condition occurs in WAD while parsing certain URIs.

Improvements to WAD to optimize CPU usage when using user groups.

An error condition occurs in WAD during an AV scan submission.

In a firewall proxy policy, the SD-WAN zone assigned to interface is not checked.

An error condition occurs in WAD when the srcintf of a firewall proxy-policy is set to an SD-WAN zone.

FortiGate out-of-band certificate check issue occurs in a proxy mode policy with SSL inspection.

Unable to make API calls using Postman Runtime script after upgrading to 7.2.0.

Improvements to WAD to optimize CPU usage when using user groups.

Improvements to WAD to resolve a memory usage issue when user-info updates the FortiAP information.

The WAD process memory usage gradually increases over a few days, causing the FortiGate to enter into conserve mode.

An encoded HTTP header may be improperly handled, causing inadvertent disruption to traffic.

Memory usage issue caused by the WAD user-info history daemon.

Memory usage issue occurs on the WAD worker in a specific scenario.

An error condition occurs in WAD when the dstaddr6 of a firewall proxy-policy is set to an IPv6 address.

User information attributes can cause disruption when they are not properly merged.

An error condition occurs in WAD due to an improper NULL check.

Unable to send logs from FortiClient to FortiAnalyzer when deep inspection is enabled on firewall policy.

Able to add incomplete policies with empty mandatory fields using the REST API.

/api/v2/monitor/system/certificate/download can still download already deleted CSR files.

High CPU usage of httpsd on FG-3600E HA system.

The MTU value on an interface cannot be set using the interface REST API.

No IGMP-IF for ifindex log points to multicast enabled interface.

Router policy destination address not take effect when internet-service-id is configured.

Early packet drop occurs when running UTM traffic on virtual switch interface.

Using set load-balance-mode weight-based in SD-WAN implicit rule does not take effect occasionally.

IPv6 VRRP backup is sending RA, which causes routing issues.

IPsec traffic sourced from a loopback interface does not follow the policy route or SD-WAN rules.

Spoke-to-spoke communication randomly breaks. The BGP route to reach the spoke subnet points to the main ADVPN tunnel instead of the shortcut tunnel.

When creating a new rule on the Network > Routing Objects page, the user cannot create a route map with a rule that has multiple similar or different AS paths in the GUI.

When there are multiple routes in the link monitor, they are not withdrawn from the routing table when the link monitor is not functioning as expected.

Traffic session is processed by a different SD-WAN rule and randomly times out.

FortiGate does not add the route in the routing table when it changes for SD-WAN members.

Application VWL crash occurs after FortiManager configuration push causes an SD-WAN related outage.

SD-WAN GUI does not load, and the lnkmtd process crashes frequently.

Application forticron signal 11 (Segmentation fault) received.

When BSM carries multiple CRPs, PIM might use the incorrect prefix to update the mroute's RP information.

Unable to set local-as in BGP confederation configuration.

Delay in joining (S,G) in PIM-SM.

All BGP routes in dual ADVPN redundant configuration are not getting updated to the correct WAN interface post-rollback to WAN failover.

After upgrading, SD-WAN is unable to fail over the traffic when one interface is down.

GUI does not show gateway IP on the routing table page if VDOM mode is transparent.

IoT device vulnerabilities should be included in security ratings.

Security Fabric widget and Fabric Connectors page do not identify FortiGates properly in HA.

The threat level threshold in the compromised host trigger does not work.

After adding a Fabric device widget, the device widget does not appear in the dashboard.

Security rating test for FortiAnalyzer fails when connected to FortiAnalyzer Cloud.

Root FortiGate cannot finish the security rating with a large Fabric topology (more than 25 to 30 devices) because the REST API is not limited to the local network.

Cisco APIC SDN update times out on large datasets.

When a custom LLDP profile has auto-isl disabled, the security rating test, Lockdown LLDP Profile, fails.

The FortiAP Firmware Versions and FortiSwitch Firmware Versions security rating tests fail because the firmware version on the FortiAPs and FortiSwitches is not recognized correctly.

Sessions with csf_syncd_log flag in a Security Fabric are not logged.

Various places in the GUI do not show the secondary HA device.

On a FortiGate that has large tables (over 1000 firewall policies, address, or other tables), security rating reports may cause the FortiGate to go into conserve mode.

Unable to load topology pages for a specific Security Fabric topology on the root and downstream FortiGates.

Error triggering automation stitch message appears when the license expiry notification type is FortiGuard Web Filter.

In a simple cluster, the primary unit failed to upgrade to 7.2.3.

FortiGate cannot display more than 500 VMs in a GCP dynamic address.

Unable to remove external resource in a certain VDOM when the external resource has no reference in that VDOM.

When the Security Fabric is enabled and admin-https-redirection is enabled on a downstream FortiGate, the following GUI features do not work for the downstream FortiGate when the administrator manages the downstream FortiGate using the root FortiGate's GUI:

• Web console access
• Diagnostic packet capture
• GUI notification when a new device joins or leaves the Security Fabric
• GUI notification if a configuration on the current page changes

These features still work for the root FortiGate's GUI.

The gcpd daemon constantly crashes (signal 11 segmentation fault).

Fabric crashes when synchronizing objects with names longer than 64 characters.

The dstaddr/dstaddr6 of an SSL VPN policy can be set to all when split tunnel mode is enabled and only the default portal is set.

The No SSL-VPN policies exist warning is displayed when an SSL VPN zone having an SSL VPN tunnel interface is used in a policy. The warning can be ignored; it does not affect the SSL VPN functionality.

When sending the SSL VPN settings email (VPN > SSL-VPN Settings > Send SSL-VPN Configuration), the Email template only includes a hyperlink to the configuration, which is not supported by Gmail and Fortinet email.

Authentication request of SSL VPN realm can now only be sent to user group, local user, and remote group that is mapped to that realm in the SSL VPN settings. The authentication request will not be applied to the user group and remote group of non-realm or other realms.

The web-mode setting should not be enabled when the portal is mapped in an SSL VPN policy where a VIP is applied.

FortiGate is not sending Accounting-Request packet that contains the Interim-Update AVP when two-factor authentication is assigned to a user (defined on the FortiGate) while connecting using SSL VPN.

Unable to view PDF files in SSL VPN web mode.

Multiple DNS suffixes cannot be set for the SSL VPN portal.

SSL VPN stops passing traffic after some time.

On the VPN > SSL-VPN Settings page, when the source-address-negate option is enabled for an address in the CLI, the GUI does not display an exclamation mark against that address entry in the Hosts field.

This is cosmetic and does not affect on the FortiGate functionality or operation. The source-address-negate option being enabled can be confirmed in the CLI.

OS checklist for the SSL VPN in FortiOS does not include macOS Ventura (13).

User peer feature for one group to match to multiple user peers in the authentication rules is broken.

Unable to access Synology NAS server through SSL VPN web mode.

Internal website with JavaScript is proxying some functions in SSL VPN web mode, which breaks them.

Browser displays an Error, Feature is not available message if a file larger than 1 MB is uploaded from FTP or SMB using a web bookmark, even though the file is uploaded successfully. There are no issues with downloading files.

SSL VPN web mode top-right dropdown button (user profile menu) does not work.

SSL VPN bookmark not accessible.

RDP over SSL VPN web mode to a Windows Server changes the time zone to GMT.

EcoStruxure Building Operations 2022 does not render using SSL VPN bookmark.

In the second authentication of RADIUS two-factor authentication, the acct-update-interval returned is 0. SSL VPN uses the second return and not send RADIUS acct-interim-update packet.

RDP/VNC host name is not encrypted when URL obscuration is enabled.

Kernel does not delete original route after address assigned to the client changes.

SSL VPN policy is ignored if no user or user group is set and the FSSO group is set.

Problem with the internal website using SSL VPN web mode.

When accessing the VDOM's GUI in SSL VPN web mode, policies are only shown for a specific VDOM instead of all VDOMs.

SSL VPN tunnel mode gets disconnected when SSL VPN web mode is disconnected by limit-user-logins.

FortiSwitch enabled VLANs with VLAN and proxy ARP access have large latencies on initial ARP resolutions.

FortiSwitches managed by FortiGate go offline intermittently and require a FortiGate reboot to recover.

Support FortiLink to recognize a FortiSwitch based on its name and not just by serial number.

Layer 3 FortiLink does not come up after upgrading.

FortiLink daemon keeps pushing the configuration to FortiSwitch for a long time when the FortiSwitch is deleted and re-discovered.

Switch controller managed switch port configuration changes do not take effect on the FortiSwitch.

On the WiFi & Switch Controller > Managed FortiSwitches page, when an administrator with restricted access permissions is logged in, the Diagnostics and Tools page for a FortiSwitch cannot be accessed.

FortiLink virtually managed switch port status is not getting pushed after the FortiGate reboots.

Inadvertent traffic disruption caused by WAD due to deadlock.

HA synchronization packets are hashed to a single queue when sync-packet-balance is enabled.

Interface belonging to other VDOMs should be removed from interface list when configuring a GENEVE interface.

The forticron daemon is constantly being restarted.

Get can not set mac address(16) error message when setting a MAC address on an interface in HA that is already set.

Not all ports are coming up after an LAG bounce on 8 × 10 GB LAG with ASR9K. Affected platforms: FG-3960E and FG-3980E.

SA is freed while its timer is still pending, which leads to a kernel crash.

Traffic passing through an EMAC VLAN interface when the parent interface is in another VDOM is blocked if NP7 offloading is enabled.

DNS proxy does not transfer the DNS query for IPv6 neighbor discovery (ND) when client devices are using random MAC addresses, so one device can configure many IPv6 addresses.

Wrong IP displayed in GUI widget if FortiGuard anycast AWS is used.

On the Network > Interfaces page, configuring a delegated interface to obtain the IPv6 prefix from an upstream DHCPv6 server fails with an error notification (CLI internal error).

When a virtual switch member port is set to be an alternate by STP, it should not reply with ARP; otherwise, the connected device will learn the MAC address from the alternate port and send subsequent packets to the alternate port.

Improve dnsproxy process memory management.

High memory usage occurs on FG-200F.

In FIPS-CC mode, if cfg-save is set to revert, the system will halt a configuration change or certificate purge.

NP7 dos-offload triggers an established TCP session to have synproxy process issues.

Scheduled speed test crash is caused by adding the same object to a list twice.

DoS policy ID cannot be moved in GUI and CLI when multiple DoS policies are enabled.

When setting the speed of 1G SFP ports on FG-180xF platforms to 1000full, the interface does not come up after rebooting.

LACP interfaces are flapping after upgrading.

FCLF8522P2BTLFTN transceiver is not working after upgrade.

The value of SNMP OID IP-MIB (RFC 4293) is inaccurate.

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

NP7 platforms may reboot unexpectedly when unable to handle kernel null pointer dereference.

FortiGate may not provide detailed information during a watchdog-initiated reboot.

A disabled EMAC VLAN interface is replying to a ping.

When deleting a non-existing entry, the error code returned is not appropriate.

DoS anomaly has incorrect threshold after loading a modified configuration file.

When kernel debug level is set to >=KERN_INFO on NP6xLite platforms, some tuples missing debug messages may get flooded and cause the system to get stuck.

After rebooting the FortiGate, the MTU value on the VXLAN interface was changed.

NP7 platforms may encounter random kernel crash after reboot or factory reset.

Console keeps displaying bcm_nl.nr_request_drop ... after the FortiGate reboots because of the cfg-save revert setting under config system global. Affected platforms: FG-10xF and FG-20xF.

FG-20xF system halts if setting cfg-save to revert under config system global and after the cfg-revert-timeout occurs.

Huge configuration files cause delays during the booting process.

Network device kernel null pointer is causing a kernel crash.

Issue with the server_host_key_algorithm compatibility when using SSH on SolarWinds.

Fortinet 10 GB transceiver LACP flapping when shut/no shut was performed on the interface from the switch side.

Configuring set src-check disable is not persistent in the kernel after rebooting for GRE interfaces.

False alarm of the PSU2 occurs with only one installed.

Time zone for Kyiv, Ukraine is missing.

Random reboots and kernel panic on NP7 cluster when the FortiGate sends a TCP RST packet and IP options are missing in the header.

The FortiGate is only offering the ssh-ed25519 algorithm for an SSH connection.

High CPU utilization occurs when relay is enabled on VLAN, and this prevents users from getting an IP from DHCP.

The 40G/100G port goes down on FG-260xF when upgrading to 7.2.

IPv6 BGP session drops when passing through a FortiGate configured with VRF.

GUI displays a blank page if vdom-admin user has partial permissions.

Add check to skip invalid names when creating a VDOM.

FG-400E-BP has crash at initXXXXXXXXXXX[1]: segfault at 3845d5a after package validation fails.

Subnet overlap error occurs when configuring the same IPv4 link-local addresses on two different interfaces.

After a cold reboot (such as a power outage), traffic interfaces may not come up with a possible loss of VLAN configurations.

execute ssh-regen-keys should be global-level command.

Forticron memory is leaking.

Memory corruption or incorrect memory access when processing a bad WQE.

The session output of dia sys npu-session list shows wrong duration when the session is very long (+40 hours).

HQIP test fails on FG-2201E.

ACME auto-renewal is not performed after HA failover.

No output of execute sensor list is displayed after rebooting.

The Dashboard > Status > Sensor Information widget does not load.

On the Network > BGP page, creating or editing a table entry increases memory consumption of the FortiGate to 99%.

FortiGate with new kernel crashes when starting debug flow.

Get zip conf file failed -1 error message when running a script configuring the FortiGate.

When traffic is offloaded to an NP7 source MAC, the packets sent from the EMAC VLAN interface are not correct.

NP7 is not configured properly when the ULL ports are added to LAG interface, which causes accounting on the LAG to not work.

FG-3501F NP7 is dropping all traffic after it is offloaded.

Kernel panic occurs due to null pointer dereference.

CPU usage issue in WAD caused by checking authentication group member information.

Unable to configure IPv6 setting on system interface (FWF-81F-2R-POE).

Unable to handle kernel NULL pointer dereference at 0000000000000000 for NP7 device; the device keeps rebooting.

Sensor information widget continuously loading.

FG-3000F reboots unexpectedly with NULL pointer dereference.

The endpoint-control fctems entry 0 is added after upgrading from 6.4 to 7.0.8 when the FortiGate does not have EMS server, which means the endpoint-control fctems feature was not enabled previously. This leads to a FortiManager installation failure.

Static route configurations were lost upgrading from 7.0.7 to 7.2.3.

FG-601E crashes randomly after upgrading to 7.0.8 and 7.0.11.

When MAC-based authentication is enabled, multiple RADIUS authentication requests may be sent at the same time. This results in duplicate sessions for the same device.

When a search is performed on a user (User & Authentication > User Definition page), the search results highlight all the groups the user belongs to.

Automatic certificate name generation is the same for global and VDOM remote certificates, which can cause certificates to exist with the same name.

RADIUS MAC authentication using ClearPass is intermittently using old credentials.

LDAPS connectivity test fails with old WinAD after OpenSSL was upgraded to 3.0.2.

FG-81F 802.1X MAC authentication bypass (MAB) failed to authenticate Cisco AP.

All devices are detected as Other identified device in the Device Inventory widget.

The EAP proxy worker application crashes frequently.

SSL VPN group matching does not work as expected for Azure auto login.

Client's firewall authentication session timeout is set to 900 when it passes MAC authentication bypass by ping.

In some cases, the proper hostnames are not showing up when looking at APs on the FortiSwitch ports screen.

ACME client fails to work with some CA servers.

A cid scan crash occurs when device detections happen in a certain order.

IPv6 traffic triggers <interface>: hw csum failure message on CLI console.

Session is not crated over NSX imported object when traffic starts to flow.

Unable to enable FIPS cipher mode on FG-VM-ARM64-AWS.

VPNs over Oracle Cloud stop processing traffic.

CPU spike observed on all the cores in a GCP firewall VM.

During a same zone AWS HA failover, moving the secondary IP will cause the EIP to be in a disassociated state.

Azure auto-scale HA shows certificate error for secondary VM.

FG-ARM64-GCP and FG-ARM64-AZURE have HA synchronization issue with internal IP after failover.

Kernel hangs on FG-VM64-AZURE.

FG-AWS SDN is unable to retrieve EKS cluster information, even thought its role is trusted by the EKS role.

Backup virtual server not working as expected (ERR_EMPTY_RESPONSE).

Azure SDN connector stopped processing when Azure returned NotFound error for VMSS interface from an AD DS-managed subscription.

FG‑VM Rackspace On-Demand upgrade from 7.2.3 to 7.2.4 breaks the pay-as-you-go license, and reverts it to an evaluation license.

An error condition occurs after a failover on the HA cluster deployed on an FG-VM64-AZURE.

Block replacement page is not pushed automatically to replace the video content when using a video filter.

Video filter function does not block YouTube stream after accessing some allowed channels.

In flow mode, URL filter configuration changes cause a spike in CPU usage of the IPS engine process.

The urlfilter process causes a memory leak, even when the firewall policy is not using the web filter feature.

FortiOS exhibits segmentation fault on hostapd on the secondary controller configured in HA.

FG-1800F drops wireless client traffic in L2 tunneled VLAN with capwap-offload enabled.

The 6 GHz channel lists should be updated according to the latest WiFi country region channels map.

Connectivity loss occurs due to switch and FortiAPs (hostapd crash).

Application hostapd crash found on FG-101F.

A hostapd process crash is shown in device crash logs.

CAPWAP traffic is not offloaded when re-enabling capwap-offload.

Wireless client shows portal related webpage while doing MAC authentication with MAB mode.

Dynamic VLAN assignment is disabled in the GUI when editing an SSID with radius mac-auth and dynamic-vlan enabled.

The voice-enterprise value changed after upgrading.

HA FortiGate encounters multiple hostapd crashes.

Hostapd segmentation fault signal 6 occurs upon HA failover.

Hostapd segmentation fault signal 11 occurs upon RF chamber setup.

The cw_acd process appears to be stuck, and is sending several access requests for MAC authentication.

Invalid wireless MAC OUI detected for a valid client on the network.

Wireless client gets disconnect from WiFi if it is connected to a WPA2 SSID more than 12 hours.

Incorrect source IP used in the self-originating traffic to RADIUS server.

Wi-Fi clients on a RADIUS MAC MPSK SSID get prematurely de-authenticated by the secondary FortiGate in the HA cluster.

Fetching the registration status does not always work.

FortiWiFi fails to act as the root mesh AP, and leaf AP does not come online.

Quarantined STA connected to a long interface name VAP is not moved to quarantined VLAN 4093.

The EMS tag name (defined in the EMS server's Zero Trust Tagging Rules) format changed in 7.2.1 from FCTEMS<serial_number>_<tag_name> to EMS<id>_ZTNA_<tag_name>.

After upgrading from 7.2.0 to 7.2.1, the EMS tag format was converted properly in the CLI configuration, but the WAD daemon is unable to recognize this new format, so the ZTNA traffic will not match any ZTNA policies with EMS tag name checking enabled.

ZTNA server (access proxy VIP) is causing all interfaces that receive ARP request to reply with their MAC address.

ZTNA real server address group gets unset once the FortiGate restarts.

Adding an EMS tag on the Policy & Objects > Firewall Policy edit page for a normal firewall policy forces NAT to be enabled.

An error case occurs in WAD when a client EMS tag changes.

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

• CVE-2023-41675

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

• CVE-2022-45862

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

• CVE-2023-33307

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

• CVE-2023-28001

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

• CVE-2023-33306

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

• CVE-2023-33301

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

• CVE-2023-29183

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

• CVE-2023-29178

IPS Engine 7.00314 is no longer vulnerable to the following CVE Reference:

• CVE-2023-40718

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

• CVE-2023-27997

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

• CVE-2023-41841