Fix ICAP client not forwarding response when host matches FQDN.

SSH command filter no longer works after prompt change.

No valid FortiSandbox Cloud license while enabling Cloud Sandbox.

LDAP cache was not updated properly after the user group changed in Active Directory server.

SSH public keys are lost after upgrading from Beta 1 to latest interim build, and they can no longer be configured.

Correlation log does not show security action when application category is unknown.

Fix matching regression caused by secure web proxy .

Config backup encryption key should not appear in GET parameters.

Issue with the WAD debug filter on vd_id and dst6 or src6.

Unexpect hang-up on FPX-4000E.

FortiProxy ESXi VM reboots randomly.

FortiNBI reports error: Failed to change FPX add mode because the FNBI service is stopped.

Authenticated users using an IP-based authentication rule may need to be re-authenticated per request.

Fix WAD crash seen due to missing hash map initialization and port.

FortiNBI does not support PAC file and does not work using manually configuration.

Update voltage monitoring with official Supermicro values.

FortiGate DLP filter EXE files does not work on Windows.

Some non-http traffic was redirected to WAD unexpectedly when L7 address exists in policy.

FPX-2000G and FPX-4000G STA and UID LED color issue.

FortiProxy kernel memory leak.

EIP of mgmt-intf is mistakenly moved from secondary FPX to the primary in an AWS A-P HA cluster.

Issue with format string that causes httpsd and CLI crash.

LDAP search type default is unset due to an incorrect default value.

WAD debug settings do not show the correct category.

Tencent WeCom cannot send picture through web explicit proxy.

Unable to config wildcard FQDN addresses in the GUI.

FortiProxy HA config-sync-only secondaries receive system updates triggered by both updated and hasync.

Need to verify filters of wad debug trace and make sure all the necessary info is logged and filter works properly.

Fix the proxy-based address is not allowed for access-proxy proxy-policy.

Explicit FTPS authentication with transparent policy does not work.

WAD policy matching crashed at matching the source address due to null source and destination addresses in dummy policy.

Validate address group members when config is loaded. If an error occurs while loading iptables rules for a specific policy, skip only the malformed policy instead of aborting the policy loading as a whole.

FortiProxy matches user to wrong user group and hits the wrong policy.

External resource entry missing under destination address in firewall policy.

When multiple ports are configured for a firewall policy's service, only traffic to the first port matches the policy.

Non-root VDOM explicit proxy DNS fails.

Fix scanunit error logs on non-error case.

Inline option for FortiSandbox inspection is missing in FPX antivirus profile.

Sessions pane does not show any data in FortiView ZTNA Servers by Bytes

Local traffic section should be removed as FortiProxy does not support local-in policy.

Change FortiCloud Logs to FortiGate Cloud.

Fix HTTP request to FQDN address not directed to WAN when dst_address includes wildcard FQDN.

Cloud FortiSandbox is shown instead of FortiCloud Logs/FortiGate Cloud.

WAD worker memory usage slowly increased.

GUI does not display Log HTTP Transaction under ZTNA Rules.

Add device info columns (clientdeviceid, clientdeviceowner, clientdevicetags, emsconnection) to the http-transaction log.

When executing the get sys ha status command, the CLI session crashed.

internet-service6 is not displayed properly in a policy.

srcaddr6 should not be configurable on a policy when internet-service is enabled.

Unable to save interfaces when configuring a fabric connector.

Revert to the newer version of json parse/print needed for FNBI.

WAD crashes at wad_url_fetch_cate2.

CSF GUI API forwarding fails.

Support missing nested address group members.

The visibility field is missing in the service custom.

A-P cluster fails to form properly after a switchover, requiring a reboot on the new secondary device.