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.

In multi-VDOM with default system fortiguard configuration, the DNS filter does not work for the non-management VDOM.

When a new device first connects to the EMS server with a customized certificate, the wrong slide-in pane appears in the GUI.

Fabric connection failure between EMS and FortiOS.

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

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.

Explicit web proxy does not bypass ICAP server inspection when the ICAP server is unreachable.

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

WAD is NATting to the wrong IP pool address for the interface.

Improve logic of removing HTTP Proxy-Authorization/Authorization header to prevent user credential leaking.

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.

WAD daemon may crash upon WANOpt SSL traffic.

Renaming a ClearPass dynamic address object that is configured in a proxy policy causes the address not to be matched.

In agentless NTLM authentication, the source IP in user domain-controller is not applied.

Get unexpected count for established session count, and diagnose firewall iprope clear does not work as expected.

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.

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.

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.

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.

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.

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

Dashboard > FortiView Traffic Shaping page sometimes displays an undefined traffic shaper. This is cosmetic and does not impact functionality.

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.

Dashboard > Load Balance Monitor is not loading in 7.0.4 and 7.0.5.

The number of sessions in session_count does not match the output from diagnose sys session full-stat.

The FortiGate does not refresh the iprope group for central SNAT policies after moving a newly created SNAT policy.

NAT64 is not forwarding traffic to the destination IP.

On the Traffic Shaping > Traffic Shapers tab, the Bandwidth Utilization column indicates zero traffic when there is traffic present.

Unexpected value for session_count appears.

The Traffic Shaping Policies edit dialog shows configured reverse shapers as disabled. This is a cosmetic issue and the reverse shaper is configured as defined.

IPv6 source with the same 32-bit prefix always NATs to the same IPv4 address.

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.

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

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.

Bandwidth widget shows incorrect traffic on FG-40F.

Export port link status is not correct on tenant VDOM FortiSwitch Ports page.

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

Signature not found in IPS database message when editing the IPS profile from the policy.

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

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.

Policy & Objects > DNAT & Virtual IPs page can take more than 30 seconds to load if there are more than 25 thousand virtual IPs.

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

HTTPSD daemon crashes frequently with signal 6 (aborted) at api_v2_page_result.

When logged in as guest management administrator, the custom image shows as empty on the user information printout.

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

FortiGate failed to view matched endpoints after viewing it successfully several times.

Modem 1 Health is incorrectly displayed as Disconnected in the Diagnostics and Tools pane of the FortiExtenders page.

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.

Uninterruptible upgrade might be broken in large-scale environments.

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

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

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

Firmware upgrade fails when the bandwidth between hbdev is reduced to 26 Mbps and lower (Check image file integrity error!).

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.

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 to the peer successfully.

The hasync daemon crashes on FG-80E.

FGSP does not synchronize the helper-pmap expectation session.

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

When an authentication log on length is longer than the hasync packet length and when there is a large number of logons, hasync is busy.

FortiGate does not respond to ARP request for management-ip on interface if the interface IP is changed.

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.

Failure in self-pinging towards the management IP.

HA secondary address CMDB synchronizes incorrectly for EMS dynamic tags.

Get invalid IP address when creating a firewall object in the CLI; it synchronized to the secondary in FGSP standalone-config-sync.

Unexpected HA failover on AWS A-P cluster when ipsec-soft-dec-async is enabled.

The ha-mgmt-interface stops using the configured gateway6.

Internet service database object cannot be synchronized to the secondary unit after a FortiGuard update.

hw-session-sync-dev does not support hyperscale firewall HA hardware session synchronization interface LAGs.

Flow mode web filter ovrd crashes and socket leaks in IPS daemon.

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

On SoC4 platforms, when HWDOS enabled and the anomaly action is set to block, the FortiGate does not block sessions that exceed the threshold in the DoS policy.

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.

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

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

Invalid IP address while creating a VPN IPsec tunnel.

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

Offloaded transit ESP is dropped in one direction until session is deleted.

Traffic that goes through IPsec based on a loopback interface cannot be offloaded.

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

When FGCP and FGSP is configured, but the FGCP cluster is not connected, IKE will ignore the resync event to synchronize SA data to the FGSP peer.

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

IKE is consuming excessive memory.

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.

Inbandwidth and outbandwidth on IPsec is not working properly.

IKE crash disconnected all users at the same time.

File downloads over L2TP IPsec VPN failed when using the VIP mapped to the internal server.

Shortcut fails to be triggered by interested traffic.

Logs are missing on FortiGate Cloud from the FortiGate.

Traffic denied by security policy (NGFW policy-based mode) is shown as action="accept" in the traffic log.

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.

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 crashes with signal 11 if the client sends a client hello containing a key share that does not match the key share that the server prefers.

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

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

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

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.

WAD has signal 11 crash due to invalid reading after freeing WAD user information daemon.

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.

The scan-botnet-connections block setting does not work for TCP:443 with proxy-based inspection.

WAD continually crashing at signal 11.

FortiGate is silently dropping server hello in TLS negotiation.

Memory leak identified for WAD worker dnsproxy_conn causing conserve mode.

WAD crash signal 11 and unit goes into conserve mode.

Application wad crash (Segmentation fault) , which is the first crash in a series.

In proxy inspection, IPS packet logging does not work as expected with HTTPS.

FortiGate cannot block a virus file when using the HTTP PATCH upload method.

thumbnailPhoto files are saved in the memory disk with the incorrect hash name.

Memory increase suddenly and is not released until rebooting.

In proxy inspection mode with AV enabled, TCP traffic is dropped after a while.

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.

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

Unable to set tls-active-probe.

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

FortiGate assigns an incorrect IP address for SNAT on ipunnumbered interface.

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.

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

VPN traffic is not being metered by DoS policy when using SD-WAN.

PING over IPv6 is not working from a loopback interface to any interface if the VRF on the loopback moves to vrf1.

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.

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.

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.

Unable to receive BGP routes on redundant tunnel interfaces.

SD-WAN health check event log shows the incorrect protocol.

GRE tunnel configured using a loopback interface is not working after changing the interface back and forth.

BGP neighbor advertisement-interval can be set to 0 but not take effect in ZebOS.

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

PPPoE interface is unable to accept Fabric connections.

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

Topology tree shows No connection or Unauthorized for FortiAnalyzer while sending log data to FortiAnalyzer.

Unable to send alert emails using SMTP TLS in Office 365.

Fabric Management page incorrectly shows some FortiAPs with an unregistered FortiCare status even though the FortiAP is already registered. This is just a display issue and does not impact FortiAP operation.

FortiManager card has red color on Security Fabric > Fabric Connectors page.

On the Fabric Management page, some managed FortiSwitches are not shown.

SSL VPN with external DHCP servers is not working.

Link in SSL VPN portal to FortiClient iOS redirects to legacy FortiClient 6.0 rather than the latest 6.2.

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

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

SSL VPN web mode has issues accessing https://e***.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.

SSL VPN web portal does not serve updated certificate.

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.

Slow upload speed on SSL VPN dual-stack configuration.

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.

Certain websites do not load properly in SSL VPN web mode.

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

SSL VPN web mode access to the FortiGate GUI is slow after upgrading to 7.0.3.

SSL VPN crashed when closing web mode RDP after upgrading.

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

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

Unable to access SSL VPN bookmark in web mode.

Website is not loading in SSL VPN web mode.

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%.

FortiGate GUI in SSL VPN web mode is very slow.

SSL VPN web mode is unable to redirect from port 62843 to port 8443.

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.

Unable to load NFMT routing display through SSL VPN web mode.

Internal site not loading in SSL VPN web mode.

SSO SSL VPN web mode user cannot connect to RDP intermittently.

Internal site not loading completely using SSL VPN web mode bookmark.

SSL VPN crashes and disconnects users at the same time.

SSL VPN /remote/logoutok screen loads in basic text.

Slow performance to manage FortiGate trough the bookmark configured in SSL VPN web mode.

Non-Google CAPTCHA cannot be displayed in SSL VPN web mode.

FortiGuard should only provide an installer for FortiClient VPN, instead of the full FortiClient version.

After Kronos (third-party) update from 8.1.3 to 8.1.13, SSL VPN web portal users get a blank page after logging in successfully.

SSL VPN has memory leaks and crashes.

FortiLink topology only displays partially.

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

Remote administrator password renewal shows remote token instead of new password (CLI and GUI).

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

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.

QinQ (802.1ad) support needed on the following models: FG-1100E, FG-1101E, FG-2200E, FG-2201E, FG-3300E, FG-3301E, FG-3600E, and FG-3601E.

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

A DNS proxy crash occurs during ssl_ctx_free.

Incorrect bandwidth utilization traffic widget for VLAN interface based on LACP interface.

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

Traffic passing through an EMAC VLAN interface when the parent interface is in another VDOM is blocked if NP7 offloading is enabled. If the auto-asic-offload option is disabled in the firewall policy, traffic flows as expected.

When VDOMs are enabled, changing system settings causes the GUI to display a failure to save message.

VLAN ID is not taken into consideration at the session level for traffic crossing NP7 platforms.

AirCard 340U LTE Modem does not work.

Unable to create a hardware switch with no member.

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.

FortiGate calculates faulty FDS weight with DST enabled.

HPE does not enforce a limit on fragmented packets sent to the CPU when ip-reassembly is enabled.

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.

When split port is enabled on four 10 GB ports, only one LACP port is up, and the other ports do not send/receive the LACP PDU.

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.

The value of the extra-init parameter under config system lte-modem is not passed to the modem after rebooting the device.

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.

AirCard 340U LTE modem does not work on FG-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.

After restoring the VDOM configuration, Interface <VLAN> not found in the list! is present for VLANs on the aggregate interface.

Hardware logs sent to syslog server with an incorrect timestamp in hyperscale mode.

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

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

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

Incorrect bandwidth utilization traffic widget for VLAN interface on NP6 platforms.

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.

Hardware switch is not passing VRRP packets.

Add SNMP MIB support for PBA pool.

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

Restricted VDOM user is able to access the root VDOM.

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.

ICMP traceroute with more than one probe is not working, and drops are seen on NP6 platforms.

Manually updating internet-service database may fail because there is no check of which internet-service database is being updated.

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

Memory leak and httpsd crashes.

Cached topology reports causes the FortiGate to run out of flash storage on entry-level models.

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.

DNS fails to correctly resolve hosts using the DNS database.

A request is made to the remote authentication server before checking trusthost.

The fcnacd process keeps using 99% CPU.

Repeated FortiDDNS failed messages are in the system event logs output.

BPDUs packets are blocked even though STF forwarding is enabled on FG-800D in transparent mode (UTP and SFP).

Any configuration changes on FG-2601F causes cmbdr crash with signal 6 and traffic to stop flowing.

NTP server has intermittent unresolvable logs after upgrading to 6.4.

DoS offload does not work and the npd daemon keeps crashing if the policy-offload-level is set to dos-offload under config system npu. Affected platforms: NP6XLite.

Disabling forward error correction is not working on FG-3500F.

Kernel panic occurs on FG-2610F when collecting debug flow information.

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.

FAS ends up in endless loop while synchronizing with LDAP when a special character (,) is part of a username.

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.

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.

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.

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

SCEP fails to renew if the local certificate name length is between 31 and 35 characters.

fssod crashes with signal 11 on logon_dns_callback.

When logged in with an administrator profile using a wildcard RADIUS user, creating a new dashboard widgets fails.

Incorrect captive portal page certificate is used after upgrading from 7.0.3 to 7.0.5.

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

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

FG-VM64 with specific configuration halted while upgrading from 7.0.2.

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

IBM HA is unable to fail over route properly when route table has a delegate VPC route.

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).

Azure China uses the wrong API endpoint to get meta data after secondary becomes the new primary.

HA is not in sync when a dynamic AWS service SMTP address object is retrieving a dynamic update from AWS.

Data partition is almost full on FG-VM64 platforms.

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

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.

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.

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 cannot 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.

CAPWAP tunnel traffic over WPA2-Enterprise SSID is dropped when offloading is enabled on FG-1800F.

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.

The secondary IP address in the EMS dynamic address table does not match the expected policy.

Found wad crash at wad_sched.c upon device tag matching.

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

• CVE-2022-23442

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

• CVE-2023-41678

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

• CVE-2021-43072

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

• CVE-2022-0778

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

• CVE-2022-27491