High CPU utilization because of scanunitd process spike and crash.

If a .TAR.BZ2 or .TAR.GZ archive contains an archive bomb inside its compressed stream, the AV engine will time out.

EICAR virus is not blocked when AV profile is applied in firewall interface policy (NGFW mode) with option scan due to session offloading.

Scanunitd crash on signal 6 occurs for some file downloads.

DNS filter forwards the DNS status code 1 FormErr as status code 2 ServFail in cases where the redirect server responses have no question section.

Fabric connection failure between EMS and FortiOS.

Sometimes the FortiGate fails to resolve a FortiClient MAC or IP in the firewall dynamic address table.

Websites are not accessible if the certificate-inspection SSL-SSH profile is set in a proxy policy.

When an explicit proxy policy has a category address as destination address, the FortiGate needs to check if the address is a Google Translate URL for extra rating. This will trigger a keyword match. However, if a web filter profile is not set yet, WAD will crash. The fix will delay the keyword match until a web filter profile is present.

SNI ssl-exempt result conflicts with CN ssl-exempt result when SNI is an IP.

Firewall with forward proxy and UTM enabled is sending TLS probe with forward proxy IP instead of real server IP.

PAC file download fails with incorrect service error after upgrading to 7.0.2.

GUI does not display Source Address field when using a proxy address group in authentication rules.

diagnose wad stats policy list output displays information for only 20 proxy policies, so not all policies are included.

Explicit proxy policy does not deny request for ClearPass object if it is used as a source.

FortiGate explicit proxy does not work with SOCKS4a.

Policy with a Tor exit node as the source is not blocking traffic coming from Tor.

Expiration timer of expectation session may show a negative number.

FortiGate drops SERVER HELLO when accessing some TLS 1.3 websites using a flow-based policy with SSL deep inspection.

When auto-asic-offload is enabled in policy, IP-in-IP sessions show as expired while tunnel traffic goes through the FortiGate.

Packet is dropped due to the wrong UDP header length. The NP6XLite driver and kernel drop the packet because of the transport header check.

HTTP persistence not working for HTTP cookie and SSL session ID for round-robin load balancer.

FQDN address and FQDN custom service do not work as expected in security policy.

When a policy denies traffic for a VIP and send-deny-packet is enabled, the mappedip is used for the RST packet's source IP instead of the external IP.

The match-vip option is only useful for deny policies; however, its flag is not cleared after changing the policy action from deny to accept. When a policy uses a mapped FQDN VIP, the destination field of the iprope policy accepts the full IP range.

The packet dropped counter is not incremented for per-ip-shaper with max-concurrent-session as the only criterion and offload disabled on the firewall policy.

Firewall HTTP ldb-monitor in IPv6 detects certain types of web servers as down, when they are actually up.

Custom services name is not displayed correctly in logs with a port range of more than 3000 ports.

Get httpsd signal 11 crash when inline editing custom service from policy list page with FortiGate support tool running.

Forward traffic logs do not show MAC address object name in Device column.

FortiGate policy lookup does not work as expected (in the GUI and CLI) when the destination interface is a loopback interface.

Application filter does not work when the source is ISDB or unscanned.

Dashboard > FortiView Sources - WAN monitor does not show data for VLAN interface.

FortiView monitors, such as source and proxy, show empty results when drilling-down to sessions.

Newly created deny policy incorrectly has logging disabled and can not be enabled when the Security Fabric is enabled.

The SSID dialog page does not have support for the new MAC address filter.

Policy page should show new name/content for firewall objects after editing them from the tooltip.

A user can browse HA secondary logs in the GUI, but when a user downloads these logs, it is the primary FortiGate logs instead.

Log Details under Log & Report > Events displays the wrong IP address when an administrative user logs in to the web console.

When a FortiGate is managed by FortiManager with FortiWLM configured, the HTTPS daemon may crash while processing some FortiWLM API requests. There is no apparent impact on the GUI operation.

GUI logs out when accessing FortiView monitor page if the VDOM administrator only has ftviewgrp permission.

Managed FortiAPs and Managed FortiSwitches pages keep loading when VDOM administrator has netgrp and wifi read/write permissions.

On the Policy & Objects > Firewall Policy page, an unclear error message appears when a user creates a new SSL VPN policy with a web mode portal and a VIP or VIP group is used as the destination address.

On the Policy & Objects > Virtual IP page the GUI does not allow the user to configure two virtual IPs with different service for the same external/mapped IP and external interface.

On the Network > Interfaces page, users cannot modify the TFTP server setting. A warning with the message This option may not function correctly. It is already configured using the CLI attribute: tftp-server. appears beside the DHCP Options entry.

Firewall policy changes made in the GUI remove the replacement message group in that policy.

Last Login in SSL-VPN widget is shown as NaN on macOS Safari.

cmbdsvr signal 11 crash occurs when a wildcard FQDN is created with a duplicate ID.

httpsd crashes after NGFW policy is deleted.

On the Policy & Objects > Addresses page, filters applied on the Details column do not work.

Application control profile cannot be renamed from the GUI.

Dashboard menus are not translated for non-English languages.

On the Security Fabric > Fabric Connectors page, the connection to FortiManager is shown as down even if the connection is up.

After upgrading, the new ACME certificates configured in the GUI are using the staging environment.

Dashboard > Users & Devices > Firewall Users widget cannot load if there is a client authenticated by the WiFi captive portal.

Client Count does not display in the WiFi map if the Radio 1 is disabled on the managed FortiAP.

The GUI cannot restore a CLI-encrypted configuration file saved on a TFTP server. There is no issue for unencrypted configuration files or if the file is encrypted in the GUI.

PPPoE interface is not selectable if interface type is SSL-VPN Tunnel.

Unable to see details of Apache.Struts.MPV.Input.Validation.Bypass log.

Failed to retrieve information warning appears on secondary node faceplate.

FSSO user login is not sorted correctly by duration on Firewall Users widget.

The feature to send an email under User & Authentication > Guest Management is grayed out.

After the current session is disconnected, pressing the Enter key does not restart a new session on the GUI CLI console.

On the Network > Explicit Proxy page, the GUI does not support configuring multiple outgoing IP addresses.

After a failed administrator login attempt due to a missing two-factor authentication token, the next login attempt for another administrator may incorrectly result in an authentication failure.

When using NGFW policy-based mode, the VPN > Overlay Controller VPN option is removed.

On the LDAP server page, when clicking Browse beside Distinguished Name and then clicking OK after viewing the query results, the LDAP server page is missing fields containing the server settings.

FortiAP icon cannot be moved once placed on the WiFi map.

Unable to select and copy serial number from System Information dashboard widget.

Managed FortiSwitches page incorrectly shows a warning about an unregistered FortiSwitch even though it is registered. This only impacts transferred or RMAed FortiSwitches. This is only a display issue with no impact on the FortiSwitch's operation.

Unable to set IP address for IPsec tunnel in the GUI.

Local domain name disappears from the GUI after clicking API Preview.

MAC address name is not displayed in the Device column in the Asset Identity Center.

Filtering by Status in the SD-WAN widget is not working.

GUI is slow to load when CDN is enabled and accessed on a closed network.

FortiGate should be allowed to register when it is unregistered.

The hatalk process crashed when creating a disabled VLAN interface in an A-P cluster.

The hasync process crashed because the write buffer offset is not validated before using it.

The hasync process crashes often with signal 11 in cases when a CMDB mind map file is deleted and some processes still mind map the old file.

In an HA environment with multiple virtual clusters, System > HA will display statistics for Uptime, Sessions, and Throughput under virtual cluster 1. These statistics are for the entire device. Statistics are not displayed for any other virtual clusters.

Uninterruptible upgrade might be broken in large-scale environments.

The secondary unit tries to contact the forward server for sending the health check packets when the healthcheck under web-proxy forward-server is enabled.

Unable to connect to FortiSandbox Cloud through proxy from secondary node in an HA cluster.

The secondary FortiGate shows a DHCP IP was removed due to conflict, but it is not removed on the primary FortiGate.

In large customer configurations, some functions may time out, which causes an unexpected failover and keeps high cmdbsvr usage for a long time.

HA secondary is consistently unable to synchronize any sessions from the HA primary when the original HA primary returns.

PPPoE connection gets disconnected during HA failover.

fnbamd uses ha-mgmt-interface for certificate related DNS queries when ha-direct is enabled.

When the secondary is being synchronized, the GARP is sent out from the secondary device with the physical MAC address.

Configuration pushed from FortiManager does not respect standalone-config-sync and is pushed to all cluster members.

SCTP sessions are not fully synchronized between nodes in FGSP.

A member might not be able to be added to an aggregate interface that is down in an HA cluster.

hasync crashes when the size of hasync statistics packets is invalid.

Tunnel to Fortimanager is down log message is generated on the secondary FortiGate unit (without HA management interface).

FGSP cluster with UTM does not forward UDP or ICMP packets to the session owner.

HA desynchronizes after user from a read-only administrator group logs in.

Long wait and timeout when upgrading FG- 3000D HA cluster due to vluster2 being enabled.

SNMP community name with one extra character at the end stills matches when HA is enabled.

HA uptime remains the same after mondev failure.

The dnsproxy daemon is not updating HA management VDOM DNS after it is configured. The secondary also does not update.

Static routes not installed after HA failover.

When upgrading the secondary unit to build 1097 or later, a root.vpn.certificate.local.Fortinet_SSL configuration error appears.

System becomes non-responsive due to running out of memory. This is caused when the hasync daemon does not synchronize the files successfully to the peer.

FortiGate needs time to complete reconnecting PPPoE network if it part of an HA cluster.

Packet loss occurs on the software switch interface when a passive device goes down.

The hasync daemon crashes on FG-80E.

If the interface name is a number, an error occurs when that number is used as an hbdev priority.

Unable to form HA pair when HA encryption is enabled.

On the System > HA page, Sessions are shown as 0 after upgrading from 7.0.3 to 7.0.4.

In some cases, the fgfmd daemon is blocked by a query to the HA secondary checksum, and it will cause the tunnel between FortiManager and the FortiGate to go down.

Each time an AV database update occurs (scheduled or manually triggered), the IPS engine restarts on the SLBC secondary blade.

FortiGate can only collect up to 128 packets when detected by a signature.

The IPS sessions count is higher than system sessions, which causes the FortiGate to enter conserve mode.

Each time an AV database update occurs (scheduled or manual), the IPS engine restarts on the SLBC secondary blade. This stops UTM analysis for sessions affected by that blade.

IPS engine 7.00105 has signal 14 (Alarm clock) crash during stress testing.

IKE HA resynchronizes the synchronized connection without an established IKE SA.

For dynamic addresses in IKE, the first item under config list that can be successfully converted into an IP address can be used when mode-cfg is enabled and split-include is used.

IPsec traffic dropped due to anti-replay after HA failover.

FortiGate does not accept secondary tunnel IP address in the same subnet as the primary tunnel.

Tooltip in Dashboard > Network > IPsecwidget for phase 2 shows a Timeout year of 1970 in Firefox, Chrome, and Edge.

In a setup with IPsec VPN IKEv2 tunnel on the FortiGate to a Cisco device, the tunnel randomly disconnects after updating to 7.0.2 when there is a CMDB version change (configuration or interface).

Invalid IP address while creating a VPN IPsec tunnel.

L2TP over IPsec stopped encrypting traffic after upgrading from 6.4 to 7.0.2.

Referenced IPsec phase 1 and phase 2 interfaces can be deleted.

Spoke cannot register to OCVPN when FortiGate is in policy-based NGFW mode.

FG-40F-3G4G with WWAN DHCP interface set as L2TP client shows drops in WWAN connections and does not get the WWAN IP.

Calling-Station-ID is not present in the RADIUS packet.

When net-device is enabled on the hub, the tunnel interface IP is missing in the routing table.

BGP route is inactive in the routing table after the hub's IPsec tunnel binding interface bounces.

IPsec phase 1 interface does not create the system interface if it is an aggregate member.

IPsec hub fails to delete selector routes when NAT IP changed and IKE crashed.

Session clash messages appear in event logs for new sessions from VPN towards VIP.

Framed IP is not assigned to IPsec clients configured with set assign-ip-from usrgrp.

Tunnel had one-way traffic after iked crashed.

Mixed traffic and UTM logs are in the event log file because the current category in the log packet header is not big enough.

FortiAnalyzer logs are not cached between actual and detected loss of connection.

Unknown interface is shown in flow-based UTM logs.

The reportd process consumes a high amount of CPU.

Report suddenly cannot be generated due to no response from reportd.

Logs are missing on FortiGate Cloud from the FortiGate.

The expected reboot log is missing.

When submitting files for sandbox logging in flow mode, filetype="unknown" is displayed for PDF, DOC, JS, RTF, ZIP, and RAR files.

The syslogd daemon encounters a memory leak.

Unexpected traffic logs generated when local-out is enabled in config log setting.

Cyrillic alphabet is not displayed correctly in file filter and DLP logs.

DoT log is incorrectly categorized as a forward traffic log instead of a local traffic log.

FortiGate refuses incoming TCP connection to FTP proxy port after explicit proxy related configurations are changed.

WAD memory leak causes device to go into conserve mode.

Browser has ERR_SSL_KEY_USAGE_INCOMPATIBLE error when both ZTNA and web proxy are enabled.

diagnose wad stats policy list does not show statistics correctly when enabling certificate inspection and HTTP policy redirect.

Deep inspection of SMTPS and POP3S starts to fail after restoring the configuration file of another device with the same model.

Load balancer based on HTTP host is DNATing traffic to the wrong real server when the correct real server is disabled.

Proxy-based certificate with deep inspection fails upon receipt of a large handshake message.

Explicit FTP proxy chooses random destination port when the FTP client initiates an FTP session without using the default port.

Firefox gives SEC_ERROR_REUSED_ISSUER_AND_SERIAL error when ECDSA CA is configured for deep inspection.

WAD memory spike when downloading a file larger than 4 GB.

High CPU usage in proxy-based policy with deep inspection and IPS sensor.

WAD memory usage may spike and cause the FortiGate to enter conserve mode when downloading a large file fails.

WAD crash due to LDAP group looping.

WAD memory usage may spike and cause the FortiGate to enter conserve mode.

Captive portal fails to open requested web page on first try if WAD user is expired.

The three-way handshake packet that was marked as TCP port number reused cannot pass through the FortiGate, and the FortiGate replies with a FIN, ACK to the client.

Once AV is enabled in proxy mode, traffic will be blocked in proxy mode.

Failure to access certain AWS pages with proxy SSL deep inspection.

WAD process crashes (signal 11) with disclaimer and user authentication being applied to the web proxy.

WAD crash at signal 11.

WAD signal 11 Segmentation fault crash occurs at wad_h2_port_read_sync.

Frequent WAD crashes are causing the FortiGate to go down.

Changes to address group used for full SSL exemptions are not being activated.

In some cases, WAD daemon signal 6 (Aborted) received occurs when adding a VDOM.

Proxy inspection fails due to ipsapp session open failed: all providers busy.

WAD crash with signal 11 and signal 6 occurs when performing SAML authentication if the URL size is larger than 3 KB.

FortiGate goes into conserve mode due to high memory usage of WAD user-info process. The WAD user-info process will query the user count information from the LDAP server every 24 hours. If any of the LDAP query messages are closed by exceptions, there is a memory leak. If obtain-user-info is enabled under config user ldap, this memory leak will be triggered on daily basis.

When diagnosing WAD memory with a significant number of open HTTP sessions, the function pointer may still be called and will cause a segmentation fault.

Update various REST API endpoints to prevent information in other VDOMs from being leaked.

HTTPS daemon is not responsive when successive API calls are made to create an interface.

Some static routes disappear from RIB/FIB after modifying/installing static routes from the GUI script.

External resource local out traffic does not follow the SD-WAN rule and specified egress interface when the interface-select-method configuration in system external-resource is changed.

One IPv6 BGP neighbor is allowed to be configured with one IPv6 address format and shows a different IPv6 address format.

A typo in set dst when configuring a static route with a valid set device will result in a default static route.

LDAP external connector/FSSO polling traffic is not following the SD-WAN rules.

The default SD-WAN route for the LTE wwan interface is not created.

IKE might add two connected static routes to the same destination. If they are using same interface, deleting one of the routes will make the connected address stored on that interface get deleted.

OSPF E2 routes learned by Cisco routers are randomly removed from the routing table when the OSPF/OSPFv3 neighbor flaps.

FortiGate is sending malformed packets causing a BGP IPv6 peering flap when there is a large amount of IPv6 routes, and they cannot fit in one packet.

When policy-based routing uses a PPPoE interface, the policy route order changes after rebooting and when the link is up/down.

Policy routes order is changed after updating the source/destination of SD-WAN rules.

After ADVPN HA failover, BGP is not established, and tunnels are up but not passing traffic between the hub and spokes.

OSPF authentication error occurs with MD5 or text authentication.

The set next-hop-self-rr6 enable parameter not effective.

BGP route map community attribute cannot be changed from the GUI when there are two 16-byte concatenated versions.

Deleted BGP summary routes are not removed from routing table and are still advertised to eBGP neighbors.

IPv6 route is not created for SIT tunnel interface in SD-WAN.

SD-WAN health check with FortiGate TWAMP server causes very high packet loss.

Kernel panic crash occurs after receiving new IPv6 prefix via BGP.

A new route check to make sure the route is removed when the link monitor object fails on non-ARM based platforms.

Multicast PIM hello packet is rejected by the FortiGate.

The SD-WAN service with load-balance mode is disabled, even though there is still a member alive in the service rule.

Changing the interface weight under SD-WAN takes longer to be applied from the GUI than the CLI.

SD-WAN services use a different way to handle IPv6 packets than IPv4, which causes packets loss.

Incorrect BGP Originator_ID from route reflector seen on receiving spokes.

After restarting IKE, ADVPN shortcuts stuck in the SD-WAN service and health check.

IPv6 secondary network is removed from the routing table after reboot.

The ecmp-max-paths are not behaving as expected.

SDN connector on FG-Azure stays stuck if it is alphabetically the first subscription that is not in the permission scope.

When the Security Fabric is enabled, logging is not enabled on deny policies.

The deleted auto-scripts are not sent to FortiManager through the auto-update and cause devices go out of sync.

Downstream FortiGate csfd process crashed randomly with signal 11.

Security rating report for System Uptime incorrectly fails the check for FortiAP, even though the FortiAP is up for more than 24 hours.

Customer internal website (https://cm***.msc****.com/x***) cannot be rendered in SSL VPN web mode.

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.

Web mode and tunnel mode could not reflect the VRF setting, which causes the traffic to not pass through as expected.

JS error in SSL VPN web mode when trying to retrieve a PDF from https://vpn.ca***.com/.

SAML user configured in groups in the IdP server might match to the wrong group in SSL VPN user authentication if an external browser is used.

VNC (protocol version 3.6/3.3) connection is not working in SSL VPN web mode.

When SSL VPN interface is turned down and then manually turned up again, the SSL routes are not added back to the kernel router.

Brickstream web interface is not loading properly when accessed using SSL VPN web mode.

SSL VPN web mode has issues accessing https://te***.or***.kr.

Outdated OS support for host check should be removed.

SNAT is not working in SSL VPN web mode when accessing an SFTP server.

Users can modify the URL in SSL VPN portal to show connection launcher even when the Show Connection Launcher option is disabled.

Renaming the server entry configuration will break the connection between the IdP and FortiGate, which causes the SAML login for SSL VPN to not work as expected.

Unable to add domain entry in split-dns if set domains contains an underscore character (_).

SSL VPN PKI users fail to log in when a special character is included in the CN or subject matching field.

Telnet connection gets disconnected after three to four minutes in SSL VPN web mode while the connection is idle.

Punycode is not supported in SSL VPN DNS split tunneling.

SAP Fiori webpage using JSON is not loading in SSL VPN web mode.

SSL VPN bookmark of VNC is not using ZRLE compression and consumes more bandwidth to end clients.

Extend skip-check-for-unsupported-os to support the same OS type but different OS versions.

Endpoint event is not reported when FortiClient 7.0 connects to SSL VPN.

Issues with user log out request with Okta as an identity provider for SAML authentication.

SSL VPN bookmark issues with internal website.

SCADA portal will not fully load with SSL VPN web bookmark.

Default resolution for RDP/VNC in SSL VPN web mode cannot be configured.

SSL VPN crashed when closing web mode RDP after upgrading.

Resource is not reachable using SSL quick connection.

Clicking an SSL VPN web portal bookmark web link displays blank page.

Internal website (*.blt.local) is not loading in SSL VPN web mode.

SSL VPN web mode access problem occurs for web service security camera.

Unable to access SSL VPN bookmark in web mode.

Website is not loading in SSL VPN web mode.

SSL VPN web mode access is causing issues with MiniCAU.

Unable to load SSL VPN web portal internal webpage.

Comma character (,) is acting as delimiter in authentication session decoding when CN format is Surname, Name.

The sslvpn daemon crashes due to memory access after it has been freed.

SSL VPN web mode HTTP throughputs drop over 50%.

Unable to access internal SSL VPN bookmark in web mode.

HTTPS link is not working in SSL VPN web mode.

Webpages of back-end server behind https://vpn-***.sys***.pl/remote/ could not be displayed in SSL VPN web mode.

After upgrading to 6.4.8, NLA security mode for SSL VPN web portal bookmark does not work.

Unable to load internal website in SSL VPN web mode.

SSL VPN web mode has problems accessing ComCenter websites.

When trying to create a support ticket in Jira with SSL VPN proxy web mode, the dropdown field does not contain any values.

A blank page appears after logging in to an SSL VPN bookmark.

Cannot reach local application (dat***.btn.co.id) while using SSL VPN web mode.

Internal site not loading in SSL VPN web mode.

A bin/cu_acd crash is generated when cfg-revert is enabled and involves FortiSwitch.

Bulk MAC addresses deletions on FortiSwitch is randomly causing all wired clients to disconnect at the same time and reconnect.

Support FEC (forward error correction) implementations in 10G, 25G, 40G, and 100G interfaces for FG-3400E and FG-3600E.

A large number of detected devices causes httpsd to consume resources, and causes entry-level devices to enter conserve mode.

NP6 drops, and bandwidth is limited to under 10 Gbps in npu-vlink case.

The ipmc_sensord process is killed multiple times when the CPU or memory usage is high.

TCP 8008 permitted by authd, even though the service in the policy does not include that port.

Add support for QinQ (802.1ad) on FG-1100E, FG-1101E, FG-2200E, FG-2201E, FG-3300E, FG-3301E, and FG-3600E platforms.

FortiGuard DDNS does not update the IP address when the PPPoE reconnects.

A DNS proxy crash occurs during ssl_ctx_free.

FortiCloud central management does not work if the FortiGate has trusted host enabled for the admin account.

SFP28 port flapping when the speed is set to 10G.

Verizon LTE connection is not stable, and the connection may drop after a few hours.

On FG-20xF, the RJ45 ports connected to Dell N1548 switch do not automatically have an up link for energy detect mode.

MAC address flapping on the switch is caused by a connected FortiGate where IPS is enabled in transparent mode.

Unable to create a hardware switch with no member.

Inconsistency between GUI and CLI with respect to changing password for any super_admin accounts.

Firewall does not seem to utilize its ARP cache and is ARPing for a client MAC addresses every 20-30 seconds.

Unable to save configuration changes and get failed: No space left on device error on FG-61E, FG-81E, and FG-101E.

The cmdbsvr crashes when accessing an invalid firewall vip mapped IP that causes traffic to stop traversing the FortiGate.

PSU alarm log and SNMP trap are added for FG-20xF and FGR-60F models.

DNS server obtained via DHCPv6 prefix delegation is not used by DNS proxy.

When changing mode from DHCP to static, the existing DHCP IP is kept so no CLI command is generated and sent to FortiManager.

User should be disallowed from sending an alert email from a customized address if the email security compliance check fails.

FortiGate receives Firmware image without valid RSA signature loaded error when loading the image from FortiCloud.

When changing a per-ip-shaper, if there is ongoing traffic offloaded by NPU and it attaches that shaper, the new shaper's quota will not get updated.

Direct CLI script from FortiManager fails due to additional end at the end of diagnose debug crashlog read.

Unable to configure firewall access control lists on FG-20xF.

Flow-based inspection on WCCP (L2 forwarding) enabled policy with VLAN interfaces causes traffic to drop if asic-offload is enabled.

Packet loss on the LAG interface (eight ports) using SFP+/SFP28 ports in both static and active mode. Affected models: FG-110xE, FG-220xE, and FG-330xE.

Kernel panic results in reboot due the size of inner Ethernet header and IP header not being checked properly when the SKB is received by the VXLAN interface.

When creating a new interface with MTU override enabled, PPPoE mode, and a set MTU value, the MTU value is overridden by the default value.

WAD memory leak could cause system to halt and print fork() failed on the console.

Memory leak cause by leaked JSON object.

Connectivity issue on port26 because NP6 table configuration has an incorrect member list. Affected models: FG-110xE, FG-220xE, and FG-330xE.

When updated related configurations change, the updated configurations may crash.

DDNS interface update status can get stuck if changes to the interface are made rapidly.

dnsproxy signal 11 crash at libcrypto.so.1.1 on FWF-61F.

High CPU usage on platforms with low free memory upon IPS engine initialization.

On FG-100F, no event is raised for PSU failure and the diagnostic command is not available.

FortiAnalyzer serial number automatically learned from miglogd does not send it to FortiManager through the automatic update.

Include an entry in SNMP OID that lists the number of octets for the IP type.

Slow memory leak in IPS engine 6.091, which persists in 6.107.

High memory usage caused by downloading a large CRL list.

Kernel panic occurs when adding and deleting LAG members on NP6 models.

dhcpd has signal 6 crashes in some cases.

On a FortiGate with many FortiSwitches and FortiAPs, the Device Inventory widget and user-device-store list are empty.

Kernel goes into conserve mode due to high memory consumption of confsyncd process.

Zone transfer with FortiGate as primary DNS server fails if the FortiGate has more than 241 DNS entries.

Discrepancy between session count and number of active sessions; sessions number creeps high, causing high memory utilization.

CLI help text for link monitor failtime and recoverytime range should be (1 - 3600, default = 5).

FortiGate running startup configuration is not saved on flash drive.

SCP restore TCP session does not gracefully close with FIN packet.

Add SNMP MIB support for PBA pool.

On a FortiGate only managed by FortiManager, the FDNSetup Authlist has no FortiManager serial number.

FortiCloud FDS/selective update response contains PendingRegistration when not pending.

Restricted VDOM user is able to access the root VDOM.

dhcpd is not processing discover messages if they contain a 0 length option, such as 80 (rapid commit). The warning, length 0 overflows input buffer, is displayed.

Disabling NP6XLite offloading does not work with VLAN interface on LAG one-arm scenario.

DCE-RPC expectation session expires and never times out (timeout=never).

Negative tunnel_count in diagnose firewall gtp profile list for FGSP peer.

Firewall gives incorrect information related to link_setting when running diagnose hardware device nic <port>.

Backing up to SFTP does not work when the username contains a period (.).

Memory leak and httpsd crashes.

High memory usage due to DoT leak at ssl.port_1way_client_dox leak\wad_m_dot_conn leak\sni leak when the DoX server is 8.8.8.8.

The vwl process is spiking CPU and memory, which triggers conserve mode.

Improve dnsproxy process memory management.

MAC address group is missing in the configuration after upgrading if it has members with other address groups that come behind the current one.

After upgrading, the diagnostic command for redundant PSU is missing on FG-100F.

config-error-log debugs shows Internet Service Database related errors when upgrading from 7.0 to 7.2, which causes confusion when the Internet Service Database was updated successfully.

A fnbamd crash is caused when the LDAP server is unreachable.

There is no LDAP-based authentication possible during the time WAD updates/reads group information from the AD LDAP server.

On an HA standby device, certain certificates (such as Fortinet_CA_SSL) regenerate by themselves when trying to edit them in CLI. This also causes issues when backing up configurations on the standby device.

A fnbamd crash is caused by an LDAP server being unreachable.

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.

The fnbamd process spikes to 99% or crashes during RADIUS authentication.

In the email collection captive portal, a user can click Continue without selecting the checkbox to accept the terms and disclaimer agreement.

FortiGate blocks expired root CA, even if the cross-signed intermediate CA of the root CA is valid.

Dynamic objects are cleared when there is no connection between the FortiGate and FortiManager with NSX-T.

User ID/password shows as blank when sending the guest credentials via a custom SMS server in Guest Management.

User authentication for web proxy fails when using Kerberos or NTLM authentication with LDAP server.

Local users named pop or map do not work as expected when trying to add then as sources in a firewall policy.

fssod crashes with signal 11 on logon_dns_callback.

When upgrading from 6.4.7 to 7.0.2, GCP SDN connector entries that have a gcp-project-list configuration will be lost.

Low performance when copying files from server behind FG-VM to another site via IPsec VPN.

DHCP relay fails when VMs on different VLAN interfaces use the same transaction ID.

In AWS, if the HA connection between active and passive nodes breaks for a few seconds and reconnects, sometimes the EIP will remain in the passive node.

FG-ARM64-AWS kernel panic occurs (Kernel panic - not syncing: Fatal exception in interrupt).

gcpd has signal 11 crash at gcpd_mime_part_end.

Inconsistent TXQ selection degrades mlx5 vfNIC. Azure FortiGate interface has high latency when the IPsec tunnel is up.

Azure SDN connector is unable to pull service tag from China and Germany regions.

The vmxnet3 driver is causing IPv6 neighbor solicitation packets to be ignored.

FortiFlex license activation failed to be applied to FortiGate VM in HA. Standalone mode is OK.

For S- and V-series VM models, newly installed FG-VM has capacity for only one VDOM, but the upgraded FG-VM still has capacity for two VDOMs.

GCP HA failover for external IP does not work when using Standard Tier.

Azure performance issue on MLX5 when an unrelated VPN is up.

AWS FortiGate fails to bootstrap in new region of Cape Town, South Africa (af-south-1).

PRACK will cause voipd crashes when the following conditions are met: block-unknown is disabled in the SIP profile, the PRACK message contains SDP, and PRACK fails to find any related previous transactions (this is not a usual case).

A webpage categorized as one of the blocked categories is not actually blocked because some sites may have subdomains or paths categorized in a block category that should be blocked, but instead the request is transformed into a format unrateable by FortiGuard.

Unable to block https://cle***.com/oauth/dis***-pic*** using URL filter; content from cle***.com is still shown.

FortiGate is responding on TLS 1.0, TLS 1.1, and SSLv3 on TCP port 8015.

The urlfilter daemon continuously crashes on the secondary unit.

Consistent error messages, internal_add_timer, appear on console when running an automation script.

A cw_acd crash is observed on the FortiGate when the FortiAP is deleted from the managed AP list.

Unable to quarantine hosts behind FortiAP and FortiSwitch.

Some Apple devices cannot handle 303/307 messages, and may loop to load the external portal page and fail to pass authentication. Some android devices cannot process JavaScript redirect messages after users submit their username and password.

Client should match the new NAC policy if it is reordered to the top one.

Optimize memory usage of wpad daemon in WiFi controller for large-scale 802.11r fast BSS transition deployment.

Consider not generating rogue AP logs once a certain AP has been marked as accepted.

cw_acd is crashing with signal 11 and is causing APs to disconnect/rejoin.

In RADIUS MAC authentication, the FortiGate NAS-IP-Address will revert to 0.0.0.0 after using the FortiGate address.

A batch of APs in cluster are exhibiting control messages that the maximal retransmission limit reached, and the APs disconnect from the FortiGate.

FWF-8xF platforms should allow the DHCP server configuration of an aggregate interface (aplink) to be edited in the GUI.

If concurrent-client-limit-type is set to unlimited it is limited by the max-clients value in the VAP profile.

FortiAP firmware status is inconsistent on System > Fabric Management page and upgrade slide.

Client limit description tooltip displayed in the GUI shows incorrect information.

Two-factor authentication and WPA2-Enterprise WiFi conflict on remoteauthtimeout setting.

A packet with the wrong IP header could not be processed by the CAPWAP driver, which randomly causes the FortiGate to reboot.

FortiAP upgrade panel still prompts to upgrade to latest firmware, even when FortiAP is operating latest firmware.

Unable to import MPSK keys in the GUI (CSV file into an SSID). An Invalid file content error appears.

The arrp-profile table can now be purged if no entry is in use.

Improve arrp-profile configuration to avoid confusion.

FWF-60F has kernel panic and reboots by itself every few hours.

ZTNA access is systematically denied for ZTNA rule using SD-WAN zone as an incoming interface.

ZTNA tags do not follow the correct policy when bound in a single policy. They also do not work with groups.

Traffic was blocked by mismatched ZTNA EMS tags in a forwarding firewall policy.

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

• CVE-2021-41032

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

• CVE-2021-42755

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

• CVE-2021-43206

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

• CVE-2022-22299

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

• CVE-2022-23442

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

• CVE-2023-41678

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

• CVE-2021-43072