Add data for 10.2 issues, addressed and known
This commit is contained in:
@@ -0,0 +1,48 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.0-h2
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-237871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
WF-500 appliances and PAN-DB private cloud deployments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
|
|
||||||
|
## PAN-202450
|
||||||
|
|
||||||
|
Fixed an issue where the device-client-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-198372
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.0-h3
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.0-h4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.0
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-231823
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-5916](https://security.paloaltonetworks.com/CVE-2024-5916).
|
||||||
|
|
||||||
|
## PAN-186143
|
||||||
|
|
||||||
|
Fixed an issue where no local changes could be made on a ZTP-enabled device after an upgrade to PAN-OS 10.1.x.
|
||||||
|
|
||||||
|
## PAN-182634
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-400 series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall detected a Power Supply Unit (PSU) failure for the opposite side when disconnecting a PSU from the device. This issue occurred when redundant PSUs were connected.
|
||||||
|
|
||||||
|
## PAN-178165
|
||||||
|
|
||||||
|
Fixed an issue where the CLI command set system setting ctd ctd-agent-assigned-cores 0 to change assigned cores for the ctd-agent failed.
|
||||||
|
|
||||||
|
## PAN-175950
|
||||||
|
|
||||||
|
Fixed an issue where IoT Security (without Strata Logging Service) onboarding failed.
|
||||||
@@ -0,0 +1,52 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.1-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-239241
|
||||||
|
|
||||||
|
Extended the root certificate for WildFire appliances to December 31, 2032.
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-237871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
WF-500 appliances and PAN-DB private cloud deployments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
|
|
||||||
|
## PAN-202450
|
||||||
|
|
||||||
|
Fixed an issue where the device-client-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-198372
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.1-h2
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.1-h3
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
@@ -0,0 +1,59 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h10
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-268823
|
||||||
|
|
||||||
|
Fixed an issue where **Monitor > Log Display** did not display all logs when you applied a filter.
|
||||||
|
|
||||||
|
## PAN-268727
|
||||||
|
|
||||||
|
Fixed an issue where traffic was dropped when the accumulation proxy was enabled and header insertion modified packets.
|
||||||
|
|
||||||
|
## PAN-268314
|
||||||
|
|
||||||
|
Fixed an issue where new files were not sent to WildFire. With this fix, the WildFire reserved drive space has been increased for greater session caching capability.
|
||||||
|
|
||||||
|
## PAN-268002
|
||||||
|
|
||||||
|
Fixed an issue where URL filtering response pages were not displayed for sites that were blocked as a result of SSL/TLS handshake inspection.
|
||||||
|
|
||||||
|
## PAN-267704
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not send an ICMP error packet to Envoy when the MSS was exceeded.
|
||||||
|
|
||||||
|
## PAN-263973
|
||||||
|
|
||||||
|
Fixed an issue where log collectors had a low incoming log rate.
|
||||||
|
|
||||||
|
## PAN-261673
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where, when Accelerated Networking was enabled, traffic was dropped because of the flow_parse_ip_hdr counter related to an Nvidia driver issue.
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Networking Cards (NC) experienced an internal link fault which caused path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-253213
|
||||||
|
|
||||||
|
Fixed an issue where the firewall sent HIP notifications every time it received a HIP report instead of every two hours.
|
||||||
|
|
||||||
|
## PAN-246699
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where **Rule Usage** and **Apps Seen** under Security policy rules stopped incrementing.
|
||||||
|
|
||||||
|
## PAN-233195
|
||||||
|
|
||||||
|
Fixed an issue where logs continued to be ingested when the vldmgr process was restarted.
|
||||||
@@ -0,0 +1,155 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h14
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-279604
|
||||||
|
|
||||||
|
Fixed an issue where scheduled SaaS application usage reports were generated incorrectly, and the login page was displayed instead of the report content.
|
||||||
|
|
||||||
|
## PAN-276822
|
||||||
|
|
||||||
|
Fixed an issue where the packet buffer size increased significantly when WildFire File Forwarding was continued after a threat detection and then canceled.
|
||||||
|
|
||||||
|
## PAN-276177
|
||||||
|
|
||||||
|
Fixed an issue where **App Acceleration** did not work with Oracle databases.
|
||||||
|
|
||||||
|
## PAN-274592
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not fail over when the active firewall experienced data plane issues.
|
||||||
|
|
||||||
|
## PAN-273994
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0111](https://security.paloaltonetworks.com/CVE-2025-0111).
|
||||||
|
|
||||||
|
## PAN-273971
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0108](https://security.paloaltonetworks.com/CVE-2025-0108).
|
||||||
|
|
||||||
|
## PAN-273278
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0109](https://security.paloaltonetworks.com/CVE-2025-0109).
|
||||||
|
|
||||||
|
## PAN-273153
|
||||||
|
|
||||||
|
Fixed an issue where the Panorama web interface was slower than expected due to excessive polling of the MonitorDirect.getTasks API by the Task Manager.
|
||||||
|
|
||||||
|
## PAN-273021
|
||||||
|
|
||||||
|
Fixed an issue where 25G port links did not come up due to a change in the handling of 25G DAC modules.
|
||||||
|
|
||||||
|
## PAN-271926
|
||||||
|
|
||||||
|
Fixed an issue where TLS 1.3 decryption failed with a bad record MAC error when the firewall was configured to decrypt and inspect TLS traffic.
|
||||||
|
|
||||||
|
## PAN-271301
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Amazon Web Services (AWS) environments with GWLB integrated only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where DNS queries timed out when overlay routing was enabled.
|
||||||
|
|
||||||
|
## PAN-270549
|
||||||
|
|
||||||
|
Fixed an issue where some TLS connections were not handled correctly, which led to instability in the dataplane.
|
||||||
|
|
||||||
|
## PAN-269899
|
||||||
|
|
||||||
|
Fixed an issue where the Panorama web interface was slower than expected when querying for device tags.
|
||||||
|
|
||||||
|
## PAN-269731
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not display logs from firewalls after upgrading to PAN-OS 10.2.11 on devices due to Elasticsearch (ES) getting restarted continuously.
|
||||||
|
|
||||||
|
## PAN-269027
|
||||||
|
|
||||||
|
Fixed an issue related to external dynamic lists that caused commit times on the firewall to be higher than expected.
|
||||||
|
|
||||||
|
## PAN-268972
|
||||||
|
|
||||||
|
Fixed an issue where Panorama was slower than expected when using a high number of device group tags in a non-shared context.
|
||||||
|
|
||||||
|
## PAN-268501
|
||||||
|
|
||||||
|
Fixed an issue where the firewall was unable to generate a TSF file due to a full root partition.
|
||||||
|
|
||||||
|
## PAN-268489
|
||||||
|
|
||||||
|
Fixed a Threat log PCAP ID overwrapping issue.
|
||||||
|
|
||||||
|
## PAN-268260
|
||||||
|
|
||||||
|
Fixed an issue on hardware firewalls where, when SSL decryption was enabled and Client Hello messages spanned multiple TCP segments, some SSL decrypted sessions failed.
|
||||||
|
|
||||||
|
## PAN-267781
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not display the Source Dynamic Address Group.
|
||||||
|
|
||||||
|
## PAN-267671
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly due to the all_task process restarting and repeated OOM conditions occurring on the pan_task process.
|
||||||
|
|
||||||
|
## PAN-265791
|
||||||
|
|
||||||
|
Fixed an issue where the all_task process stopped responding, which caused the dataplane to go down.
|
||||||
|
|
||||||
|
## PAN-265179
|
||||||
|
|
||||||
|
Fixed an issue where a kernel race condition caused the firewall to reboot with a kernel panic.
|
||||||
|
|
||||||
|
## PAN-262627
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted into maintenance mode due to a service failure in the configd process.
|
||||||
|
|
||||||
|
## PAN-261739
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall displayed 0 for the physical port counters read from MAC.
|
||||||
|
|
||||||
|
## PAN-261074
|
||||||
|
|
||||||
|
Fixed an issue where the firewall delayed video file transfers over SMB when **Exclude Video Traffic** from the Tunnel feature was enabled and no applications were added to the list.
|
||||||
|
|
||||||
|
## PAN-260827
|
||||||
|
|
||||||
|
Fixed an issue where the firewall consumed excessive CPU while processing traffic for a workload running on a GKE cluster, which caused reduced throughput.
|
||||||
|
|
||||||
|
## PAN-260090
|
||||||
|
|
||||||
|
Fixed an issue where commit all operations failed when the application openair-psa was used as a keyword on a remote network instance that was upgraded to PAN-OS 10.2.4-h20.
|
||||||
|
|
||||||
|
## PAN-259727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Panorama became unresponsive and displayed a 504 gateway timeout error when accessing the web interface or the CLI.
|
||||||
|
|
||||||
|
## PAN-246304
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where commits failed due to a timeout in the sysd process during decryption.
|
||||||
|
|
||||||
|
## PAN-239952
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in active/passive HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where HA sync messages from the active firewall took longer than expected to reach the passive firewall.
|
||||||
|
|
||||||
|
## PAN-222484
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-5920](https://security.paloaltonetworks.com/CVE-2024-5920).
|
||||||
@@ -0,0 +1,203 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h17
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-282236
|
||||||
|
|
||||||
|
Fixed an issue where large IPv6 packets were reassembled incorrectly on the firewall when the packets arrived fragmented over an IPv4 tunnel.
|
||||||
|
|
||||||
|
## PAN-277234
|
||||||
|
|
||||||
|
Fixed an issue where a device group import resulted in a Security policy rule being created with **Application** set to **none**.
|
||||||
|
|
||||||
|
## PAN-277135
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding when a DNS client closed or reset a TCP connection while the firewall was sending a response.
|
||||||
|
|
||||||
|
## PAN-276607
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect users experienced DNS resolution timeouts when using Prisma Access.
|
||||||
|
|
||||||
|
## PAN-274570
|
||||||
|
|
||||||
|
Fixed an issue where the devsrvr process restarted after a failed commit due to an invalid memory access.
|
||||||
|
|
||||||
|
## PAN-273453
|
||||||
|
|
||||||
|
Fixed an issue where restarting the firewall did not initiate an autocommit job, which caused the firewall to stop responding and the HA interface to go down.
|
||||||
|
|
||||||
|
## PAN-272395
|
||||||
|
|
||||||
|
Fixed an issue where informational logs caused the distributord process log file to be frequently overwritten.
|
||||||
|
|
||||||
|
## PAN-271507
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the DPC on slot 3 intermittently stopped responding due an all_pktproc restart.
|
||||||
|
|
||||||
|
## PAN-271351
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0116](https://security.paloaltonetworks.com/CVE-2025-0116).
|
||||||
|
|
||||||
|
## PAN-271184
|
||||||
|
|
||||||
|
Fixed an issue where Device Telemetry failed due to an issue with the encoding of characters in the log file path.
|
||||||
|
|
||||||
|
## PAN-269677
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not check for a NULL pointer when querying logs, which caused logs to not display on the web interface.
|
||||||
|
|
||||||
|
## PAN-269106
|
||||||
|
|
||||||
|
Fixed an issue where the wifclient stopped responding during server certificate verification for MICA gRPC connections and caused the dataplane to restart when using a cloud-based ML detection engine (MICA). On certain platforms, this caused the firewall to reboot periodically.
|
||||||
|
|
||||||
|
## PAN-268823
|
||||||
|
|
||||||
|
Fixed an issue where **Monitor > Log Display** did not display all logs when you applied a filter.
|
||||||
|
|
||||||
|
## PAN-267097
|
||||||
|
|
||||||
|
Fixed an issue where the replay database size increased significantly due to local and special configurations not being purged after commits.
|
||||||
|
|
||||||
|
## PAN-266695
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where a cyclic nested address group configuration caused the configd process to stop responding after a commit.
|
||||||
|
|
||||||
|
## PAN-266427
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where, when a high number of SD-WAN branch sites or interfaces were not connected, SD-WAN processes and tund processes stopped responding due to a high probing rate.
|
||||||
|
|
||||||
|
## PAN-265900
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding due to a tund process or SD-WAN process restart.
|
||||||
|
|
||||||
|
## PAN-264883
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7080 appliances with LPCs only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where syslog forwarding over TCP stopped after upgrading.
|
||||||
|
|
||||||
|
## PAN-264708
|
||||||
|
|
||||||
|
Fixed an issue where a selective push was blocked when a configuration load was done.
|
||||||
|
|
||||||
|
## PAN-264678
|
||||||
|
|
||||||
|
Fixed an issue where **Preview Changes** did not display configuration changes in **Commit and push** > **Push Scope**.
|
||||||
|
|
||||||
|
## PAN-263369
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Internal error during commit processing. Commit/Validate failed
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where commits from Panorama to Panorama virtual appliances failed with the error message after upgrading Panorama.
|
||||||
|
|
||||||
|
## PAN-262831
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400f Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an intermittent issue where the all_task process stopped responding, which caused the firewall to restart.
|
||||||
|
|
||||||
|
## PAN-262540
|
||||||
|
|
||||||
|
Fixed an issue where application traffic transactions that reused TCP ports did not work with decryption.
|
||||||
|
|
||||||
|
## PAN-261673
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where, when Accelerated Networking was enabled, traffic was dropped because of the flow_parse_ip_hdr counter related to an Nvidia driver issue.
|
||||||
|
|
||||||
|
## PAN-260218
|
||||||
|
|
||||||
|
Fixed an issue where BGP Aggregate Advertise filters did not work as expected when the summary option was enabled, and only summarized routes were advertised.
|
||||||
|
|
||||||
|
## PAN-259351
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3393](https://security.paloaltonetworks.com/CVE-2024-3393).
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Networking Cards (NC) experienced an internal link fault which caused path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-256738
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where BGP routes from the active firewall were lost when the passive firewall was rebooted.
|
||||||
|
|
||||||
|
## PAN-256223
|
||||||
|
|
||||||
|
Fixed an issue where device telemetry log collection filled the root partition.
|
||||||
|
|
||||||
|
## PAN-255323
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the Network Processing Card (NPC), Data Processing Card (DPC), and Log forwarding Card (LFC) remained in a starting state after an unexpected power cycle.
|
||||||
|
|
||||||
|
## PAN-254422
|
||||||
|
|
||||||
|
Fixed an issue where the firewall required a restart when an SD-WAN policy rule was pushed from Panorama.
|
||||||
|
|
||||||
|
## PAN-254403
|
||||||
|
|
||||||
|
Fixed an issue where not all syslog logs were displayed in **Monitor** > **Monitor** > **System** when FIPS mode was enabled.
|
||||||
|
|
||||||
|
## PAN-254241
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding due to a high number of SD-WAN probes being sent.
|
||||||
|
|
||||||
|
## PAN-252300
|
||||||
|
|
||||||
|
Fixed an issue where you were unable to select device groups in the push scope for user accounts.
|
||||||
|
|
||||||
|
## PAN-249384
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where configuration locks were observed during a partial rulebase commit.
|
||||||
|
|
||||||
|
## PAN-249011
|
||||||
|
|
||||||
|
Fixed an issue where the firewall became unresponsive when committing a configuration change with a large number of uncommitted changes in the replay database.
|
||||||
|
|
||||||
|
## PAN-243240
|
||||||
|
|
||||||
|
Fixed an issue where the using QoS caused packet buffer utilization to increase exponentially and the PKI POOL DFLT pool depleted until a reboot was performed.
|
||||||
|
|
||||||
|
## PAN-242479
|
||||||
|
|
||||||
|
Fixed an issue where a high number of packets caused high packet descriptors on the firewall when handling EtherIP traffic.
|
||||||
|
|
||||||
|
## PAN-238286
|
||||||
|
|
||||||
|
Fixed an issue where FTP control connections were lost after an HA failover event.
|
||||||
|
|
||||||
|
## PAN-230893
|
||||||
|
|
||||||
|
Added a CLI command to address an issue where system lock files blocked authentication.
|
||||||
|
|
||||||
|
## PAN-193285
|
||||||
|
|
||||||
|
Fixed an issue where the policy optimizer feature did not add entries back to the mongodb database after removing them during an upgrade or downgrade.
|
||||||
@@ -0,0 +1,141 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h18
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-286255
|
||||||
|
|
||||||
|
Fixed an issue where, when the firewall received an unexpected termination request for SSL sessions, the dataplane experienced a slow buffer resource leak.
|
||||||
|
|
||||||
|
## PAN-283813
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the web interface performance was slower than usual when retrieving read-only configurations from Panorama.
|
||||||
|
|
||||||
|
## PAN-279400
|
||||||
|
|
||||||
|
Fixed an issue where, when **Restrict Certificate Extensions** was enabled on decryption profiles, the basic constraints extension was overwritten incorrectly.
|
||||||
|
|
||||||
|
## PAN-278150
|
||||||
|
|
||||||
|
Fixed an issue where the firewall removed the Authentication Key Identifier (AKID) from the certificate during SSL decryption, which caused Python 3.13 to fail with a certificate verification error.
|
||||||
|
|
||||||
|
## PAN-277417
|
||||||
|
|
||||||
|
Fixed an memory leak issue related to TLS inbound decryption.
|
||||||
|
|
||||||
|
## PAN-277147
|
||||||
|
|
||||||
|
Fixed an issue where daily scheduled reports were not generated and emailed.
|
||||||
|
|
||||||
|
## PAN-276692
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not install a Pay-as-you-go (PAYG) license if the check failed.
|
||||||
|
|
||||||
|
## PAN-276678
|
||||||
|
|
||||||
|
Fixed an issue where Panorama became unresponsive while performing a dynamic address update without a lock.
|
||||||
|
|
||||||
|
## PAN-271425
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in active/active high availability (HA) configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue with SSL inbound decryption on firewalls on a vwire setup with asymmetric routing.
|
||||||
|
|
||||||
|
To use this fix, enter the CLI command set system setting ssl-decrypt ha-vwire-mac-learn global yes on both firewalls in an HA pair.
|
||||||
|
|
||||||
|
## PAN-269956
|
||||||
|
|
||||||
|
Fixed an issue where the all_pktproc process stopped responding, which caused internal path monitor failures.
|
||||||
|
|
||||||
|
## PAN-269700
|
||||||
|
|
||||||
|
Fixed an issue where commits to service connection firewalls from Panorama failed.
|
||||||
|
|
||||||
|
## PAN-269499
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding when receiving a high number of logs.
|
||||||
|
|
||||||
|
## PAN-269291
|
||||||
|
|
||||||
|
Fixed an issue where the scheduled report generation script did not return debug information.
|
||||||
|
|
||||||
|
## PAN-265646
|
||||||
|
|
||||||
|
Fixed an issue where the config lock icon was not visible for a custom role-based admin when a Superuser admin had acquired the config lock.
|
||||||
|
|
||||||
|
## PAN-264169
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall sent correlated event logs to the syslog server using the management interface instead of the log interface.
|
||||||
|
|
||||||
|
## PAN-263291
|
||||||
|
|
||||||
|
Fixed an issue where Microsoft Outlook did not work as expected when the GlobalProtect clientless VPN was configured.
|
||||||
|
|
||||||
|
## PAN-262946
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where logging in via the CLI or web interface did not work due to increased memory usage.
|
||||||
|
|
||||||
|
## PAN-260564
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in HA configurations where a network loop was detected by switches after suspending HA on the active firewall.
|
||||||
|
|
||||||
|
## PAN-257432
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the reportd process stopped responding, which caused a log query issue.
|
||||||
|
|
||||||
|
## PAN-256666
|
||||||
|
|
||||||
|
Fixed an issue where the configd process stopped responding when **Commit and Push** operations were performed on multiple device groups.
|
||||||
|
|
||||||
|
## PAN-256115
|
||||||
|
|
||||||
|
Fixed an issue where, after replacing a Panorama appliance or log collector, the secondary Panorama appliance or log collector displayed a **disconnected** status for the inter-log collector connection.
|
||||||
|
|
||||||
|
## PAN-254524
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where, when the **Commit and Push** button was clicked during a selective **Commit and Push** operation, the window stopped responding, which caused the operation to be delayed.
|
||||||
|
|
||||||
|
## PAN-254174
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0115](https://security.paloaltonetworks.com/CVE-2025-0115).
|
||||||
|
|
||||||
|
## PAN-251929
|
||||||
|
|
||||||
|
Fixed an issue where inbound decryption did not work when FIPS self tests were turned on.
|
||||||
|
|
||||||
|
## PAN-244227
|
||||||
|
|
||||||
|
Fixed an issue where inconsistent FIB entries across the dataplane were not detected.
|
||||||
|
|
||||||
|
## PAN-241547
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2023-48795](https://security.paloaltonetworks.com/CVE-2023-48795).
|
||||||
|
|
||||||
|
## PAN-238594
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted when a QSFP28 cable was removed from the port while the port was passing traffic.
|
||||||
|
|
||||||
|
## PAN-237010
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where local commits took longer than expected after an upgrade.
|
||||||
|
|
||||||
|
## PAN-233868
|
||||||
|
|
||||||
|
Fixed an issue where the firewall took an incorrect action for overlapping custom and edl-url-categories in a policy rule.
|
||||||
|
|
||||||
|
## PAN-224833
|
||||||
|
|
||||||
|
Fixed an issue where the firewall dropped DHCPv6 relay packets if there were duplicate link-local addresses on different sub-interfaces.
|
||||||
|
|
||||||
|
## PAN-214177
|
||||||
|
|
||||||
|
Fixed an issue where template configurations were not properly pushed to the firewall during an export or push of the device configuration bundle.
|
||||||
@@ -0,0 +1,253 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h21
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-291060
|
||||||
|
|
||||||
|
Fixed an issue where commits failed due to the configured connected gateway IPv6 address in the NAT64 policy exceeding the 31 character limit.
|
||||||
|
|
||||||
|
## PAN-288930
|
||||||
|
|
||||||
|
Fixed an issue where, when ACE was enabled, traffic from cloud applications randomly matched an incorrect **cloud-apps** policy rule.
|
||||||
|
|
||||||
|
## PAN-286475
|
||||||
|
|
||||||
|
Fixed an issue where the option to sort sequence numbers was missing from **Filters prefix list** in the advanced routing filters.
|
||||||
|
|
||||||
|
## PAN-284908
|
||||||
|
|
||||||
|
Fixed an issue where retrieving filenames from OneDrive resulted in a cache miss.
|
||||||
|
|
||||||
|
## PAN-284552
|
||||||
|
|
||||||
|
Fixed an intermittent issue where gateway logout events were not logged when the GlobalProtect client was unable to send a logout notification, which resulted in the inactivity logout timer not triggering a gateway logout event. This caused user sessions to remain active beyond the configured inactivity timeout.
|
||||||
|
|
||||||
|
## PAN-284116
|
||||||
|
|
||||||
|
Fixed an issue where mTLS decryption bypass did not work when the decryption profile was configured with the maximum TLS version as TLS 1.3.
|
||||||
|
|
||||||
|
## PAN-283644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Prisma Access only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where URL log ingestion decreased after an upgrade, and secondary connections were lost.
|
||||||
|
|
||||||
|
## PAN-282640
|
||||||
|
|
||||||
|
Fixed an issue where custom reports showed incomplete data when exported in CSV format from Panorama.
|
||||||
|
|
||||||
|
## PAN-280698
|
||||||
|
|
||||||
|
Fixed an issue where the firewall removed the TCP timestamp from client hello messages that did not fit in a single packet, which resulted in connection issues.
|
||||||
|
|
||||||
|
## PAN-280505
|
||||||
|
|
||||||
|
Fixed an issue where the web interface did not display a message to commit prior changes before attempting a partial configuration load.
|
||||||
|
|
||||||
|
## PAN-280409
|
||||||
|
|
||||||
|
Fixed an issue where the popup window did not appear as expected for Clientless VPN users.
|
||||||
|
|
||||||
|
## PAN-279621
|
||||||
|
|
||||||
|
Fixed an issue where processes stopped responding when HTTPS Forward traffic was run.
|
||||||
|
|
||||||
|
## PAN-279495
|
||||||
|
|
||||||
|
Fixed an issue where accessing a URL from the browser returned the error message ERR_RESPONSE_HEADERS_TRUNCATED when the firewall was configured with TLS 1.3.
|
||||||
|
|
||||||
|
## PAN-279336
|
||||||
|
|
||||||
|
Fixed an issue where the CLI did not display a message to commit prior changes before loading a partial configuration.
|
||||||
|
|
||||||
|
## PAN-279176
|
||||||
|
|
||||||
|
Fixed an issue where the configuration audit displayed inaccurate information after partially loading the configuration via the CLI, which caused the audit to flag the configuration as deleted or changed.
|
||||||
|
|
||||||
|
## PAN-278812
|
||||||
|
|
||||||
|
Fixed an issue where authentication to GlobalProtect failed with the error message User not in allowed list.
|
||||||
|
|
||||||
|
## PAN-277617
|
||||||
|
|
||||||
|
Fixed an issue where deleting the NTP server address caused a commit validation error. This occurred when the configuration included both primary and secondary NTP servers and the secondary server was removed.
|
||||||
|
|
||||||
|
## PAN-276016
|
||||||
|
|
||||||
|
Fixed an issue where Prisma Access cap700 instances did not insert HTTP headers when accessing certain Google domains if the 32 byte pool size was low.
|
||||||
|
|
||||||
|
## PAN-273949
|
||||||
|
|
||||||
|
Fixed an issue where the firewall generated the following error message in the snmpd logs: pan_get_keystr_from_cryptod
|
||||||
|
|
||||||
|
(pan_snmpinterface.c:181): Key X2F1dGhfa2V5 import from cryptod failed.
|
||||||
|
|
||||||
|
## PAN-272539
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where user to IP address mapping was missing for some users connected to specific Prisma Access gateways, which caused the collection layer Azure firewall to not form the mapping.
|
||||||
|
|
||||||
|
## PAN-271432
|
||||||
|
|
||||||
|
Fixed an issue where the firewall was unable to decrypt SSL traffic when using forward proxy and HSM with an ECDSA signing certificate.
|
||||||
|
|
||||||
|
## PAN-270849
|
||||||
|
|
||||||
|
Fixed a memory leak issue related to the configd process that occurred when running consecutive commits for multiple days.
|
||||||
|
|
||||||
|
## PAN-269624
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect clients failed to connect with the error message The device or feature requires a GlobalProtect subscription license.
|
||||||
|
|
||||||
|
## PAN-268909
|
||||||
|
|
||||||
|
Fixed an issue where IP address tags were removed from firewalls after a management server or useridd process restart. This occurred when a Panorama serial-number based configuration was used for User-ID redistribution.
|
||||||
|
|
||||||
|
## PAN-268708
|
||||||
|
|
||||||
|
Fixed an issue where PDF summary and email reports displayed IPv6 addresses instead of IPv4 addresses.
|
||||||
|
|
||||||
|
## PAN-268614
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where, when all rules were highlighted when a read-only admin user clicked the **Highlight Unused Rules** checkbox.
|
||||||
|
|
||||||
|
## PAN-268017
|
||||||
|
|
||||||
|
Fixed an issue where the IP address-to-user mapping timeout was triggered and the Inactivity TTL was refreshed unexpectedly
|
||||||
|
|
||||||
|
## PAN-265782
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where, after you enabled multihop in a BFD profile, you were unable to disable it via the web interface.
|
||||||
|
|
||||||
|
## PAN-264883
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7080 appliances with LPCs only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where syslog forwarding over TCP stopped after upgrading.
|
||||||
|
|
||||||
|
## PAN-260796
|
||||||
|
|
||||||
|
Fixed an issue where servers were not accessible through an active SSL GlobalProtect VPN tunnel until a new connection was established or the session was cleared on the firewall.
|
||||||
|
|
||||||
|
## PAN-260132
|
||||||
|
|
||||||
|
Fixed an issue where secondary IP addresses with a /32 prefix configured on Layer 3 interfaces were not reachable in FRR mode.
|
||||||
|
|
||||||
|
## PAN-259759
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0125](https://security.paloaltonetworks.com/CVE-2025-0125).
|
||||||
|
|
||||||
|
## PAN-257624
|
||||||
|
|
||||||
|
Fixed an issue where the firewall web interface was blank after logging in.
|
||||||
|
|
||||||
|
## PAN-257117
|
||||||
|
|
||||||
|
Fixed an issue where CSV or PDF exports of zones did not contain all zones.
|
||||||
|
|
||||||
|
## PAN-255759
|
||||||
|
|
||||||
|
Fixed an issue where the firewall was unable to match HIP data with the correct anti-malware object for Windows Defender.
|
||||||
|
|
||||||
|
## PAN-255252
|
||||||
|
|
||||||
|
Fixed an issue where Panorama administrators with the type Dynamic were unable to create, modify, or delete BGP Dampening profiles.
|
||||||
|
|
||||||
|
## PAN-253829
|
||||||
|
|
||||||
|
Fixed an issue where the CLI command show running security-policy timed out when the Security policy was large.
|
||||||
|
|
||||||
|
## PAN-253584
|
||||||
|
|
||||||
|
Fixed an issue where ikemgr process unexpectedly stopped due to a memory mapping in an incorrect location.
|
||||||
|
|
||||||
|
## PAN-252974
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where specific routes were not advertised when BGP Aggregate was configured with the advertise filter.
|
||||||
|
|
||||||
|
## PAN-252270
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where changes were incorrectly applied after a reboot or a restart of the configd process.
|
||||||
|
|
||||||
|
## PAN-249581
|
||||||
|
|
||||||
|
Fixed an issue where stale BGP routes were advertised to peers even when they were not present in the local RIB table.
|
||||||
|
|
||||||
|
## PAN-248975
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where no content was displayed after logging in.
|
||||||
|
|
||||||
|
## PAN-243333
|
||||||
|
|
||||||
|
Fixed an issue where selective push operations failed with the following error message: SelPush:Base config is invalid! invalid configuration. Schema verification failed. This occurred when a policy rule was moved from the post-rule base to the pre-rule base.
|
||||||
|
|
||||||
|
## PAN-241230
|
||||||
|
|
||||||
|
Fixed an issue where the SNMP get request status value for Panorama connections was incorrect.
|
||||||
|
|
||||||
|
## PAN-240001
|
||||||
|
|
||||||
|
Fixed an issue where the pan_task process restarted due to configd and devsrvr process memory requirements.
|
||||||
|
|
||||||
|
## PAN-239256
|
||||||
|
|
||||||
|
Fixed an issue where ARP entries were unable to be completed for subinterfaces with SNAT configured.
|
||||||
|
|
||||||
|
## PAN-238610
|
||||||
|
|
||||||
|
Fixed an issue with the Panorama Virtual Appliance where, after the mgmtsrvr restarted on the passive appliance, stale IP address tags were pushed to the connected firewalls with the message clear all registered ip addresses.
|
||||||
|
|
||||||
|
## PAN-237582
|
||||||
|
|
||||||
|
Fixed an issue where logs were intermittently missing on the log collector due to missing aliases for some indices.
|
||||||
|
|
||||||
|
## PAN-237475
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding when FIPS mode was enabled.
|
||||||
|
|
||||||
|
## PAN-232530
|
||||||
|
|
||||||
|
Fixed an issue where the useridd process ran out of memory and restarted when the number of user or user groups exceeded the threshold.
|
||||||
|
|
||||||
|
## PAN-230330
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where disk space usage was significantly higher than expected after upgrading.
|
||||||
|
|
||||||
|
## PAN-224729
|
||||||
|
|
||||||
|
Fixed an issue where you were unable to create duplicate entries in Advanced Routing AS path prepend in the BGP filter route map.
|
||||||
|
|
||||||
|
## PAN-224195
|
||||||
|
|
||||||
|
Fixed an issue where Captive Portal redirects failed with a 500 Internal error when the captive portal token was disabled.
|
||||||
|
|
||||||
|
## PAN-222579
|
||||||
|
|
||||||
|
Fixed an issue where the useridd and distd process restarted, which resulted in missing mappings.
|
||||||
|
|
||||||
|
## PAN-221571
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where the Security policy rule hit count remained at 0 for some rules even though the traffic logs showed live hits.
|
||||||
|
|
||||||
|
## PAN-212182
|
||||||
|
|
||||||
|
Fixed an issue where TLS 1.3 connections failed if the server sent a certificate request after sending its certificate.
|
||||||
@@ -0,0 +1,95 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
Fixed an issue where decryption based traffic failed on Explicit Proxy nodes.
|
||||||
|
|
||||||
|
## PAN-263164
|
||||||
|
|
||||||
|
Fixes a problem where Netflow User ID information was truncated to 31 characters.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
Fixed an issue where dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261917
|
||||||
|
|
||||||
|
Fixed an issue where websites with a no-decrypt policy rule were decrypted in traffic log when using a Google Chrome browser with PQC enabled
|
||||||
|
|
||||||
|
## PAN-261797
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls and Panorama appliances in FIPS-CC mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the authd process restarted if RADIUS PAP/CHAP authentication was used.
|
||||||
|
|
||||||
|
## PAN-261270
|
||||||
|
|
||||||
|
Fixed an issue where the firewall decremented the TTL/Hop limit for BGPv6 packets by 1 after IPSec decryption.
|
||||||
|
|
||||||
|
## PAN-260662
|
||||||
|
|
||||||
|
Fixed an issue where large file downloads were slower than expected when private IP address visibility was enabled.
|
||||||
|
|
||||||
|
## PAN-258442
|
||||||
|
|
||||||
|
Fixed an issue where changes made to the split tunnel configuration on the Prisma Access gateway were not reflected on the GlobalProtect client.
|
||||||
|
|
||||||
|
## PAN-257957
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls and Panorama appliances in FIPS-CC mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the authd process restarted if RADIUS PAP/CHAP authentication was used.
|
||||||
|
|
||||||
|
## PAN-257563
|
||||||
|
|
||||||
|
Fixed an issue where the logrcvr component for SASE and MCW displayed incorrect zones in the traffic flow.
|
||||||
|
|
||||||
|
## PAN-256223
|
||||||
|
|
||||||
|
Fixed an issue where device telemetry log collection filled the root partition.
|
||||||
|
|
||||||
|
## PAN-255619
|
||||||
|
|
||||||
|
Fixed an intermittent issue where file downloads from websites failed.
|
||||||
|
|
||||||
|
## PAN-254826
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding when processing traffic.
|
||||||
|
|
||||||
|
## PAN-254671
|
||||||
|
|
||||||
|
Fixed an issue where excessive Timed out while getting config lock error messages were generated when making bulk changes via XML API.
|
||||||
|
|
||||||
|
## PAN-250371
|
||||||
|
|
||||||
|
Fixed an issue where the logrcvr process stopped responding, which caused commits to fail with the error message Management server failed to send phase 1 to client logrcvr.
|
||||||
|
|
||||||
|
## PAN-247257
|
||||||
|
|
||||||
|
Fixed an issue where the useridd process stopped responding, which caused the firewall to reboot.
|
||||||
|
|
||||||
|
## PAN-242958
|
||||||
|
|
||||||
|
Fixed an issue where the firewall intermittently logged connect-agent-failure messages for service connection instances due to bi-directional host ID redistribution.
|
||||||
|
|
||||||
|
## PAN-242331
|
||||||
|
|
||||||
|
Fixed an issue where Prisma Access remote network firewalls intermittently created incorrect user-to-IP-address mappings.
|
||||||
|
|
||||||
|
## PAN-240990
|
||||||
|
|
||||||
|
Fixed an issue where l3svc.py displayed incorrect logs.
|
||||||
|
|
||||||
|
## PAN-218873
|
||||||
|
|
||||||
|
Fixed an issue where a HIP mask was reused when an existing IP address user mapping was updated by a new IP address user mapping that had a different username but the same IP address.
|
||||||
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h5
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-256077
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect client would disconnect consistently due to keep-alive timeouts when using an SSL-only tunnel.
|
||||||
|
|
||||||
|
## PAN-241044
|
||||||
|
|
||||||
|
Fixed an issue where traffic was denied by the interzone-default policy rule when a Security policy rule with an FQDN destination was configured.
|
||||||
|
|
||||||
|
## PAN-222590
|
||||||
|
|
||||||
|
Fixed an issue where a semicolon appeared at the end of file names of data filtering logs.
|
||||||
|
|
||||||
|
## PAN-217198
|
||||||
|
|
||||||
|
Fixed an issue where Security policy rules did not display values for FQDN.
|
||||||
|
|
||||||
|
## PAN-203231
|
||||||
|
|
||||||
|
Fixed an issue where **Software Version** in the device summary report exported from Panorama included HTML tags.
|
||||||
@@ -0,0 +1,111 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h7
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-267662
|
||||||
|
|
||||||
|
Fixed an issue where the firewall experienced a memory out-of-bounds access when the firewall was configured with SD-WAN and the SD-WAN plugin was loading, which caused the firewall to stop responding and drop VPN tunnels.
|
||||||
|
|
||||||
|
## PAN-266769
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect gateway did not handle IP address changes of the inner gateway when the NGPA new protocol enabled.
|
||||||
|
|
||||||
|
## PAN-265742
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where the **OK** button on the GlobalProtect gateway configuration dialog box was not clickable.
|
||||||
|
|
||||||
|
## PAN-265462
|
||||||
|
|
||||||
|
Fixed an issue where you were unable to download PDFs when connected via Clientless VPN.
|
||||||
|
|
||||||
|
## PAN-264871
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the configd process stopped responding when viewing IP addresses on dynamic address groups with a large number of IP addresses.
|
||||||
|
|
||||||
|
## PAN-264246
|
||||||
|
|
||||||
|
Fixed an issue where the Authentication Portal did not work properly with session cookies when the request to the portal contained the header Sec-Fetch-Site=cross-site.
|
||||||
|
|
||||||
|
## PAN-263680
|
||||||
|
|
||||||
|
Fixed an issue where Prisma Access gateways consistently stopped responding with process restarts.
|
||||||
|
|
||||||
|
## PAN-262340
|
||||||
|
|
||||||
|
Fixed an issue where FQDN resolution failed for address objects, and all FQDN traffic was denied by the interzone-default policy rule.
|
||||||
|
|
||||||
|
## PAN-261484
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where DPDK allocated twice the amount of memory as requested for pre-allocation.
|
||||||
|
|
||||||
|
## PAN-260928
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect failed to connect connect when using LDAP authentication with machine certificates with the error message You are not authorized to connect to GlobalProtect portal.
|
||||||
|
|
||||||
|
## PAN-260512
|
||||||
|
|
||||||
|
Fixed an issue where accessing the IP address of the device address group objects from the user interface caused the configd process to stop responding.
|
||||||
|
|
||||||
|
## PAN-259002
|
||||||
|
|
||||||
|
Fixed an issue where frequent external dynamic list updates caused the configd process to restart.
|
||||||
|
|
||||||
|
## PAN-257736
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where traffic to benign applications was was impacted by holding TCP sequential segments for MLC inspection and not releasing the full chain after a benign verdict was received.
|
||||||
|
|
||||||
|
## PAN-256077
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect client would disconnect consistently due to keep-alive timeouts when using an SSL-only tunnel.
|
||||||
|
|
||||||
|
## PAN-255619
|
||||||
|
|
||||||
|
Fixed an intermittent issue where file downloads from websites failed.
|
||||||
|
|
||||||
|
## PAN-255509
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions flapped intermittently.
|
||||||
|
|
||||||
|
## PAN-250787
|
||||||
|
|
||||||
|
Fixed an issue where network issues between the firewall and the log collector caused logrcvr process memory exhaustion.
|
||||||
|
|
||||||
|
## PAN-250394
|
||||||
|
|
||||||
|
Fixed an issue where a large amount of group data caused serialization errors and prevented synchronization.
|
||||||
|
|
||||||
|
## PAN-241044
|
||||||
|
|
||||||
|
Fixed an issue where traffic was denied by the interzone-default policy rule when a Security policy rule with an FQDN destination was configured.
|
||||||
|
|
||||||
|
## PAN-233681
|
||||||
|
|
||||||
|
Fixed an issue where the authd process on Prisma Access firewalls stopped responding after receiving the SIGUSR1 signal.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions might end unexpectedly with the error resources-unavailable when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-222590
|
||||||
|
|
||||||
|
Fixed an issue where a semicolon appeared at the end of file names of data filtering logs.
|
||||||
|
|
||||||
|
## PAN-217198
|
||||||
|
|
||||||
|
Fixed an issue where Security policy rules did not display values for FQDN.
|
||||||
|
|
||||||
|
## PAN-203231
|
||||||
|
|
||||||
|
Fixed an issue where **Software Version** in the device summary report exported from Panorama included HTML tags.
|
||||||
@@ -0,0 +1,43 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h9
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
|
|
||||||
|
## PAN-268314
|
||||||
|
|
||||||
|
Fixed an issue where new files were not sent to WildFire. With this fix, the WildFire reserved drive space has been increased for greater session caching capability.
|
||||||
|
|
||||||
|
## PAN-267535
|
||||||
|
|
||||||
|
Fixed an issue where all_task processes stopped responding on the remote network firewall, which caused tunnels to go down and the pan_task CPU usage to approach 100%.
|
||||||
|
|
||||||
|
## PAN-265778
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect client failed to connect after an upgrade due to the group names not being retrieved on time.
|
||||||
|
|
||||||
|
## PAN-265399
|
||||||
|
|
||||||
|
Fixed an issue where DNS queries for uppercase internal domain (SRV record) timed out when DNS Security was enabled.
|
||||||
|
|
||||||
|
## PAN-255915
|
||||||
|
|
||||||
|
Fixed an issue where a memory leak in the sslmgr process caused the firewall to restart.
|
||||||
|
|
||||||
|
## PAN-240251
|
||||||
|
|
||||||
|
Fixed an issue where the vldmgr process incorrectly restarted during an Elasticsearch restart.
|
||||||
|
|
||||||
|
## PAN-232368
|
||||||
|
|
||||||
|
Fixed an issue where commits failed with the error message Error: Max. user groups used in policy 1389 exceed capacity (1000).
|
||||||
|
|
||||||
|
## PAN-218279
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where hostname variables displayed as **unknown** when exporting template or template stack variables in CSV format.
|
||||||
@@ -0,0 +1,235 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-257197
|
||||||
|
|
||||||
|
Fixed an issue where ifType and ifSpeed were not populated in asynchronous mode of SNMP operations.
|
||||||
|
|
||||||
|
## PAN-256181
|
||||||
|
|
||||||
|
Fixed an issue where the management interface and front panel port interface statistics were not populated in asynchronous mode of SNMP operations.
|
||||||
|
|
||||||
|
## PAN-255868
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall entered maintenance mode after enabling kernel data collection during the silent reboot.
|
||||||
|
|
||||||
|
## PAN-255396
|
||||||
|
|
||||||
|
Fixed an issue where, when using serial number and IP address authentication, and multiple gateways were configured, the portal returned the last gateway in the list and disregarded the satellite assignment by serial number.
|
||||||
|
|
||||||
|
## PAN-253546
|
||||||
|
|
||||||
|
Fixed an issue where a TLS client hello was split into multiple packets and arrived out of order, so the packets were dropped and the session terminated.
|
||||||
|
|
||||||
|
## PAN-253317
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where you were unable to log in to the firewall after a private data reset.
|
||||||
|
|
||||||
|
## PAN-252730
|
||||||
|
|
||||||
|
Fixed an issue where the Elasticsearch status for a log collector group changed to red or yellow after performing a collector group push.
|
||||||
|
|
||||||
|
## PAN-252517
|
||||||
|
|
||||||
|
Fixed an issue where SNMP failed to respond to multiple Object Identifier (OID) queries in a single SNMP GET request.
|
||||||
|
|
||||||
|
## PAN-251895
|
||||||
|
|
||||||
|
Fixed an issue where enabling inline Cloud Analysis features caused a slow packet buffer leak, which resulted in performance issues and dropped traffic.
|
||||||
|
|
||||||
|
## PAN-251639
|
||||||
|
|
||||||
|
Fixed an issue where an out of memory condition might occur due to a memory leak in the varrcvr process when a Wildfire Analysis security profile is enabled.
|
||||||
|
|
||||||
|
## PAN-251563
|
||||||
|
|
||||||
|
Added CPLD enhancement to capture external power issues.
|
||||||
|
|
||||||
|
## PAN-251013
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where the **Virtual Router** and **Virtual System** configurations for the template incorrectly showed as **none**.
|
||||||
|
|
||||||
|
## PAN-250083
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in HA configurations where packets were dropped over HA3 HSCI due to the default MRU being incorrect.
|
||||||
|
|
||||||
|
## PAN-250020
|
||||||
|
|
||||||
|
Fixed an issue where MLC2 verdict retrieval failed due to a regression in loopback data flag handling.
|
||||||
|
|
||||||
|
## PAN-248130
|
||||||
|
|
||||||
|
Fixed an issue where the **AND** operation under a Dynamic Address Group comparison did not work after upgrading the AWS plugin to 3.0.1.
|
||||||
|
|
||||||
|
## PAN-248105
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect SSL VPN tunnel immediately disconnected due to a keep-alive timeout.
|
||||||
|
|
||||||
|
## PAN-246976
|
||||||
|
|
||||||
|
Fixed an issue with unbalanced NAT session distribution with multidataplane firewalls when persistent-dipp was enabled.
|
||||||
|
|
||||||
|
## PAN-246960
|
||||||
|
|
||||||
|
Fixed an issue where firewalls failed to fetch content updates from the WildFire private cloud due to an **Unsupported protocol** error.
|
||||||
|
|
||||||
|
## PAN-245850
|
||||||
|
|
||||||
|
Fixed an issue on Panorama appliances in active/passive HA configurations where the firewalls entered an HA out-of-sync status and jobs failed on the passive appliance with the error message Could not merged running config from file.
|
||||||
|
|
||||||
|
## PAN-245842
|
||||||
|
|
||||||
|
Fixed an issue with the syn-cookie option where traffic unexpectedly stopped during packet exchange.
|
||||||
|
|
||||||
|
## PAN-245690
|
||||||
|
|
||||||
|
Fixed an issue where the managed collectors health status on Panorama displayed as empty.
|
||||||
|
|
||||||
|
## PAN-245125
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where file descriptors were not closed due to invalid configurations.
|
||||||
|
|
||||||
|
## PAN-244907
|
||||||
|
|
||||||
|
Fixed an issue where ports did not go down when moving from an active state to a suspended state.
|
||||||
|
|
||||||
|
## PAN-244746
|
||||||
|
|
||||||
|
Fixed an issue where changes committed on Panorama were not reflected on the firewall after a successful push.
|
||||||
|
|
||||||
|
## PAN-244648
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5200 Series only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not boot up after a factory reset, and, with FIPS mode enabled, the firewall rebooted into maintenance mode.
|
||||||
|
|
||||||
|
## PAN-244622
|
||||||
|
|
||||||
|
Fixed an issue where FIB repush did not work with Advanced Routing enabled.
|
||||||
|
|
||||||
|
## PAN-244013
|
||||||
|
|
||||||
|
Fixed an issue where the web interface did not display newly added antispyware signatures or Vulnerability signatures.
|
||||||
|
|
||||||
|
## PAN-243240
|
||||||
|
|
||||||
|
Fixed an issue where the using QoS caused packet buffer utilization to increase exponentially and the PKI POOL DFLT pool depleted until a reboot was performed.
|
||||||
|
|
||||||
|
## PAN-242893
|
||||||
|
|
||||||
|
Fixed an issue where the verdict for www.googleapis.com displayed the message not-resolved.
|
||||||
|
|
||||||
|
## PAN-242309
|
||||||
|
|
||||||
|
Fixed an issue where a higher byte count (s2c) was observed for DNS-Base application.
|
||||||
|
|
||||||
|
## PAN-241230
|
||||||
|
|
||||||
|
Fixed an issue where the SNMP get request status value for Panorama connections was incorrect.
|
||||||
|
|
||||||
|
## PAN-241192
|
||||||
|
|
||||||
|
Fixed an issue where HIP reports did not match HIP objects configured with certificate check.
|
||||||
|
|
||||||
|
## PAN-240786
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in HA configurations where VXLAN sessions were allocated, but not installed or freed, which resulted in a constant high session table usage that was not synced between the firewalls. This resulted in a session count mismatch.
|
||||||
|
|
||||||
|
## PAN-240612
|
||||||
|
|
||||||
|
Fixed a kernel panic caused by a third-party issue
|
||||||
|
|
||||||
|
## PAN-240368
|
||||||
|
|
||||||
|
Fixed an issue where Authentication Portal redirection for HTTPS websites did not work when **Enhanced Handling of SSL/TLS Handshakes for Decrypted Traffic** was enabled.
|
||||||
|
|
||||||
|
## PAN-240347
|
||||||
|
|
||||||
|
Fixed an issue with the web interface where the **Dashboard** and a **Device Group** policy rule took longer than expected to load.
|
||||||
|
|
||||||
|
## PAN-240225
|
||||||
|
|
||||||
|
Fixed an issue where authentication failed on web-based GlobalProtect portal.
|
||||||
|
|
||||||
|
## PAN-239662
|
||||||
|
|
||||||
|
Fixed an issue where the NSSA default route from the firewall was not generated to advertise even though the backbone area default route was advertised during a graceful restart.
|
||||||
|
|
||||||
|
## PAN-239354
|
||||||
|
|
||||||
|
Fixed an issue where DNS resolution was delayed when an antispyware policy rule was applied to both client to firewall and firewall to internal DNS server legs of a connection.
|
||||||
|
|
||||||
|
## PAN-238625
|
||||||
|
|
||||||
|
Fixed an issue where, when the physical interface went down, the SD-WAN Ethernet connection state still showed **UP/path-monitor** due to the Active URL SaaS monitor connection state remaining UP/path-monitor.
|
||||||
|
|
||||||
|
## PAN-237608
|
||||||
|
|
||||||
|
Fixed an issue where a NetFlow export truncated the source username.
|
||||||
|
|
||||||
|
## PAN-236133
|
||||||
|
|
||||||
|
Fixed an issue where SSL traffic was impacted when **SSL Command and Control detector** for Incline Cloud Analysis was set to **reset-both**, **reset-client**, **reset-server**, or **drop**.
|
||||||
|
|
||||||
|
## PAN-232550
|
||||||
|
|
||||||
|
Fixed an issue where SNMPv3 authentication failed when using SHA-512 Auth protocol.
|
||||||
|
|
||||||
|
## PAN-231642
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where users who were logged in through multiple sessions were able to see an active lock on only one session.
|
||||||
|
|
||||||
|
## PAN-229115
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where the screen was blank after logging in to Panorama.
|
||||||
|
|
||||||
|
## PAN-226108
|
||||||
|
|
||||||
|
Fixed an issue where the masterd process was unable to start or stop the sysd process.
|
||||||
|
|
||||||
|
## PAN-225394
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where SNMP incorrectly reported high packet descriptor usage.
|
||||||
|
|
||||||
|
## PAN-223914
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the reportd process unexpectedly stopped responding.
|
||||||
|
|
||||||
|
## PAN-223418
|
||||||
|
|
||||||
|
Fixed an issue where heartbeats to the brdagent process were lost, resulting in the process not responding, which caused the firewall to reboot.
|
||||||
|
|
||||||
|
## PAN-221041
|
||||||
|
|
||||||
|
Fixed an issue where the following error message was seen frequently in the system logs: Clearing snmpd.log due to log overflow.
|
||||||
|
|
||||||
|
## PAN-216941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances in Log Collector mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Panorama stopped processing and saving logs.
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where **Commit and Push** or **Push to Devices** operations failed when an external dynamic list was configured to check for updates every 5 minutes due to the commit and external dynamic fetch processes overlapping.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.11-h10
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-259351
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3393](https://security.paloaltonetworks.com/CVE-2024-3393).
|
||||||
@@ -0,0 +1,95 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.11-h12
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-279604
|
||||||
|
|
||||||
|
Fixed an issue where scheduled SaaS application usage reports were generated incorrectly, and the login page was displayed instead of the report content.
|
||||||
|
|
||||||
|
## PAN-273994
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0111](https://security.paloaltonetworks.com/CVE-2025-0111).
|
||||||
|
|
||||||
|
## PAN-273971
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0108](https://security.paloaltonetworks.com/CVE-2025-0108).
|
||||||
|
|
||||||
|
## PAN-273278
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0109](https://security.paloaltonetworks.com/CVE-2025-0109).
|
||||||
|
|
||||||
|
## PAN-271926
|
||||||
|
|
||||||
|
Fixed an issue where TLS 1.3 decryption failed with a bad record MAC error when the firewall was configured to decrypt and inspect TLS traffic.
|
||||||
|
|
||||||
|
## PAN-270549
|
||||||
|
|
||||||
|
Fixed an issue where some TLS connections were not handled correctly, which led to instability in the dataplane.
|
||||||
|
|
||||||
|
## PAN-269731
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not display logs from firewalls after upgrading to PAN-OS 10.2.11 on devices due to Elasticsearch (ES) getting restarted continuously.
|
||||||
|
|
||||||
|
## PAN-268727
|
||||||
|
|
||||||
|
Fixed an issue where traffic was dropped when the accumulation proxy was enabled and header insertion modified packets.
|
||||||
|
|
||||||
|
## PAN-268319
|
||||||
|
|
||||||
|
Fixed an issue where **Receive Time** and **Time Generated** were not visible as attributes in the **Filter Builder** for system logs and URL filtering logs.
|
||||||
|
|
||||||
|
## PAN-268260
|
||||||
|
|
||||||
|
Fixed an issue on hardware firewalls where, when SSL decryption was enabled and Client Hello messages spanned multiple TCP segments, some SSL decrypted sessions failed.
|
||||||
|
|
||||||
|
## PAN-267781
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not display the Source Dynamic Address Group.
|
||||||
|
|
||||||
|
## PAN-264762
|
||||||
|
|
||||||
|
Fixed an issue where the firewall showed the status of SFP+ interfaces as not up, or up but not configured, when a PAN-SFP-PLUS-SR cable was connected.
|
||||||
|
|
||||||
|
## PAN-263465
|
||||||
|
|
||||||
|
Fixed an issue where the logrcvr process stopped responding due to a memory leak and buffer overrun.
|
||||||
|
|
||||||
|
## PAN-261739
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall displayed 0 for the physical port counters read from MAC.
|
||||||
|
|
||||||
|
## PAN-259351
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3393](https://security.paloaltonetworks.com/CVE-2024-3393).
|
||||||
|
|
||||||
|
## PAN-256051
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where enabling flow basic caused the firewall to stop responding due to a masterd process restart.
|
||||||
|
|
||||||
|
## PAN-255619
|
||||||
|
|
||||||
|
Fixed an intermittent issue where file downloads from websites failed when decrypting HTTP/2 traffic.
|
||||||
|
|
||||||
|
## PAN-249597
|
||||||
|
|
||||||
|
Fixed an issue where the **Policy** page on the Panorama web interface was slower than expected when a device group had a large number of managed devices.
|
||||||
|
|
||||||
|
## PAN-241004
|
||||||
|
|
||||||
|
Fixed an issue where DNS Proxy dropped client requests of the type ns for a root domain.
|
||||||
|
|
||||||
|
## PAN-233965
|
||||||
|
|
||||||
|
Fixed an issue here the tund process stopped responding, which caused push operation to managed firewalls or making changes to local firewalls to fail.
|
||||||
|
|
||||||
|
## PAN-230825
|
||||||
|
|
||||||
|
Fixed an issue where link flaps occurred on Panorama appliances in HA configurations.
|
||||||
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.11-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
Fixed an issue where decryption based traffic failed on Explicit Proxy nodes.
|
||||||
|
|
||||||
|
## PAN-261917
|
||||||
|
|
||||||
|
Fixed an issue where websites with a no-decrypt policy rule were decrypted in traffic log when using a Google Chrome browser with PQC enabled.
|
||||||
|
|
||||||
|
## PAN-257957
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls and Panorama appliances in FIPS-CC mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the authd process restarted if RADIUS PAP/CHAP authentication was used.
|
||||||
@@ -0,0 +1,51 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.11-h6
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
|
|
||||||
|
## PAN-267001
|
||||||
|
|
||||||
|
Fixed an issue where multicast streams were unstable with ECMP and dropped every 30 seconds.
|
||||||
|
|
||||||
|
## PAN-266704
|
||||||
|
|
||||||
|
Fixed an issue where filtering BGP routes by peer name in Advanced Routing Engine (ARE) did not display the correct routes.
|
||||||
|
|
||||||
|
## PAN-266312
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions took longer than expected to establish after an HA failover due to BGP.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
Fixed an issue where dereferencing a NULL pointer that occurred caused pan_task processes to stop responding.
|
||||||
|
|
||||||
|
## PAN-259870
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000b firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Luna Network Hardware Security Modules (HSM) did not work after an upgrade or downgrade.
|
||||||
|
|
||||||
|
## PAN-258912
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000b firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall web interface displayed an incorrect HSM client version when the client was upgraded to version 7.2.0.220.
|
||||||
|
|
||||||
|
## PAN-255360
|
||||||
|
|
||||||
|
Fixed an issue where the firewall booted into maintenance mode when there was no connectivity to the specified HSM.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions bypassed L7 inspection or ended unexpectedly with the error resources unavailable when the firewall incorrectly interpreted the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
@@ -0,0 +1,528 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.11
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the set deviceconfig setting preserve-prenat-feature no CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||||
|
|
||||||
|
## PAN-265336
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11-h2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Copper ports flap when generating a technical support file, executing telemetry, or retrieving port status using a Management Data Input/Output (MDIO) read.
|
||||||
|
|
||||||
|
## PAN-264680
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
**Device** > **Setup** is not displayed when the Enterprise Data Loss Prevention (E-DLP) plugin is installed.
|
||||||
|
|
||||||
|
**Workaround:** Uninstall the Enterprise DLP plugin.
|
||||||
|
|
||||||
|
1. Log in to the firewall web interface.
|
||||||
|
2. Select **Device** > **Plugins**.
|
||||||
|
3. Search for dlp.
|
||||||
|
4. **Uninstall**.
|
||||||
|
|
||||||
|
## PAN-264580
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.11 results in the following error: Target image validation failed with error invalid literal for int() with base 10.
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||||
|
|
||||||
|
**Workaround:** Disable Client Hello accumulation using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The command show auth radius-require-msg-authentic might return no output.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-257957
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.12 Addressed Issues.Affects 10.2.11-h1 and later 10.2 releases.
|
||||||
|
```
|
||||||
|
|
||||||
|
If you enable FIPS-CC mode and use the PAP or CHAP authentication methods for your RADIUS server, the authd process may restart unexpectedly. To avoid this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- If you use PAN-OS 10.2.10-h3, 10.2.11, or an earlier version, configure the RADIUS server so that it does not send the message authenticator back to client.
|
||||||
|
- Use other protocols, such as LDAP, Kerberos, TACACS+, SAML, RADIUS EAP, instead of RADIUS PAP or CHAP.
|
||||||
|
- Change from FIPS mode to normal mode.
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```resolved
|
||||||
|
Fixed in PAN-OS 10.2.11. Affects 10.2.11-h2 and later 10.2 releases.
|
||||||
|
```
|
||||||
|
|
||||||
|
Networking cards can experience an internal link fault, causing path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in Traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11-h4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Sessions might end unexpectedly with the error resources-unavailable when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling the [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a JavaScript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on an M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to an M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 Series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific websites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (high availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the Traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the Advanced URL Filtering license, your license entitlements for PAN-DB and Advanced URL Filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,159 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.12
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-264680
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where **Device > Setup** was not displayed on the web interface.
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
Fixed an issue where, when SSL decryption was enabled and Client Hello messages spanned multiple TCP segments, some SSL decrypted sessions failed.
|
||||||
|
|
||||||
|
## PAN-263164
|
||||||
|
|
||||||
|
Fixes a problem where Netflow User ID information was truncated to 31 characters.
|
||||||
|
|
||||||
|
## PAN-262593
|
||||||
|
|
||||||
|
Fixed an issue where traffic to websites failed on the Google Chrome web browser on Secure Web Gateway (SWG) nodes.
|
||||||
|
|
||||||
|
## PAN-261991
|
||||||
|
|
||||||
|
Fixed an issue where traffic that did not match a decryption policy rule, or matched a no-decrypt policy rule, failed when accumulation proxy was enabled and a Zone Protection profile was configured with syn-cookies enabled.
|
||||||
|
|
||||||
|
## PAN-261917
|
||||||
|
|
||||||
|
Fixed an issue where websites with a no-decrypt policy rule were decrypted in traffic log when using a Google Chrome browser with PQC enabled.
|
||||||
|
|
||||||
|
## PAN-261489
|
||||||
|
|
||||||
|
Fixed an issue where an out-of-memory (OOM) condition caused a firewall outage.
|
||||||
|
|
||||||
|
## PAN-261484
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where DPDK allocated twice the amount of memory as requested for pre-allocation.
|
||||||
|
|
||||||
|
## PAN-260928
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect failed to connect when using LDAP authentication with machine certificates with the error message You are not authorized to connect to GlobalProtect portal.
|
||||||
|
|
||||||
|
## PAN-260738
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where the progress bar did not complete when importing a vulnerability profile configuration through an XML file.
|
||||||
|
|
||||||
|
## PAN-260149
|
||||||
|
|
||||||
|
Fixed an issue where the management plane DNS cache size was lower than expected.
|
||||||
|
|
||||||
|
## PAN-259883
|
||||||
|
|
||||||
|
Fixed an issue where the firewalls behind an Amazon Web Services (AWS) Gateway Load Balancer (GWLB) stopped responding when processing GENEVE packets with the reserved bit set.
|
||||||
|
|
||||||
|
## PAN-257994
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
CN-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where commits failed with the error failed to handle CONFIG_UPDATE_START due to cfgdb files for the container not being symbolically linked to the cfgdb files on the virtual machine.
|
||||||
|
|
||||||
|
## PAN-257957
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls and Panorama appliances in FIPS-CC mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the authd process restarted if RADIUS PAP/CHAP authentication was used.
|
||||||
|
|
||||||
|
## PAN-257652
|
||||||
|
|
||||||
|
Fixed an issue where Internal Host Detection for IPv6 did not work after upgrading to a PAN-OS 10.2 release.
|
||||||
|
|
||||||
|
## PAN-255611
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where newly added routes were not automatically sorted based on subnets when added to a redistribution profile.
|
||||||
|
|
||||||
|
## PAN-255509
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions flapped intermittently.
|
||||||
|
|
||||||
|
## PAN-255323
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the Network Processing Card (NPC), Data Processing Card (DPC), and Log Forwarding Card (LFC) remained in a starting state after an unexpected power cycle.
|
||||||
|
|
||||||
|
## PAN-252974
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where specific routes were not advertised when BGP Aggregate was configured with the advertise filter.
|
||||||
|
|
||||||
|
## PAN-252669
|
||||||
|
|
||||||
|
Fixed an issue where the ikemgr process stopped responding with a SIGSEGV error.
|
||||||
|
|
||||||
|
## PAN-251446
|
||||||
|
|
||||||
|
Fixed an issue where a critical system log was generated for a SAML authenticated user whose username length was greater than 32 characters.
|
||||||
|
|
||||||
|
## PAN-250394
|
||||||
|
|
||||||
|
Fixed an issue where a large amount of group data caused serialization errors and prevented synchronization.
|
||||||
|
|
||||||
|
## PAN-239246
|
||||||
|
|
||||||
|
Fixed an issue where the CLI command debug user-id dump hip-based-profile-database-entry returned an incorrect value in the output for the total size of hip reports.
|
||||||
|
|
||||||
|
## PAN-230825
|
||||||
|
|
||||||
|
Fixed an issue where link flaps occurred on Panorama appliances in high-availability (HA) configurations.
|
||||||
|
|
||||||
|
## PAN-227543
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not match traffic to FQDN objects if the FQDN object contained uppercase characters.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions might end unexpectedly with the error resources-unavailable when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-221127
|
||||||
|
|
||||||
|
Fixed an issue where a large number of core files were generated, which caused the root partition to become full and the firewall to move into a non-functional state.
|
||||||
|
|
||||||
|
## PAN-210395
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect application configuration screen did not display all value names when a language other than English was selected.
|
||||||
|
|
||||||
|
## PAN-203231
|
||||||
|
|
||||||
|
Fixed an issue where **Software Version** in the device summary report exported from Panorama included HTML tags.
|
||||||
|
|
||||||
|
## PAN-189951
|
||||||
|
|
||||||
|
Fixed an issue where the CLI command debug device-telemetry on debug caused high CPU load.
|
||||||
|
|
||||||
|
## PAN-76904
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5410 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the management interface went down and an error message displayed in the show interface management CLI command output.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272413
|
||||||
|
|
||||||
|
Fixed an issue where device telemetry did not generate logs after upgrading the firewall.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13-h2
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-259351
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3393](https://security.paloaltonetworks.com/CVE-2024-3393).
|
||||||
@@ -0,0 +1,127 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13-h3
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-274570
|
||||||
|
|
||||||
|
Fixed an issue where the devsrvr process restarted after a failed commit due to an invalid memory access.
|
||||||
|
|
||||||
|
## PAN-273994
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0111](https://security.paloaltonetworks.com/CVE-2025-0111).
|
||||||
|
|
||||||
|
## PAN-273971
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0108](https://security.paloaltonetworks.com/CVE-2025-0108).
|
||||||
|
|
||||||
|
## PAN-273278
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2025-0109](https://security.paloaltonetworks.com/CVE-2025-0109).
|
||||||
|
|
||||||
|
## PAN-273215
|
||||||
|
|
||||||
|
Fixed an issue where a syntax error in the index generation script caused a high management plane CPU load after upgrading.
|
||||||
|
|
||||||
|
## PAN-273021
|
||||||
|
|
||||||
|
Fixed an issue where 25G port links did not come up due to a change in the handling of 25G DAC modules.
|
||||||
|
|
||||||
|
## PAN-271926
|
||||||
|
|
||||||
|
Fixed an issue where TLS 1.3 decryption failed with a bad record MAC error when the firewall was configured to decrypt and inspect TLS traffic.
|
||||||
|
|
||||||
|
## PAN-270549
|
||||||
|
|
||||||
|
Fixed an issue where some TLS connections were not handled correctly, which led to instability in the dataplane.
|
||||||
|
|
||||||
|
## PAN-269899
|
||||||
|
|
||||||
|
Fixed an issue where the Panorama web interface was slower than expected when querying for device tags.
|
||||||
|
|
||||||
|
## PAN-269731
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not display logs from firewalls after upgrading to PAN-OS 10.2.11 on devices due to Elasticsearch (ES) getting restarted continuously.
|
||||||
|
|
||||||
|
## PAN-269624
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect clients failed to connect with the error message The device or feature requires a GlobalProtect subscription license.
|
||||||
|
|
||||||
|
## PAN-268972
|
||||||
|
|
||||||
|
Fixed an issue where Panorama was slower than expected when using a high number of device group tags in a non-shared context.
|
||||||
|
|
||||||
|
## PAN-268909
|
||||||
|
|
||||||
|
Fixed an issue where IP address tags were removed from firewalls after a management server or useridd process restart. This occurred when a Panorama serial-number based configuration was used for User-ID redistribution.
|
||||||
|
|
||||||
|
## PAN-268727
|
||||||
|
|
||||||
|
Fixed an issue where traffic was dropped when the accumulation proxy was enabled and header insertion modified packets.
|
||||||
|
|
||||||
|
## PAN-268319
|
||||||
|
|
||||||
|
Fixed an issue where **Receive Time** and **Time Generated** were not visible as attributes in the **Filter Builder** for system logs and URL filtering logs.
|
||||||
|
|
||||||
|
## PAN-268260
|
||||||
|
|
||||||
|
Fixed an issue on hardware firewalls where, when SSL decryption was enabled and Client Hello messages spanned multiple TCP segments, some SSL decrypted sessions failed.
|
||||||
|
|
||||||
|
## PAN-267781
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not display the Source Dynamic Address Group.
|
||||||
|
|
||||||
|
## PAN-267671
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly due to the all_task process restarting with an OOM condition due to a memory leak on the reportd process.
|
||||||
|
|
||||||
|
## PAN-267001
|
||||||
|
|
||||||
|
Fixed an issue where multicast streams were unstable with ECMP and dropped every 30 seconds.
|
||||||
|
|
||||||
|
## PAN-266312
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions took longer than expected to establish after an HA failover due to BGP.
|
||||||
|
|
||||||
|
## PAN-265179
|
||||||
|
|
||||||
|
Fixed an issue where a kernel race condition caused the firewall to reboot with a kernel panic.
|
||||||
|
|
||||||
|
## PAN-261739
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall displayed 0 for the physical port counters read from MAC.
|
||||||
|
|
||||||
|
## PAN-259002
|
||||||
|
|
||||||
|
Fixed an issue where frequent external dynamic list updates caused the configd process to restart.
|
||||||
|
|
||||||
|
## PAN-256051
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where enabling flow basic caused the firewall to stop responding due to a masterd process restart.
|
||||||
|
|
||||||
|
## PAN-249597
|
||||||
|
|
||||||
|
Fixed an issue where the **Policy** page on the Panorama web interface was slower than expected when a device group had a large number of managed devices.
|
||||||
|
|
||||||
|
## PAN-246949
|
||||||
|
|
||||||
|
Fixed an issue where custom admin users were not able to click **OK** in the push scope selection window when device group or template were disabled under commit in the admin roles.
|
||||||
|
|
||||||
|
## PAN-240739
|
||||||
|
|
||||||
|
Fixed an issue where the ECMP FIB update on the dataplane didn't clear the pending change flag, which caused the next non-ECMP FIB update to miss the latest generation ID and age out after 5 minutes
|
||||||
|
|
||||||
|
## PAN-225213
|
||||||
|
|
||||||
|
Fixed an issue where **Push All Changes** displayed changes that were already committed in the push scope for another device group after performing a selective commit and selective push to the first device group.
|
||||||
|
|
||||||
|
## PAN-215038
|
||||||
|
|
||||||
|
Fixed an issue where the output of the request logging-service-forwarding status CLI command did not display the correct information after successfully onboarding a firewall to Cloud Delivered Licensing (CDL).
|
||||||
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13-h5
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
Fixed an issue where SMTP packets were not sent out when the Client Hello arrived at the firewall in multiple out-of-order segments and the traffic was not subject to SSL decryption.
|
||||||
|
|
||||||
|
## PAN-268815
|
||||||
|
|
||||||
|
Fixed an issue that caused the firewall to reboot due to the wifclient exiting multiple times when using IoT Security.
|
||||||
|
|
||||||
|
## PAN-268800
|
||||||
|
|
||||||
|
Fixed an issue where a large number of logs caused the logrcvr process to stop responding.
|
||||||
|
|
||||||
|
## PAN-268705
|
||||||
|
|
||||||
|
Fixed an intermittent issue where the firewall failed to process FTP traffic after upgrading to PAN-OS 10.1.14.
|
||||||
@@ -0,0 +1,253 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13-h7
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-286255
|
||||||
|
|
||||||
|
Fixed an issue where, when the firewall received an unexpected termination request for SSL sessions, the dataplane experienced a slow buffer resource leak.
|
||||||
|
|
||||||
|
## PAN-283813
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the web interface performance was slower than usual when retrieving read-only configurations from Panorama.
|
||||||
|
|
||||||
|
## PAN-282394
|
||||||
|
|
||||||
|
Fixed an issue where a firewall was only able to display a maximum of 14 permitted IP addresses from a Panorama Template Variable.
|
||||||
|
|
||||||
|
## PAN-282236
|
||||||
|
|
||||||
|
Fixed an issue where large IPv6 packets were reassembled incorrectly on the firewall when the packets arrived fragmented over an IPv4 tunnel.
|
||||||
|
|
||||||
|
## PAN-279621
|
||||||
|
|
||||||
|
Fixed an issue where processes stopped responding when HTTPS Forward traffic was run.
|
||||||
|
|
||||||
|
## PAN-279400
|
||||||
|
|
||||||
|
Fixed an issue where, when **Restrict Certificate Extension**s was enabled on decryption profiles, the basic constraints extension was overwritten incorrectly.
|
||||||
|
|
||||||
|
## PAN-278150
|
||||||
|
|
||||||
|
Fixed an issue where the firewall removed the Authentication Key Identifier (AKID) from the certificate during SSL decryption, which caused Python 3.13 to fail with a certificate verification error.
|
||||||
|
|
||||||
|
## PAN-277417
|
||||||
|
|
||||||
|
Fixed an memory leak issue related to TLS inbound decryption.
|
||||||
|
|
||||||
|
## PAN-277234
|
||||||
|
|
||||||
|
Fixed an issue where a device group import resulted in a Security policy rule being created with **Application** set to **none**.
|
||||||
|
|
||||||
|
## PAN-277147
|
||||||
|
|
||||||
|
Fixed an issue where daily scheduled reports were not generated and emailed.
|
||||||
|
|
||||||
|
## PAN-276678
|
||||||
|
|
||||||
|
Fixed an issue where Panorama became unresponsive while performing a dynamic address update without a lock.
|
||||||
|
|
||||||
|
## PAN-275077
|
||||||
|
|
||||||
|
Fixed an issue where DNS Security intermittently logs malicious domain URLs as Alert instead of taking a Sinkhole action, even when configured to Sinkhole malicious DNS domains.
|
||||||
|
|
||||||
|
## PAN-274797
|
||||||
|
|
||||||
|
Fixed an issue where a DPC on slot 3 failed intermittently due to the pktlog_forwarding process restarting, which resulted in an unexpected HA failover.
|
||||||
|
|
||||||
|
## PAN-274726
|
||||||
|
|
||||||
|
Fixed an issue where Wildfire signature generation was enabled on all nodes in a cluster instead of only the active node.
|
||||||
|
|
||||||
|
## PAN-273964
|
||||||
|
|
||||||
|
Fixed an issue where SNMP scans to a firewall timed out after upgrading to a PAN-OS 10.2 release.
|
||||||
|
|
||||||
|
## PAN-273453
|
||||||
|
|
||||||
|
Fixed an issue where restarting the firewall did not initiate an autocommit job, which caused the firewall to stop responding and the HA interface to go down.
|
||||||
|
|
||||||
|
## PAN-273141
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect clients experienced slow file transfer download throughput when passing through an IPSec tunnel.
|
||||||
|
|
||||||
|
## PAN-272959
|
||||||
|
|
||||||
|
Fixed an issue where the firewall generated BGP update packets larger than 1500 bytes when the interface MTU was 1500 bytes and jumbo frames were enabled globally.
|
||||||
|
|
||||||
|
## PAN-272395
|
||||||
|
|
||||||
|
Fixed an issue where informational logs caused the distributord process log file to be frequently overwritten.
|
||||||
|
|
||||||
|
## PAN-272175
|
||||||
|
|
||||||
|
Fixed an issue where session rematch caused ACE cloud application traffic to match the wrong policy.
|
||||||
|
|
||||||
|
## PAN-271425
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in active/active HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue with SSL inbound decryption on firewalls on a vwire setup with asymmetric routing.
|
||||||
|
|
||||||
|
To use this fix, enter the CLI command set system setting ssl-decrypt ha-vwire-mac-learn global ye s on both firewalls in an HA pair.
|
||||||
|
|
||||||
|
## PAN-271184
|
||||||
|
|
||||||
|
Fixed an issue where Device Telemetry failed due to an issue with the encoding of characters in the log file path.
|
||||||
|
|
||||||
|
## PAN-269956
|
||||||
|
|
||||||
|
Fixed an issue where the all_pktproc process stopped responding, which caused internal path monitor failures.
|
||||||
|
|
||||||
|
## PAN-269677
|
||||||
|
|
||||||
|
Fixed an issue where Panorama did not check for a NULL pointer when querying logs, which caused logs to not display on the web interface.
|
||||||
|
|
||||||
|
## PAN-269291
|
||||||
|
|
||||||
|
Fixed an issue where the scheduled report generation script did not return debug information.
|
||||||
|
|
||||||
|
## PAN-269106
|
||||||
|
|
||||||
|
Fixed an issue where the wifclient stopped responding during server certificate verification for MICA gRPC connections and caused the dataplane to restart when using a cloud-based ML detection engine (MICA). On certain platforms, this caused the firewall to reboot periodically.
|
||||||
|
|
||||||
|
## PAN-269052
|
||||||
|
|
||||||
|
Fixed an issue where traffic was blocked by a URL filtering profile even though the Security policy rule did not have a URL filtering profile configured.
|
||||||
|
|
||||||
|
## PAN-269027
|
||||||
|
|
||||||
|
Fixed an issue related to external dynamic lists that caused commit times on the firewall to be higher than expected.
|
||||||
|
|
||||||
|
## PAN-268951
|
||||||
|
|
||||||
|
Fixed a CPS counter query issue that caused SNMP polling timeouts on the firewall.
|
||||||
|
|
||||||
|
## PAN-268118
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in active/passive HA configurations where, after a failover, irrelevant routing FIB entries were seen in the routing table on the newly active firewall.
|
||||||
|
|
||||||
|
## PAN-267707
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions did not come up even when BGP peering was established.
|
||||||
|
|
||||||
|
## PAN-267097
|
||||||
|
|
||||||
|
Fixed an issue where the replay database size increased significantly due to local and special configurations not being purged after commits.
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where you were unable to click **OK** after selecting an install package type and file from the dropdown and selecting a firewall.
|
||||||
|
|
||||||
|
## PAN-265791
|
||||||
|
|
||||||
|
Fixed an issue where the all_task process stopped responding, which caused the dataplane to go down.
|
||||||
|
|
||||||
|
## PAN-265646
|
||||||
|
|
||||||
|
Fixed an issue where the config lock icon was not visible for a custom role-based admin when a Superuser admin had acquired the config lock.
|
||||||
|
|
||||||
|
## PAN-264708
|
||||||
|
|
||||||
|
Fixed an issue where a selective push was blocked when a configuration load was done.
|
||||||
|
|
||||||
|
## PAN-264678
|
||||||
|
|
||||||
|
Fixed an issue where **Preview Changes** did not display configuration changes in **Commit and push > Push Scope**.
|
||||||
|
|
||||||
|
## PAN-264169
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall sent correlated event logs to the syslog server using the management interface instead of the log interface.
|
||||||
|
|
||||||
|
## PAN-263654
|
||||||
|
|
||||||
|
Fixed an issue where multiple DNS responses with different CNAME values caused evasion false positive alerts.
|
||||||
|
|
||||||
|
## PAN-263559
|
||||||
|
|
||||||
|
Fixed an issue where the dataplane stopped responding and the firewall unexpectedly rebooted due to multiple process restarts.
|
||||||
|
|
||||||
|
## PAN-262729
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the configd process experienced continuous high CPU utilization and repeatedly restarted.
|
||||||
|
|
||||||
|
## PAN-262540
|
||||||
|
|
||||||
|
Fixed an issue where application traffic transactions that reused TCP ports did not work with decryption.
|
||||||
|
|
||||||
|
## PAN-262383
|
||||||
|
|
||||||
|
Fixed an issue where the firewall was unable to decompress the HTTP2 header, which caused the session to be classified as unknown-tcp instead of web-browsing.
|
||||||
|
|
||||||
|
## PAN-260300
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5410, PA-5420, PA-5430, PA-5440 and PA-5445 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue related to the all_pktproc process where DPC slot 3 stopped responding.
|
||||||
|
|
||||||
|
## PAN-260131
|
||||||
|
|
||||||
|
Fixed an issue where Wildfire content installation failed for WF-500B clusters when deployed from Panorama using the deployment schedule.
|
||||||
|
|
||||||
|
## PAN-260015
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where the dataplane restarted due to insufficient allocation of memory buffers.
|
||||||
|
|
||||||
|
## PAN-254577
|
||||||
|
|
||||||
|
Fixed an issue where a core file was created on the Log Forwarding Card due to a third-party software issue.
|
||||||
|
|
||||||
|
## PAN-249581
|
||||||
|
|
||||||
|
Fixed an issue where stale BGP routes were advertised to peers even when they were not present in the local RIB table.
|
||||||
|
|
||||||
|
## PAN-249011
|
||||||
|
|
||||||
|
Fixed an issue where the firewall became unresponsive when committing a configuration change with a large number of uncommitted changes in the replay database.
|
||||||
|
|
||||||
|
## PAN-241772
|
||||||
|
|
||||||
|
Fixed an issue where, when TLSv1.3 was used, an incorrect error message invalid padding was displayed instead of the expected error message Invalid server certificate.
|
||||||
|
|
||||||
|
## PAN-241126
|
||||||
|
|
||||||
|
Fixed an issue where the client IP address was incorrect in the authentication logs for Captive Portal authentication events when the client used IPv6.
|
||||||
|
|
||||||
|
## PAN-238594
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted when a QSFP28 cable was removed from the port while the port was passing traffic.
|
||||||
|
|
||||||
|
## PAN-237010
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where local commits took longer than expected after an upgrade.
|
||||||
|
|
||||||
|
## PAN-233868
|
||||||
|
|
||||||
|
Fixed an issue where the firewall took an incorrect action for overlapping custom and edl-url-categories in a policy rule.
|
||||||
|
|
||||||
|
## PAN-233581
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in active/active HA configurations where SYN+ACK packets of asymmetric TCP sessions were dropped because of a session synchronization issue.
|
||||||
|
|
||||||
|
## PAN-224833
|
||||||
|
|
||||||
|
Fixed an issue where the firewall dropped DHCPv6 relay packets if there were duplicate link-local addresses on different sub-interfaces.
|
||||||
|
|
||||||
|
## PAN-212735
|
||||||
|
|
||||||
|
Fixed an issue where sessions that were previously in sw-cut-through mode (software fast forwarding) and persisted after an HA failover were no longer subject to software fast forwarding, which led to increased dataplane CPU load after HA failover.
|
||||||
@@ -0,0 +1,622 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-297775
|
||||||
|
|
||||||
|
The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail.
|
||||||
|
|
||||||
|
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-293673
|
||||||
|
|
||||||
|
When the firewall generates a high volume of logs and attempts to export these logs to an FTP server, it may consume excessive memory leading to all PAN-OS processes crashing.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-289102
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
A race condition issue leads to a dataplane restart when a predict session is hit at the moment when it's timing out.
|
||||||
|
|
||||||
|
## PAN-288930
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h7 only) This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When ACE (App-ID Cloud Engine) is enabled, traffic from cloud applications might intermittently match an incorrect **cloud-apps** policy rule.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286306
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays Unknown instead of 25GBase-SR.
|
||||||
|
|
||||||
|
## PAN-286255
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.13-h5 This issue is now resolved. See PAN-OS 10.2.13-h7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When a firewall receives an unexpected termination request for certain SSL sessions , NGFW dataplane might experience a slow buffer resource leak.
|
||||||
|
|
||||||
|
**Workaround**: Disable accumulation proxy on the NGFW.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the set deviceconfig setting preserve-prenat-feature no CLI command.
|
||||||
|
|
||||||
|
## PAN-285941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When netflow is enabled, the logrcvr process might get stuck, resulting in the local logging and log forwarding to stop functioning. Running debug log-receiver queue-stats on the CLI will show the "Logs discarded (queue full)" field incrementing over time.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-284066
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
After an upgrade, the IF-MIB::ifInErrors SNMP polled values display errors that don't match the results from the show interface CLI command.
|
||||||
|
|
||||||
|
## PAN-283467
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
The firewall might unexpectedly reboot and enter maintenance mode due to a ctd-agent out-of-memory (OOM) condition when undergoing advanced services load testing with a high volume of IoT EAL log forwarding.
|
||||||
|
|
||||||
|
**Workaround:** Limit the number of EAL logs generated by the firewall using the following CLI command: debug iot eal key-value EAL_PENDING_BYTES=1000.
|
||||||
|
|
||||||
|
## PAN-283331
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
Selective pushes to managed devices fail when the **User ID Master Device** is configured.
|
||||||
|
|
||||||
|
## PAN-282236
|
||||||
|
|
||||||
|
The firewall doesn't reassemble IPv6 packets correctly after they are fragmented.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279901
|
||||||
|
|
||||||
|
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||||
|
|
||||||
|
- The segmented Client Hello packets arrive out-of-order
|
||||||
|
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||||
|
- The first segment of the Client Hello packets is less than 5 bytes
|
||||||
|
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h1 through PAN-OS 10.2.13-h4) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
An SSL/TLS Client Hello may not be transmitted out of the firewall if the Client Hello arrives in multiple TCP segments and the traffic is not subject to SSL decryption (for example, SMTP over SSL).
|
||||||
|
|
||||||
|
## PAN-279604
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h3 only) This issue is now resolved. See PAN-OS 10.2.13-h4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The scheduled SaaS application usage reports are incorrectly generated and only the login page appears instead of the intended report content.
|
||||||
|
|
||||||
|
## PAN-275077
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
DNS Security intermittently logs malicious domain URLs as alert instead of taking a **sinkhole** action, even when configured to sinkhole malicious DNS domains.
|
||||||
|
|
||||||
|
## PAN-270849
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The configd process leaks a small amount of memory in every commit.
|
||||||
|
|
||||||
|
## PAN-269106
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When using a cloud-based ML detection engine (MICA), the wifclient might crash during server cert verification for MICA gRPC connections and cause the dataplane to restart. On certain platforms, this might cause the firewall to reboot.
|
||||||
|
|
||||||
|
**Workaround**: Disable CRL using the following CLI command:debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False
|
||||||
|
|
||||||
|
## PAN-269052
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 and later 10.2.13 releases) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
Traffic might be blocked by a URL Filtering profile that isn't associated with the Security policy rule that the traffic matches.
|
||||||
|
|
||||||
|
## PAN-268815
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When using IoT Security, the wifclient might exit multiple times causing the firewall to reboot.
|
||||||
|
|
||||||
|
**Workaround**: Uninstall the IoT Security license and disable **Enable enhanced application logging** (**Device** > **Management** > **Cloud Logging** > **Cloud Logging Settings**).
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The command show auth radius-require-msg-authentic might return no output.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.14-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-286255
|
||||||
|
|
||||||
|
Fixed an issue where, when the firewall received an unexpected termination request for SSL sessions, the dataplane experienced a slow buffer resource leak.
|
||||||
@@ -0,0 +1,470 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.15
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-289102
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
A race condition issue leads to a dataplane restart when a predict session is hit at the moment when it's timing out.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the debug dataplane set ssl-decrypt accumulate-client-hello disable yes CLI command.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286306
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays Unknown instead of 25GBase-SR.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h7 only) This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When netflow is enabled, the logrcvr process might get stuck, resulting in the local logging and log forwarding to stop functioning. Running debug log-receiver queue-stats on the CLI will show the "Logs discarded (queue full)" field incrementing over time.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-284066
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
After an upgrade, the IF-MIB::ifInErrors SNMP polled values display errors that don't match the results from the show interface CLI command.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279901
|
||||||
|
|
||||||
|
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||||
|
|
||||||
|
- The segmented Client Hello packets arrive out-of-order
|
||||||
|
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||||
|
- The first segment of the Client Hello packets is less than 5 bytes
|
||||||
|
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,171 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.16
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-289102
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed a race condition issue related to predict processing, which resulted in a dataplane restart and traffic loss.
|
||||||
|
|
||||||
|
## PAN-287611
|
||||||
|
|
||||||
|
Fixed an issue where, after upgrading, the firewall incorrectly calculated the UDP checksum for RTP traffic after NAT and Security policy application, which led to dropped packets and silent calls in applications.
|
||||||
|
|
||||||
|
## PAN-286897
|
||||||
|
|
||||||
|
Fixed an issue where the pan_task process stopped responding when the firewall attempted to forward files to the WildFire public cloud, which caused the dataplane to experience heartbeat failures.
|
||||||
|
|
||||||
|
## PAN-286475
|
||||||
|
|
||||||
|
Fixed an issue where the option to sort sequence numbers was missing from **Filters prefix list** in the advanced routing filters.
|
||||||
|
|
||||||
|
## PAN-285941
|
||||||
|
|
||||||
|
Fixed an issue where high memory consumption occurred on the logrcvr process.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
Fixed an issue where the all_task process stopped responding, which caused the firewall to reboot unexpectedly, and traffic failures occurred.
|
||||||
|
|
||||||
|
## PAN-285590
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Amazon Web Services (AWS) GWLB environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall CPU usage reached 100% after upgrading to PAN-OS 11.1.6-h1.
|
||||||
|
|
||||||
|
## PAN-284908
|
||||||
|
|
||||||
|
Fixed an issue where retrieving filenames from OneDrive resulted in a cache miss.
|
||||||
|
|
||||||
|
## PAN-284840
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5220 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where custom reports were delayed when sent via email instead of being sent at the scheduled time.
|
||||||
|
|
||||||
|
## PAN-284069
|
||||||
|
|
||||||
|
Fixed an issue where, after an upgrade, the total number of logout records in the HIP database incorrectly displayed as zero.
|
||||||
|
|
||||||
|
## PAN-284066
|
||||||
|
|
||||||
|
Fixed an issue where, after an upgrade, the SNMP polled values for IF-MIB::ifInErrors displayed a high number of errors that did not match the values in the CLI show interface command.
|
||||||
|
|
||||||
|
## PAN-283664
|
||||||
|
|
||||||
|
Fixed an issue where a slow NAT leak occurred when persistent NAT was enabled. This occurred when ICMP sessions matched the persistent Dynamic IP and Port (DIPP) rule and no predict sessions were involved in that rule.
|
||||||
|
|
||||||
|
## PAN-283428
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 Firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where, after an upgrade, the dataplane CPU reached 100% due to packet buffer exhaustion, which resulted in general packet processing issues.
|
||||||
|
|
||||||
|
## PAN-281797
|
||||||
|
|
||||||
|
Fixed an issue where firewalls became unstable and stopped responding, which resulted in an OOM condition.
|
||||||
|
|
||||||
|
## PAN-280505
|
||||||
|
|
||||||
|
Fixed an issue where the web interface did not display a message to commit prior changes before attempting a partial configuration load.
|
||||||
|
|
||||||
|
## PAN-280409
|
||||||
|
|
||||||
|
Fixed an issue where the popup window did not appear as expected for Clientless VPN users.
|
||||||
|
|
||||||
|
## PAN-279706
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
M-600 appliances only
|
||||||
|
```
|
||||||
|
|
||||||
|
) Fixed an issue where Panorama did not update all panreplay database entries after performing a commit and full push to all devices.
|
||||||
|
|
||||||
|
## PAN-277617
|
||||||
|
|
||||||
|
Fixed an issue where deleting the NTP server address caused a commit validation error. This occurred when the configuration included both primary and secondary NTP servers and the secondary server was removed.
|
||||||
|
|
||||||
|
## PAN-273727
|
||||||
|
|
||||||
|
Fixed an issue where the firewall skipped the DNS policy rule of a domain external dynamic list (EDL) during an EDL refresh.
|
||||||
|
|
||||||
|
To use this fix, run the following CLI command and commit: set deviceconfig setting ctd custom-edl-domains-continuous-reload yes/no
|
||||||
|
|
||||||
|
## PAN-271701
|
||||||
|
|
||||||
|
Fixed an issue where Advanced Services, App-ID Cloud Engine (ACE), and Enhanced Application Log stopped working due to incorrect memory usage accounting, which caused memory usage to remain at 99% after an extended period of time.
|
||||||
|
|
||||||
|
## PAN-270379
|
||||||
|
|
||||||
|
Fixed an issue where socket files created in the /tmp directory were not cleared.
|
||||||
|
|
||||||
|
## PAN-268614
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where, when all rules were highlighted when a read-only admin user clicked the **Highlight Unused Rules** checkbox.
|
||||||
|
|
||||||
|
## PAN-268313
|
||||||
|
|
||||||
|
Fixed an issue where the Priority Code Point (PCP) bits in the VLAN header were not reset to 0 when a packet was received from one Layer 3 tagged interface and forwarded to another, which resulted in dropped packets.
|
||||||
|
|
||||||
|
To use this fix, run the CLI command set force-vlan-pcp-reset yes and reboot the firewall.
|
||||||
|
|
||||||
|
## PAN-267707
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions did not come up even when BGP peering was established.
|
||||||
|
|
||||||
|
## PAN-265782
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where, after you enabled multihop in a BFD profile, you were unable to disable it via the web interface.
|
||||||
|
|
||||||
|
## PAN-260132
|
||||||
|
|
||||||
|
Fixed an issue where secondary IP addresses with a /32 prefix configured on Layer 3 interfaces were not reachable in FRR mode.
|
||||||
|
|
||||||
|
## PAN-260015
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where the dataplane restarted due to insufficient allocation of memory buffers.
|
||||||
|
|
||||||
|
## PAN-255654
|
||||||
|
|
||||||
|
Fixed an issue where, when QoS was enabled on aggregate interfaces, the maximum aggregate interface throughput was capped, which limited network traffic. This occurred even with default QoS settings and no configured egress max-bandwidth.
|
||||||
|
|
||||||
|
## PAN-253187
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the class of service (CoS) priority bit was not modified, causing access points to lose connectivity to the wireless controller when traffic was routed through the firewall.
|
||||||
|
|
||||||
|
## PAN-240606
|
||||||
|
|
||||||
|
Fixed an issue where licenses expired a day before the expiry date.
|
||||||
|
|
||||||
|
## PAN-224729
|
||||||
|
|
||||||
|
Fixed an issue where you were unable to create duplicate entries in Advanced Routing AS path prepend in the BGP filter route map.
|
||||||
|
|
||||||
|
## PAN-224020
|
||||||
|
|
||||||
|
Fixed an issue where CIE validation checks on the firewall prevented configuration pushes from Panorama, which resulted in commit failures during new firewall deployment. This occurred when a template with an Authentication Profile with the **Authentication Type** as **Cloud Authentication Service** was pushed to a newly deployed firewall without internet access or without a device certificate.
|
||||||
|
|
||||||
|
## PAN-220435
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect client failed to install on the firewall.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.18-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-306502
|
||||||
|
|
||||||
|
Fixed an issue where TLS connection failure occurred when traffic was over TLS1.2 or below, header insertion was enabled on the firewall, **send TLS handshake to CTD** was enabled, and traffic hit a decryption policy rule configured with the **no-decrypt** action.
|
||||||
@@ -0,0 +1,357 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.18
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,776 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as out-of-sync on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now out-of-sync.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the show log-collector-es-cluster health command displays the status is red. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called SharedAO1 and a vsys-specific address object also called SharedAO1.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (SharedAO1) in a **Shared** address group called SharedAG1.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (SharedAG1) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** SharedAO1 object was 10.1.1.1 and the device group specific SharedAO1 was 10.2.2.2, the 10.1.1.1 IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the es-1 and es-2 ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector ES health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
admin>debug elasticsearch es-restart optional all
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
log-start eq no
|
||||||
|
|
||||||
|
log-end eq no
|
||||||
|
|
||||||
|
log-end eq yes
|
||||||
|
|
||||||
|
## PAN-215778
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the M-600 appliance in Management Only mode, XML API Get requests for /config fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||||
|
|
||||||
|
504 Gateway timeout
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208325
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||||
|
|
||||||
|
- M-300 and M-700
|
||||||
|
- PA-410 Firewall
|
||||||
|
- PA-440, PA-450, and PA-460 Firewalls
|
||||||
|
- PA-3400 Series
|
||||||
|
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||||
|
- PA-5450 Firewall
|
||||||
|
|
||||||
|
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||||
|
|
||||||
|
admin>request certificate fetch
|
||||||
|
|
||||||
|
## PAN-207629
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, selective push fails to managed firewalls if the managed firewalls are enabled with multiple vsys and the Push Scope contains shared objects in device groups.
|
||||||
|
|
||||||
|
## PAN-206268
|
||||||
|
|
||||||
|
On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (**Device** > **Setup** > **Management**) as part of a template or template stack configuration.
|
||||||
|
|
||||||
|
## PAN-206253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
For PA-3400 Series firewalls, the default log rate is set too low and the max configurable log rate is incorrectly capped resulting in the firewall not generating more than 6,826 logs per second.
|
||||||
|
|
||||||
|
## PAN-206243
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (**Monitor** > **Logs** > **System**) is generated each time the firewall reaches maximum disk usage capacity.
|
||||||
|
|
||||||
|
## PAN-205187
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
ElasticSearch may not start properly when a newly installed Panorama virtual appliance powers on for the first time, resulting in the Panorama virtual appliance being unable to query logs forwarded from the managed firewall to a Log Collector.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and start the PAN-OS software.
|
||||||
|
|
||||||
|
admin>request restart software
|
||||||
|
|
||||||
|
## PAN-204663
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, you are unable to Context Switch from one managed firewall to another.
|
||||||
|
|
||||||
|
**Workaround:** After you Context Switch to a managed firewall, you must first Context Switch back to Panorama before you can continue to Context Switch to a different managed firewall.
|
||||||
|
|
||||||
|
## PAN-201855
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.
|
||||||
|
|
||||||
|
For example, you have template A, B, and C where templates A and B have certificates with the **Block Private Key Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||||
|
|
||||||
|
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||||
|
|
||||||
|
## PAN-199557
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in an Active/Passive high availability (HA) configuration, the configd process restarts due to a memory leak on the Active Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||||
|
|
||||||
|
**Workaround:** Manually reboot the Active Panorama HA peer.
|
||||||
|
|
||||||
|
## PAN-197097
|
||||||
|
|
||||||
|
Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-194826
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
WF-500 appliance only
|
||||||
|
```
|
||||||
|
|
||||||
|
System log forwarding does not work over a TLS connection.
|
||||||
|
|
||||||
|
## PAN-194708
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
URL filtering logs (**Monitor** > **Logs** > **URL Filtering**) erroneously truncate a 16KB Header value and do not display the Header values that follow the truncated 16KB header.
|
||||||
|
|
||||||
|
For example, a URL filtering log has 5 Headers. The second Header has a 16KB value. In the URL filtering log, the first header and the value are displayed, second Header value is truncated, and remaining three headers are not displayed.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-193251
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
If SAML is configured as the authentication method for GlobalProtect, authentication on the Portal page is not successful in the browser.
|
||||||
|
|
||||||
|
**Workaround:** Use the GlobalProtect app installed on the endpoint to authenticate.
|
||||||
|
|
||||||
|
## PAN-192403
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
There is no commit warning in the web interface when configuring the management interface and logging interface in the same subnetwork. Having both interfaces in the same subnetwork can cause routing and connectivity issues.
|
||||||
|
|
||||||
|
## PAN-190735
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain webpages that use chunked-encoded data transfers might not load properly when analyzed by Advanced URL Filtering cloud inline categorization.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-190435
|
||||||
|
|
||||||
|
When you **Commit** a configuration change, the **Task Manager** commit Status goes directly from 0% to Completed and does accurately reflect the commit job progress.
|
||||||
|
|
||||||
|
## PAN-189425
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, **Export Panorama and devices config bundle** (**Panorama** > **Setup** > **Operations**) fails to export. When the export fails, you are redirected to a new window and the following error is displayed:
|
||||||
|
|
||||||
|
Failed to redirect error to /var/log/pan/appweb3-panmodule.log (Permission denied)
|
||||||
|
|
||||||
|
## PAN-189395
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Running any version of PAN-OS 10.2.1 on a PA-400 Series firewall can cause the dataplane process to restart unexpectedly and trigger a crash.
|
||||||
|
|
||||||
|
## PAN-189380
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you successfully upgrade a PA-3000 Series firewall to PAN-OS 10.2.0 or later release and Enterprise data loss prevention (DLP) plugin 3.0.0 or later release, the first configuration push from the Panorama management server causes the firewall dataplane to crash.
|
||||||
|
|
||||||
|
**Workaround:** Restart the firewall to restore dataplane functionality.
|
||||||
|
|
||||||
|
1. [Log in to the firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli).
|
||||||
|
2. Restart the firewall.
|
||||||
|
admin> request restart system
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-189057
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
HA configuration
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, Panorama enters a non-functional state due to php.debug.log life taking up too much space.
|
||||||
|
|
||||||
|
**Workaround:** Disable the debug flag for Panorama.
|
||||||
|
|
||||||
|
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface).
|
||||||
|
2. In the same browser you are logged into the Panorama web interface, enter the following URL.
|
||||||
|
https://<panorama_ip>/debug
|
||||||
|
3. Uncheck (disable) **Debug** or **Clear Debug**.
|
||||||
|
4. () Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.
|
||||||
|
|
||||||
|
## PAN-188904
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.
|
||||||
|
|
||||||
|
## PAN-188489
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, dynamic content updates are not automatically pushed to VM-Series firewalls licensed using the Panorama Software Firewall License plugin when **Automatically push content when software device registers to Panorama** (**Panorama** > **Templates** > **Add Stack**) is enabled.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-188064
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The SCP Server Profile configuration (**Devices** > **Server Profiles** > **SCP** are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset
|
||||||
|
|
||||||
|
## PAN-187429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On PA-3400 & PA-5400 series firewalls (minus the PA-5450), the CLI and SNMP MIB walk do not display the Model and Serial-number of the Fan tray and PSUs.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-187234
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.
|
||||||
|
|
||||||
|
## PAN-186913
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, **Validate Device Group** (**Commit** > **Commit and Push** erroneously issues a CommitAll operation instead of a ValidateAll operation when multiple device groups are included in the push and results in no configuration validation.
|
||||||
|
|
||||||
|
**Workaround:** Validate device group configurations using one of the following methods.
|
||||||
|
|
||||||
|
- Select only one device group when you **Validate Device Group** for a **Commit and Push** to managed firewalls.
|
||||||
|
- To validate multiple device groups, select **Commit** > **Commit to Panorama** first. After the device group configuration is committed to Panorama, select **Commit** > **Push to Devices** and **Validate Device Group** to validate multiple device groups.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-186262
|
||||||
|
|
||||||
|
The Panorama management server in Panorama or Log Collector mode may become unresponsive as Elasticsearch accumulates internal connections related to logging processes. The chances Panorama becomes unresponsive increases the longer Panorama remains powered on.
|
||||||
|
|
||||||
|
**Workaround:** Reboot Panorama if it becomes unresponsive.
|
||||||
|
|
||||||
|
## PAN-186134
|
||||||
|
|
||||||
|
On the Panorama management server, performing a **Commit and Push** (**Commit > Commit and Push**) may intermittently not push the committed configuration changes to managed firewalls.
|
||||||
|
|
||||||
|
**Workaround:** Select **Commit > Push to Devices** to push the committed configuration changes to your managed firewalls.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184708
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama managed firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
Scheduled report emails (**Monitor** > **PDF Reports** > **Email Scheduler**) are not emailed if:
|
||||||
|
|
||||||
|
- A scheduled report email contains a Report Group (**Monitor** > **PDF Reports** > **Report Group**) which includes a SaaS Application Usage report.
|
||||||
|
- A scheduled report contains only a SaaS Application Usage Report.
|
||||||
|
|
||||||
|
**Workaround:** To receive a scheduled report email for all other PDF report types:
|
||||||
|
|
||||||
|
1. Select **Monitor** > **PDF Reports** > **Report Groups** and remove all SaaS Application Usage reports from all Report Groups.
|
||||||
|
2. Select **Monitor** > **PDF Reports** > **Email Scheduler** and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select **Disable** and click **OK**.
|
||||||
|
Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
|
||||||
|
3. **Commit**.
|
||||||
|
() Select **Commit** > **Commit and Push**
|
||||||
|
|
||||||
|
## PAN-184702
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, an M-700 appliance in Log Collector mode fails to connect to Panorama when added as a managed collector (**Panorama > Managed Collectors**).
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the M-700 CLI](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli.html) and [recover the Log Collector connectivity to Panorama](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/recover-managed-device-connectivity-to-panorama.html).
|
||||||
|
|
||||||
|
## PAN-184474
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the firewall has Advanced Routing enabled, a static route stays active after the interface goes down.
|
||||||
|
|
||||||
|
**Workaround**: For firewalls that support Bidirectional Forwarding Detection (BFD), configure BFD for the static route.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-182734
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-176156
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
Executing show running resource-monitor with the ingress-backlogs option produces the following server error: Dataplane is not up or invalid target-dp(*.dp*).
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-172132
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved by PAN-189643. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
QoS fails to run on a tunnel interface (for example, tunnel.1).
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.2-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-195517
|
||||||
|
|
||||||
|
Fixed an issue where **CommitAll** operations from Panorama to Prisma Access device groups failed due to missing configuration files.
|
||||||
|
|
||||||
|
## PAN-194107
|
||||||
|
|
||||||
|
Fixed an issue where the expiry date for the Advanced Threat Protection license was incorrect for BND3 payg VM-Series firewalls on Amazon Web Services (AWS), Oracle Cloud Infrastructure (OCI), Google Cloud Platform (GCP), and Microsoft Azure.
|
||||||
|
|
||||||
|
## PAN-186075
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted after receiving large packets while in DPDK mode on Azure virtual machines running CX4 (MLx5) drivers.
|
||||||
@@ -0,0 +1,52 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.2-h4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237935
|
||||||
|
|
||||||
|
Extended the offline PAN-DB, Panorama, and WildFire certificates which were previously set to expire on September 2, 2024.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-237871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
WF-500 appliances and PAN-DB private cloud deployments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
|
|
||||||
|
## PAN-202450
|
||||||
|
|
||||||
|
Fixed an issue where the device-client-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-198372
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.2-h5
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.2-h6
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
@@ -0,0 +1,32 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.3-h11
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
@@ -0,0 +1,32 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.3-h12
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.3-h13
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.3-h14
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
@@ -0,0 +1,79 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.3-h4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-210513
|
||||||
|
|
||||||
|
Fixed an issue where Captive Portal authentication via SAML did not work.
|
||||||
|
|
||||||
|
## PAN-208737
|
||||||
|
|
||||||
|
Fixed an issue where domain information wasn't populated in IP address-to-username matching after a successful GlobalProtect authentication using an authentication override cookie.
|
||||||
|
|
||||||
|
## PAN-208079
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the PAN-DB engine did not start when using a VM-Series firewall Flex based CPU.
|
||||||
|
|
||||||
|
## PAN-207562
|
||||||
|
|
||||||
|
Fixed an issue where the shard count displayed by the show log-collector-es-cluster health CLI command was higher than the recommended limit. The recommended limit can be calculated with the formula 20*heap-memory*no-of-data-nodes.
|
||||||
|
|
||||||
|
## PAN-206963
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
M-700 Appliances only
|
||||||
|
```
|
||||||
|
|
||||||
|
A CLI command was added to check the status of each physical port of a bond1 interface.
|
||||||
|
|
||||||
|
## PAN-206921
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect client pre-login was successful, but the certificate authentication failed.
|
||||||
|
|
||||||
|
## PAN-206466
|
||||||
|
|
||||||
|
Fixed an issue where the push scope was displaying duplicate shared objects for each device group that were listed under the **shared-object** group.
|
||||||
|
|
||||||
|
## PAN-206069
|
||||||
|
|
||||||
|
Fixed an issue where the firewall was unable to boot up on older Intel CPUs.
|
||||||
|
|
||||||
|
## PAN-205698
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect authentication did not work on Apple MacOS devices when the authentication method used was CIE with SAML Authentication.
|
||||||
|
|
||||||
|
## PAN-204892
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the web interface was not accessible and displayed the error **504 Gateway Not Reachable** due to the mgmtsrvr process not responding.
|
||||||
|
|
||||||
|
## PAN-204838
|
||||||
|
|
||||||
|
Fixed an issue where the dot1q VLAN tag in ARP reply packets were not displayed.
|
||||||
|
|
||||||
|
## PAN-204572
|
||||||
|
|
||||||
|
Fixed an issue where python scripts were not working as expected.
|
||||||
|
|
||||||
|
## PAN-197339
|
||||||
|
|
||||||
|
Fixed an issue where template configuration for the User-ID agent was not reflected on the template stack on Panorama appliances on PAN-OS 10.2.1.
|
||||||
|
|
||||||
|
## PAN-196954
|
||||||
|
|
||||||
|
Fixed a memory leak issue related to the distributord process.
|
||||||
|
|
||||||
|
## PAN-195149
|
||||||
|
|
||||||
|
Fixed an issue where firewall administrators were unable to log in to the web interface when RADIUS two-factor authentication was used.
|
||||||
|
|
||||||
|
## PAN-186270
|
||||||
|
|
||||||
|
Fixed an issue where, when high availability (HA) was enabled and a dynamic update schedule was configured, the configd process unexpectedly stopped responding during configuration commits.
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.3-h9
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-202450
|
||||||
|
|
||||||
|
Fixed an issue where the device-client-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
|
|
||||||
|
## PAN-198372
|
||||||
|
|
||||||
|
Fixed an issue where the root-cert was set to expire on December 31, 2023. With this fix, the expiration date has been extended.
|
||||||
@@ -0,0 +1,32 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.4-h10
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.4-h32
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
@@ -0,0 +1,87 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.4-h3
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-222035
|
||||||
|
|
||||||
|
Fixed an issue where when multiple portals were configured in Prisma Access deployments, CIE SAML authentication failed on the secondary portal.
|
||||||
|
|
||||||
|
## PAN-221068
|
||||||
|
|
||||||
|
Fixed an issue where the firewall restarted after a failed push from Panorama, which resulted in autocommit failures.
|
||||||
|
|
||||||
|
## PAN-219355
|
||||||
|
|
||||||
|
Fixed an issue where disk space became full due to a GPSVC FD leak.
|
||||||
|
|
||||||
|
## PAN-219333
|
||||||
|
|
||||||
|
Fixed an issue where a secondary Prisma Access Portal address with port 8443 did not work.
|
||||||
|
|
||||||
|
## PAN-218620
|
||||||
|
|
||||||
|
Fixed an issue where scheduled configuration exports and SCP server connection testing failed.
|
||||||
|
|
||||||
|
## PAN-218368
|
||||||
|
|
||||||
|
Fixed an issue with incorrect VLAN tagging on Intel based platforms that occurred when opening a response page from a virtual-wire subinterface.
|
||||||
|
|
||||||
|
## PAN-218340
|
||||||
|
|
||||||
|
Fixed a memory leak issue related to the configd process that affected selective pushes on Panorama.
|
||||||
|
|
||||||
|
## PAN-218267
|
||||||
|
|
||||||
|
Fixed an issue where a partial commit and push operation from Panorama to managed firewalls did not work as expected.
|
||||||
|
|
||||||
|
## PAN-218046
|
||||||
|
|
||||||
|
Fixed an issue where the **Virtual Routers** (**Network** > **Virtual Routers**) setting was not available when configuring a custom admin role **Device** > **Admin Roles**.
|
||||||
|
|
||||||
|
## PAN-217053
|
||||||
|
|
||||||
|
Fixed an issue where the configd process stopped responding after a selective push to multiple device groups failed.
|
||||||
|
|
||||||
|
## PAN-215899
|
||||||
|
|
||||||
|
Fixed an issue with Panorama appliances in high availability (HA) configurations where configuration synchronization between the HA peers failed.
|
||||||
|
|
||||||
|
## PAN-215767
|
||||||
|
|
||||||
|
Fixed an issue where, after a high availability failover, IKE SA negotiation failed with the error message INVALID_SPI, which resulted in temporary loss of traffic over some proxy IDs.
|
||||||
|
|
||||||
|
## PAN-215324
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls with Jumbo Frames enabled only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue with CPU throttling and buffer depletion.
|
||||||
|
|
||||||
|
## PAN-215315
|
||||||
|
|
||||||
|
Fixed an issue where the dataplane stopped responding due to ager and inline packet processing occurring concurrently on different cores for the same session.
|
||||||
|
|
||||||
|
## PAN-214463
|
||||||
|
|
||||||
|
Fixed an issue where IKE rekey negotiation failed with a third-party vendor and the firewall acting as the initiator received a response with the VENDOR_ID payload and the error message unexpected critical payload (type 43).
|
||||||
|
|
||||||
|
## PAN-213973
|
||||||
|
|
||||||
|
Fixed an issue where the authd process stopped responding during a cleanup of authentication server context.
|
||||||
|
|
||||||
|
## PAN-212978
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding when executing an SD-WAN configuration or operational CLI command.
|
||||||
|
|
||||||
|
## PAN-210366
|
||||||
|
|
||||||
|
Fixed an issue where deleting a device group when a selective configuration push was in progress caused the configd process to stop responding.
|
||||||
|
|
||||||
|
## PAN-208240
|
||||||
|
|
||||||
|
Fixed an issue where, when attempting to replace an existing certificate, importing a new certificate with the same name as the existing certificate failed due to mismatched public and private keys.
|
||||||
@@ -0,0 +1,87 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.4-h4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-223501
|
||||||
|
|
||||||
|
Fixed an issue where diagnostic information for the dataplane in the dp-monitor.log file was not complete.
|
||||||
|
|
||||||
|
## PAN-222712
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed a low frequency DPC restart issue.
|
||||||
|
|
||||||
|
## PAN-221984
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where an interface went down after a hotplug event and was only recoverable by restarting the firewall.
|
||||||
|
|
||||||
|
## PAN-221836
|
||||||
|
|
||||||
|
Fixed an issue where improper SNI detection caused incorrect URL categorization.
|
||||||
|
|
||||||
|
## PAN-219508
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series, PA-400 Series, PA-1400, PA-3400, and PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Bidirectional Forwarding Detection (BFD) packets experienced a delay in processing, which caused the BFD connection to flap.
|
||||||
|
|
||||||
|
## PAN-217489
|
||||||
|
|
||||||
|
Fixed an issue with firewalls in active/passive high availability (HA) configurations where the passive firewall MAC flapping occurred when the passive firewall was rebooted.
|
||||||
|
|
||||||
|
## PAN-216043
|
||||||
|
|
||||||
|
Fixed an issue where wifclient stopped responding due to shared memory corruption.
|
||||||
|
|
||||||
|
## PAN-215655
|
||||||
|
|
||||||
|
Fixed an issue where, after a multi-dynamic group push, Security policies with the target device tag was added to a firewall that did not have the tag.
|
||||||
|
|
||||||
|
## PAN-215066
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where push scope rendering caused the commit and push or push operation window to hang for several minutes.
|
||||||
|
|
||||||
|
## PAN-214187
|
||||||
|
|
||||||
|
Fixed an issue where superreaders were able to execute the request restart system CLI command.
|
||||||
|
|
||||||
|
## PAN-211191
|
||||||
|
|
||||||
|
Fixed an issue where the firewall restarted after initiating a mgmtsrvr process restart.
|
||||||
|
|
||||||
|
## PAN-210661
|
||||||
|
|
||||||
|
Fixed an issue where firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
|
||||||
|
## PAN-210429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the HTTP service failed to come up on DHCP dataplane interfaces after rebooting the firewall, which resulted in health-check failure on HTTP/80 with a 503 error code on the public load balancer.
|
||||||
|
|
||||||
|
## PAN-195439
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the dataplane interface status went down after a hotplug event triggered by Azure infrastructure.
|
||||||
|
|
||||||
|
## PAN-169586
|
||||||
|
|
||||||
|
Fixed an issue where scheduled log view reports in emails didn't match the monitor page query result for the same time interval.
|
||||||
@@ -0,0 +1,632 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as out-of-sync on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now out-of-sync.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the show log-collector-es-cluster health command displays the status is red. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-227342
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
In an Active/Active High Availability (HA) setup, enabling hardware offload can result in web traffic being blocked.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called SharedAO1 and a vsys-specific address object also called SharedAO1.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (SharedAO1) in a **Shared** address group called SharedAG1.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (SharedAG1) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** SharedAO1 object was 10.1.1.1 and the device group specific SharedAO1 was 10.2.2.2, the 10.1.1.1 IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the es-1 and es-2 ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector ES health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
admin>debug elasticsearch es-restart optional all
|
||||||
|
|
||||||
|
## PAN-220180
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
log-start eq no
|
||||||
|
|
||||||
|
log-end eq no
|
||||||
|
|
||||||
|
log-end eq yes
|
||||||
|
|
||||||
|
## PAN-216821
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The reportd process crashes after you successfully upgrade an M-200 appliance to PAN-OS 10.2.4.
|
||||||
|
|
||||||
|
## PAN-215778
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the M-600 appliance in Management Only mode, XML API Get requests for /config fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||||
|
|
||||||
|
504 Gateway timeout
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212978
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The Palo Alto Networks firewall stops responding when executing an SD-WAN debug operational CLI command.
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-210366
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4-h3 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in a high availability (HA) configuration, the primary HA peer may enter a primary-non-functional state and generate a system log (**Monitor** > **Logs** > **System**) with the following message:
|
||||||
|
|
||||||
|
High root partition usage: going to state Non-Functional
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-208325
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||||
|
|
||||||
|
- M-300 and M-700
|
||||||
|
- PA-410 Firewall
|
||||||
|
- PA-440, PA-450, and PA-460 Firewalls
|
||||||
|
- PA-3400 Series
|
||||||
|
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||||
|
- PA-5450 Firewall
|
||||||
|
|
||||||
|
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||||
|
|
||||||
|
admin>request certificate fetch
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||||
|
|
||||||
|
## PAN-201855
|
||||||
|
|
||||||
|
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.
|
||||||
|
|
||||||
|
For example, you have template A, B, and C where templates A and B have certificates with the **Block Private Key Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||||
|
|
||||||
|
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||||
|
|
||||||
|
## PAN-199557
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in an Active/Passive high availability (HA) configuration, the configd process restarts due to a memory leak on the Active Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||||
|
|
||||||
|
**Workaround:** Manually reboot the Active Panorama HA peer.
|
||||||
|
|
||||||
|
## PAN-198708
|
||||||
|
|
||||||
|
On the Panorama management server, the File Type field does not display any data when you view the Detailed Log View in the Data Filtering log (**Monitor** > **Logs** > **Data Filtering** > **<select log>** > **DLP**).
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-196146
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-190435
|
||||||
|
|
||||||
|
When you **Commit** a configuration change, the **Task Manager** commit Status goes directly from 0% to Completed and does accurately reflect the commit job progress.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-182734
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
|
|
||||||
|
## PAN-160633
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3200 Series, PA-5200 Series, and PA-7000 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
The dataplane restarts repeatedly due to internal path monitoring failures until a power cycle.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.5-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-229705
|
||||||
|
|
||||||
|
Fixed an issue where running the show rule-hit-count CLI command on Panorama displayed the error message Server error : Timed out while getting config lock. Please try again. when attempting to log in or run CLI commands.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.5-h6
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
@@ -0,0 +1,32 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.6-h1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.6-h3
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
@@ -0,0 +1,639 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.6
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-244648
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5200 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
After a factory reset, the firewall may get stuck in maintenance mode and be unable to load the boot image. The firewall fails to enable FIPS-CC mode during this time.
|
||||||
|
|
||||||
|
**Workaround:** The following workaround allows the firewall to boot in normal mode but does not apply to FIPS-CC mode. Attempting to enable FIPS-CC mode after using this workaround will cause the firewall to reboot and re-enter maintenace mode.
|
||||||
|
|
||||||
|
1. Enter maintenance mode.
|
||||||
|
2. Select **Disk Image** > **Advanced Options**.
|
||||||
|
3. Select **Bootstrap** with the options panos-10.2.8, maint, and maint.
|
||||||
|
4. Select **Bootstrap** with the options panos-10.2.8, sysroot0, and panos.
|
||||||
|
5. Select **Bootstrap** with the option sysroot0.
|
||||||
|
6. Select **Reboot**.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as out-of-sync on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now out-of-sync.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-234929
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The tabs in the **ACC**, such as **Network Activity**, **Threat Activity**, and **Blocked Activity**, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the show log-collector-es-cluster health command displays the status is red. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called SharedAO1 and a vsys-specific address object also called SharedAO1.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (SharedAO1) in a **Shared** address group called SharedAG1.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (SharedAG1) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** SharedAO1 object was 10.1.1.1 and the device group specific SharedAO1 was 10.2.2.2, the 10.1.1.1 IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-227368
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The GlobalProtect app cannot connect to a portal or gateway and GlobalProtect Clientless VPN users cannot access applications if authentication takes longer than 20 seconds.
|
||||||
|
|
||||||
|
**Workaround:** Increase the TCP handshake timeout to the maximum value of 60 seconds.
|
||||||
|
|
||||||
|
## PAN-226768
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the GlobalProtect app is installed on iOS endpoints and the gateway is configured to accept cookies, the app stays in Connecting stage after authentication and the GlobalProtect log displays the error message, **User is not in allow list**. This happens when the app is restarted or when the app tries to reconnect after disconnection.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223457
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
If the number of group queries exceeds the Okta rate limit threshold, the firewall clears the cache for the groups. To avoid encountering this issue, disable the Okta rate limit.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222418
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The firewall intermittently records a reconnection message to the authentication server as a error, even if no disconnection occurs.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221857
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Users are unable to log in to the GlobalProtect app using SAML authentication after the app is upgraded to 10.2.3-h4 and the GlobalProtect logs display the following error message: **Username from SAML SSO response is different from the input.**.
|
||||||
|
|
||||||
|
## PAN-221126
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Email server profiles (**Device** > **Server Profiles** > **Email** and **Panorama** > **Server Profiles** > **Email**) to forward logs as email notifications are not forwarded in a readable format.
|
||||||
|
|
||||||
|
**Workaround:** Use a **Custom Log Format** to forward logs as email notifications in a readable format.
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the es-1 and es-2 ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector ES health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
admin>debug elasticsearch es-restart optional all
|
||||||
|
|
||||||
|
## PAN-220180
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
log-start eq no
|
||||||
|
|
||||||
|
log-end eq no
|
||||||
|
|
||||||
|
log-end eq yes
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-196146
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-193004
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama management server fails to delete old IP Tag data. This causes the /opt/pancfg partition to reach maximum capacity which impacts Panorama performance.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,87 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7-h12
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
Fixed an issue where decryption based traffic failed on Explicit Proxy nodes.
|
||||||
|
|
||||||
|
## PAN-261917
|
||||||
|
|
||||||
|
Fixed an issue where websites with a no-decrypt policy rule were decrypted in traffic log when using a Google Chrome browser with PQC enabled
|
||||||
|
|
||||||
|
## PAN-258996
|
||||||
|
|
||||||
|
Fixed an issue where the firewall displayed the SFP ports as PowerDown when the SFP transceiver was removed and reinserted or the port was shut down and brought back up on the peer device.
|
||||||
|
|
||||||
|
## PAN-255868
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall entered maintenance mode after enabling kernel data collection during the silent reboot.
|
||||||
|
|
||||||
|
## PAN-253546
|
||||||
|
|
||||||
|
Fixed an issue where a TLS client hello was split into multiple packets and arrived out of order, so the packets were dropped and the session terminated.
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
|
|
||||||
|
## PAN-251661
|
||||||
|
|
||||||
|
Fixed an issue where a memory overwrite occurred during HTTP/2 header inflation.
|
||||||
|
|
||||||
|
## PAN-251563
|
||||||
|
|
||||||
|
Added CPLD enhancement to capture external power issues.
|
||||||
|
|
||||||
|
## PAN-250152
|
||||||
|
|
||||||
|
Fixed an issue related to shared-to-shared optimization. To utilize this fix, contact Palo Alto Networks Tech Support.
|
||||||
|
|
||||||
|
## PAN-249814
|
||||||
|
|
||||||
|
Fixed an issue where multiple all_task processes stopped responding, which caused the dataplane to fail.
|
||||||
|
|
||||||
|
## PAN-247257
|
||||||
|
|
||||||
|
Fixed an issue where the useridd process stopped responding, which caused the firewall to reboot.
|
||||||
|
|
||||||
|
## PAN-244648
|
||||||
|
|
||||||
|
Fixed an issue where, when FIPS was enabled in maintenance mode, the firewall rebooted and returned to maintenance mode.
|
||||||
|
|
||||||
|
## PAN-240612
|
||||||
|
|
||||||
|
Fixed a kernel panic caused by a third-party issue.
|
||||||
|
|
||||||
|
## PAN-244013
|
||||||
|
|
||||||
|
Fixed an issue where the web interface did not display newly added Anti-Spyware signatures or Vulnerability Signatures.
|
||||||
|
|
||||||
|
## PAN-239662
|
||||||
|
|
||||||
|
Fixed an issue with firewalls in active/passive HA configurations where the NSSA default route from the active firewall was not generated to advertise even though the backbone area default route was advertised during a graceful restart.
|
||||||
|
|
||||||
|
## PAN-238625
|
||||||
|
|
||||||
|
Fixed an issue where, when the physical interface went down, the SD-WAN ethernet connection state still showed **UP/path-monitor** due to the Active URL SaaS monitor connection state remaining UP/path-monitor.
|
||||||
|
|
||||||
|
## PAN-233191
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the Data Processing Card (DPC) restarted due to path monitor failure after QSFP28 disconnected from the Network Processing Card (NPC).
|
||||||
|
|
||||||
|
## PAN-226768
|
||||||
|
|
||||||
|
Fixed an issue where, when the GlobalProtect app was installed on iOS endpoints and the gateway was configured to accept cookies, the app remained in the **Connecting** stage after authentication, and the GlobalProtect log displayed the error message User is not in allow list. This occurred when the app was restarted or when the app attempted to reconnect after disconnection.
|
||||||
@@ -0,0 +1,39 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7-h16
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-264871
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the configd process stopped responding when viewing IP addresses on dynamic address groups with a large number of IP addresses.
|
||||||
|
|
||||||
|
## PAN-262340
|
||||||
|
|
||||||
|
Fixed an issue where FQDN resolution failed for address objects, and all FQDN traffic was denied by the interzone-default policy rule.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
Fixed an issue where dereferencing a NULL pointer that occurred caused pan_task processes to stop responding.
|
||||||
|
|
||||||
|
## PAN-250787
|
||||||
|
|
||||||
|
Fixed an issue where network issues between the firewall and the log collector caused logrcvr process memory exhaustion.
|
||||||
|
|
||||||
|
## PAN-242910
|
||||||
|
|
||||||
|
Fixed an issue where a custom based non Superuser was unable to push to firewalls.
|
||||||
|
|
||||||
|
## PAN-231823
|
||||||
|
|
||||||
|
Fixed an issue where server profile details in the configd process log were incorrectly displayed in plaintext
|
||||||
|
|
||||||
|
## PAN-230755
|
||||||
|
|
||||||
|
Fixed an issue where the devsrvr process intermittently restarted when processing traffic with a Cloud App ID.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions bypassed L7 inspection or ended unexpectedly with the error resources unavailable when the firewall incorrectly interpreted the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
@@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7-h18
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
Fixed an issue where dereferencing a NULL pointer that occurred caused pan_task processes to stop responding.
|
||||||
|
|
||||||
|
## PAN-255653
|
||||||
|
|
||||||
|
Fixed a high availability (HA) failover issue where, when Management Processing Card (MPC) or Base Card (BC) failures occurred, the HA link went down, which caused fpp-down events on one firewall.
|
||||||
|
|
||||||
|
## PAN-240450
|
||||||
|
|
||||||
|
Fixed an issue where commits failed when pushing a configuration to a large number of device groups (vsys) on a firewall.
|
||||||
|
|
||||||
|
## PAN-234560
|
||||||
|
|
||||||
|
Fixed an issue where the daily summary report displayed IPv6 addresses instead of IPv4 addresses.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions bypassed L7 inspection or ended unexpectedly with the error resources unavailable when the firewall incorrectly interpreted the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-219805
|
||||||
|
|
||||||
|
Fixed an issue where the reportd process stopped responding due to a race condition.
|
||||||
@@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7-h19
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-273730
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the web interface became unresponsive after upgrading to PAN-OS 10.2.7-h8.
|
||||||
|
|
||||||
|
## PAN-268727
|
||||||
|
|
||||||
|
Fixed an issue where traffic was dropped when the accumulation proxy was enabled and header insertion modified packets.
|
||||||
|
|
||||||
|
## PAN-260131
|
||||||
|
|
||||||
|
Fixed an issue where the firewall consumed a large amount of memory when forwarding raw logs.
|
||||||
|
|
||||||
|
## PAN-248752
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3200 Series, PA-5200 Series, and PA-850 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not have enough Linux memory on the dataplane, which caused the firewall to restart.
|
||||||
|
|
||||||
|
## PAN-246772
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where the dataplane went down due to a path monitor failure caused by an out-of-memory (OOM) condition related to the pan_task process.
|
||||||
@@ -0,0 +1,140 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7-h3
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-240197
|
||||||
|
|
||||||
|
Fixed an issue where configuration changes made in Panorama and pushed to the firewall were not reflected on the firewall.
|
||||||
|
|
||||||
|
## PAN-239144
|
||||||
|
|
||||||
|
Fixed an issue where the web interface was slower than expected when logging in, committing, and pushing changes after upgrading to PAN-OS 10.2.7.
|
||||||
|
|
||||||
|
## PAN-238792
|
||||||
|
|
||||||
|
Fixed the following device certificate issues:
|
||||||
|
|
||||||
|
- The firewall was unable to automatically renew the device certificate-Fetching device certificates failed incorrectly with the error message OTP is not valid.
|
||||||
|
- Firewalls disconnected from Strata Logging Service after renewing the device certificate.
|
||||||
|
- The device certificate was not correctly generated on the log forwarding card (LFC).
|
||||||
|
- WildFire cloud logs did not log thermite certificate usage status.
|
||||||
|
|
||||||
|
## PAN-237935
|
||||||
|
|
||||||
|
Extended the offline PAN-DB, Panorama, and WildFire certificates which were previously set to expire on September 2, 2024.
|
||||||
|
|
||||||
|
## PAN-237876
|
||||||
|
|
||||||
|
Extended the firewall Panorama root CA certificate which was previously set to expire on April 7th, 2024.
|
||||||
|
|
||||||
|
## PAN-234929
|
||||||
|
|
||||||
|
Fixed an issue where tabs in the **ACC** such as **Network Activity** **Threat Activity** and **Blocked Activity** did not display data when you applied a **Time** filter of **Last 15 Minutes**, **Last Hour**, **Last 6 Hours**, or **Last 12 Hours**, and the data that was displayed with the **Last 24 Hours** filter was not accurate. Reports that were run against summary logs also did not display accurate results.
|
||||||
|
|
||||||
|
## PAN-234279
|
||||||
|
|
||||||
|
Fixed an issue where the ikemgr process crashed due to an IKEv1 timing issue, which caused commits to fail with the following error message: Client ikemgr requesting last config in the middle of a commit/validate, aborting current commit.
|
||||||
|
|
||||||
|
## PAN-232377
|
||||||
|
|
||||||
|
Fixed an issue where the AddrObjRefresh job failed when the useridd process restarted.
|
||||||
|
|
||||||
|
## PAN-231771
|
||||||
|
|
||||||
|
Fixed an issue where the firewall issued /box/getserv/ requests with PAN-OS 7.1.0 and did not take device certificates.
|
||||||
|
|
||||||
|
## PAN-231169
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where an unused plugin incorrectly used memory.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances in FIPS-CC mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the Elasticsearch cluster did not come up, and the show log-collector-es-cluster health CLI command displayed the status as red. This caused log ingestion issues for Panorama appliances in Panorama mode or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227568
|
||||||
|
|
||||||
|
When a device certificate is installed, renewed, or removed, the firewall will reconnect to the WildFire cloud to use the newest certificate.
|
||||||
|
|
||||||
|
## PAN-224954
|
||||||
|
|
||||||
|
Fixed an issue where, after upgrading and rebooting a Panorama appliance in Panorama or Log Collector mode, managed firewalls continuously disconnected.
|
||||||
|
|
||||||
|
## PAN-224067
|
||||||
|
|
||||||
|
Fixed an issue where cookie authentication did not work for GlobalProtect when an authentication override domain was configured in the SAML authentication profile.
|
||||||
|
|
||||||
|
## PAN-224060
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where multiple dataplane processes stopped responding after an upgrade.
|
||||||
|
|
||||||
|
## PAN-223652
|
||||||
|
|
||||||
|
Fixed an issue where data was not thread safe and led to concurrent read/write issues that caused GPSVC to stop working unexpectedly.
|
||||||
|
|
||||||
|
## PAN-223270
|
||||||
|
|
||||||
|
Fixed an issue with Virtual Wire links on firewalls in active/active HA configurations where the forwarding path was not preserved in HTTP/2 cleartext traffic with asymmetric routing.
|
||||||
|
|
||||||
|
## PAN-222002
|
||||||
|
|
||||||
|
Fixed an issue where content updates failed with the error message Unable to get key pancontent-8.0.pass from cryptod. Error -9.
|
||||||
|
|
||||||
|
## PAN-218988
|
||||||
|
|
||||||
|
Fixed an issue in FIPS mode where, when importing a certificate with a new private key, and the certificate used the name of an existing certificate on the Panorama, the following error message was displayed: Mismatched public and private keys.
|
||||||
|
|
||||||
|
## PAN-218057
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where internal path monitoring failed due to a heartbeat miss.
|
||||||
|
|
||||||
|
## PAN-217289
|
||||||
|
|
||||||
|
Fixed an intermittent issue where HTTP/2 traffic caused buffer depletion.
|
||||||
|
|
||||||
|
## PAN-216214
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama managed firewalls in active/active HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the HA (high availability) status displayed as **Out of Sync** (**Panorama > Managed Devices > Health**) if local firewall configurations were made on one of the HA peers. This caused the next HA configuration sync to overwrite the local firewall configuration made on the HA peer.
|
||||||
|
|
||||||
|
## PAN-215576
|
||||||
|
|
||||||
|
Fixed an issue where the userID-Agent and TS-Agent certificates were set to expire on November 18, 2024. With this fix, the expiration date has been extended to January 2032.
|
||||||
|
|
||||||
|
## PAN-208395
|
||||||
|
|
||||||
|
Fixed an issue where user authentication failed in multi-vsys environments with the error message User is not in allowlist when an authentication profile was created in a shared configuration space.
|
||||||
|
|
||||||
|
## PAN-202361
|
||||||
|
|
||||||
|
Fixed an issue where packets queued to the pan_task process were still transmitted when the process was not responding.
|
||||||
|
|
||||||
|
## PAN-189769
|
||||||
|
|
||||||
|
Fixed an issue on Amazon Web Services (AWS) Gateway Load Balancer (GWLB) deployments with overlay routing enabled where, when a single firewall was the backend of multiple GWLBs, packets were re-encapsulated with an incorrect source IP address.
|
||||||
|
|
||||||
|
## PAN-181706
|
||||||
|
|
||||||
|
Fixed an issue where the logrcvr process stopped responding after upgrading to PAN-OS 10.1.
|
||||||
@@ -0,0 +1,115 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-236605
|
||||||
|
|
||||||
|
Fixed an issue where the configd process stopped responding due to a deadlock related to rule-hit-count.
|
||||||
|
|
||||||
|
## PAN-232800
|
||||||
|
|
||||||
|
Fixed an issue where critical disk usage for /opt/pancfg increased continuously and the system logs displayed the following message: Disk usage for /opt/pancfg exceeds limit, <value> percent in use.
|
||||||
|
|
||||||
|
## PAN-232132
|
||||||
|
|
||||||
|
Fixed an issue where DNS response packets were malformed when an Anti-Spyware Security Profile was enabled.
|
||||||
|
|
||||||
|
## PAN-232059
|
||||||
|
|
||||||
|
Fixed an issue with memory management when processing large certificates using TLSv1.3.
|
||||||
|
|
||||||
|
## PAN-231823
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-5916](https://security.paloaltonetworks.com/CVE-2024-5916).
|
||||||
|
|
||||||
|
## PAN-231043
|
||||||
|
|
||||||
|
Fixed an issue where websites were not able to be opened via GlobalProtect with SSL-VPN when software cut through was enabled.
|
||||||
|
|
||||||
|
## PAN-229691
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where configuration lock timeout errors were observed during normal operational commands by increasing thread stack size on Panorama.
|
||||||
|
|
||||||
|
## PAN-228998
|
||||||
|
|
||||||
|
Fixed an issue where multiple license status checks caused an internal process to stop responding.
|
||||||
|
|
||||||
|
## PAN-228877
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue with OOM conditions that caused slot restarts due to pan_cmd consuming more than 300 MB.
|
||||||
|
|
||||||
|
## PAN-227539
|
||||||
|
|
||||||
|
Fixed an issue where excess WIF process memory use caused processes to restart due to OOM conditions.
|
||||||
|
|
||||||
|
## PAN-227368
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect app was unable to connect to a portal or gateway and GlobalProtect Clientless VPN users were unable to access applications if authentication took more than 20 seconds.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
Fixed an issue on Panorama related to Shared configuration objects where configuration pushes to multi-vsys firewalls when authentication took longer than 20 seconds.
|
||||||
|
|
||||||
|
## PAN-224145
|
||||||
|
|
||||||
|
Fixed an issue in multi-vsys environments where, when Panorama was on a PAN-OS 10.2 release and the firewall was on a PAN-OS 10.1 release, commits failed on the firewall when inbound inspection mode was configured in the decryption policy rule.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
Fixed an issue where closed ElasticSearch shards were not deleted, which resulted in shard purging not working as expected.
|
||||||
|
|
||||||
|
## PAN-221973
|
||||||
|
|
||||||
|
Fixed an issue where the same user connected to multiple SSL VPN connections and one of the sessions stopped working.
|
||||||
|
|
||||||
|
## PAN-221190
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-800 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted due to I2C errors when unsupported optics were inserted in ports 5-8.
|
||||||
|
|
||||||
|
## PAN-221126
|
||||||
|
|
||||||
|
Fixed an issue where Email server profiles (**Device > Server Profiles > Email and Panorama > Server Profiles > Email**) to forward logs as email notifications were not forwarded in a readable format.
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
M-600 Appliances only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where ElasticSearch processes did not restart when the appliance was rebooted, which caused the Managed Collector ES health status to be downgraded.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
M-600 Appliances in Log Collector mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Panorama continuously rebooted and became unresponsive, which consumed excessive logging disk space and prevented new log ingestion.
|
||||||
|
|
||||||
|
## PAN-215268
|
||||||
|
|
||||||
|
Fixed an issue where selective push did not work for firewalls on PAN-OS 9.1 or an earlier release.
|
||||||
|
|
||||||
|
## PAN-214186
|
||||||
|
|
||||||
|
Fixed an issue where category length was incorrect, which caused the dataplane to restart.
|
||||||
|
|
||||||
|
## PAN-212761
|
||||||
|
|
||||||
|
Fixed an issue where the all_pktproc process stopped responding, which caused the dataplane to go down and caused HA failover.
|
||||||
|
|
||||||
|
## PAN-193004
|
||||||
|
|
||||||
|
Fixed an issue where /opt/pancfg partition utilization reached 100%, which caused access to the Panorama web interface to fail.
|
||||||
@@ -0,0 +1,103 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.8-h13
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-264883
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7080 appliances with LPCs only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where syslog forwarding over TCP stopped after upgrading.
|
||||||
|
|
||||||
|
## PAN-262946
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where logging in via the CLI or web interface did not work due to increased memory usage.
|
||||||
|
|
||||||
|
## PAN-262340
|
||||||
|
|
||||||
|
Fixed an issue where FQDN resolution failed for address objects, and all FQDN traffic was denied by the interzone-default policy rule.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
Fixed an issue where dereferencing a NULL pointer that occurred caused pan_task processes to stop responding.
|
||||||
|
|
||||||
|
## PAN-261484
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where DPDK allocated twice the amount of memory as requested for pre-allocation.
|
||||||
|
|
||||||
|
## PAN-259727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Panorama became unresponsive and displayed a 504 gateway timeout error when accessing the web interface or the CLI.
|
||||||
|
|
||||||
|
## PAN-257736
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where traffic to benign applications was was impacted by holding TCP sequential segments for MLC inspection and not releasing the full chain after a benign verdict was received.
|
||||||
|
|
||||||
|
## PAN-257462
|
||||||
|
|
||||||
|
Fixed an issue related to the varrcvr process where the management plane CPU was higher than expected.
|
||||||
|
|
||||||
|
## PAN-255509
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where BFD sessions flapped intermittently.
|
||||||
|
|
||||||
|
## PAN-253829
|
||||||
|
|
||||||
|
Fixed an issue where the CLI command show running security-policy timed out when the Security policy was large.
|
||||||
|
|
||||||
|
## PAN-252270
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where changes were incorrectly applied after a reboot or a restart of the configd process.
|
||||||
|
|
||||||
|
## PAN-252036
|
||||||
|
|
||||||
|
Fixed an issue where, when the GlobalProtect portal was not configured, accessing the GlobalProtect gateway still loaded a portal malformed page.
|
||||||
|
|
||||||
|
## PAN-250787
|
||||||
|
|
||||||
|
Fixed an issue where network issues between the firewall and the log collector caused logrcvr process memory exhaustion.
|
||||||
|
|
||||||
|
## PAN-246708
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding when the all_pktproc repeatedly restarted.
|
||||||
|
|
||||||
|
## PAN-242910
|
||||||
|
|
||||||
|
Fixed an issue where a custom based non Superuser was unable to push to firewalls.
|
||||||
|
|
||||||
|
## PAN-241044
|
||||||
|
|
||||||
|
Fixed an issue where traffic was denied by the interzone-default policy rule when a Security policy rule with an FQDN destination was configured.
|
||||||
|
|
||||||
|
## PAN-240066
|
||||||
|
|
||||||
|
Fixed a duplicate MAC address issue where an ethernet interface sent out Gratuitous ARP (GARP) messages for an IP address that was not configured on it.
|
||||||
|
|
||||||
|
## PAN-240001
|
||||||
|
|
||||||
|
Fixed an issue where the pan_task process restarted due to configd and devsrvr process memory requirements.
|
||||||
|
|
||||||
|
## PAN-239354
|
||||||
|
|
||||||
|
Fixed an issue where DNS resolution was delayed when an Antispyware policy rule was applied to both client to firewall and firewall to internal DNS server legs of a connection.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions bypassed L7 inspection or ended unexpectedly with the error resources unavailable when the firewall incorrectly interpreted the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
@@ -0,0 +1,99 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.8-h18
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-273215
|
||||||
|
|
||||||
|
Fixed an issue where a syntax error in the index generation script caused a high management plane CPU load after upgrading.
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
|
|
||||||
|
## PAN-269624
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect clients failed to connect with the error message The device or feature requires a GlobalProtect subscription license.
|
||||||
|
|
||||||
|
## PAN-268909
|
||||||
|
|
||||||
|
Fixed an issue where IP address tags were removed from firewalls after a management server or useridd process restart. This occurred when a Panorama serial-number based configuration was used for User-ID redistribution.
|
||||||
|
|
||||||
|
## PAN-264249
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where SNMP queries timed out when using SNMP.
|
||||||
|
|
||||||
|
## PAN-263973
|
||||||
|
|
||||||
|
Fixed an issue where log collectors had a low incoming log rate.
|
||||||
|
|
||||||
|
## PAN-261673
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where, when Accelerated Networking was enabled, traffic was dropped because of the flow_parse_ip_hdr counter related to an Nvidia driver issue.
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Networking Cards (NC) experienced an internal link fault which caused path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-252974
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where specific routes were not advertised when BGP Aggregate was configured with the advertise filter.
|
||||||
|
|
||||||
|
## PAN-246699
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where **Rule Usage** and **Apps Seen** under Security policy rules stopped incrementing.
|
||||||
|
|
||||||
|
## PAN-246420
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly during an upgrade.
|
||||||
|
|
||||||
|
## PAN-244950
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-2550](https://security.paloaltonetworks.com/CVE-2024-2550).
|
||||||
|
|
||||||
|
## PAN-221352
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-2550](https://security.paloaltonetworks.com/CVE-2024-2550).
|
||||||
|
|
||||||
|
## PAN-240251
|
||||||
|
|
||||||
|
Fixed an issue where the vldmgr process incorrectly restarted during an Elasticsearch restart.
|
||||||
|
|
||||||
|
## PAN-230825
|
||||||
|
|
||||||
|
Fixed an issue where link flaps occurred on Panorama appliances in high availability (HA) configurations.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
Fixed an issue where the Elasticsearch cluster health status displayed as yellow or red due to Elasticsearch SSH tunnel flaps.
|
||||||
|
|
||||||
|
## PAN-222579
|
||||||
|
|
||||||
|
Fixed an issue where the useridd and distd process restarted, which resulted in missing mappings.
|
||||||
|
|
||||||
|
## PAN-216941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances in Log Collector mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Panorama stopped processing and saving logs.
|
||||||
@@ -0,0 +1,525 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.8
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.8-h10
|
||||||
|
```
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the set deviceconfig setting preserve-prenat-feature no CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: show running application statistics.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-255868
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
After enabling kernel data collection during a silent reboot, the firewall fails and reboots to maintenance mode.
|
||||||
|
|
||||||
|
**Workaround:** To recover the firewall, initiate a reboot from maintenance mode.
|
||||||
|
|
||||||
|
## PAN-251895
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When Inline Cloud Analysis features are enabled, the firewall experiences a slow packet buffer leak, resulting in poor performance and dropped traffic.
|
||||||
|
|
||||||
|
**Workaround:** Disable WildFire Inline Cloud Analysis and Advanced Threat Prevention Inline Cloud Analysis on the firewall.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as out-of-sync on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now out-of-sync.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-242910
|
||||||
|
|
||||||
|
On the Panorama management server, Panorama administrators (**Panorama** > **Administrators**) that are assigned a custom Panorama admin role (**Panorama** > **Admin Roles**) with **Push All Changes** enabled are unable to push configuration changes to managed firewalls when **Managed Devices** and **Push For Other Admins** are disabled.
|
||||||
|
|
||||||
|
## PAN-242627
|
||||||
|
|
||||||
|
On the Panorama management server, selective configuration pushes fail with the following error message even when a full configuration push from Panorama was previously performed:Failed to generate selective push configuration. Schema validation failed. Please try a full push
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
admin debug elasticsearch es-restart all
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8-h13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Sessions might end unexpectedly with the error resources-unavailable when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
log-start eq no
|
||||||
|
|
||||||
|
log-end eq no
|
||||||
|
|
||||||
|
log-end eq yes
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
show -> dis-block-table is unexpected
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
debug software restart process log-receiver
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
admin > request plugins dlp reset
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,51 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9-h11
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
Fixed an issue where decryption based traffic failed on Explicit Proxy nodes.
|
||||||
|
|
||||||
|
## PAN-261917
|
||||||
|
|
||||||
|
Fixed an issue where websites with a no-decrypt policy rule were decrypted in traffic log when using a Google Chrome browser with PQC enabled
|
||||||
|
|
||||||
|
## PAN-260662
|
||||||
|
|
||||||
|
Fixed an issue where large file downloads were slower than expected when private IP address visibility was enabled.
|
||||||
|
|
||||||
|
## PAN-260218
|
||||||
|
|
||||||
|
Fixed an issue where BGP Aggregate Advertise filters did not work as expected when the summary option was enabled, and only summarized routes were advertised.
|
||||||
|
|
||||||
|
## PAN-258996
|
||||||
|
|
||||||
|
Fixed an issue where the firewall displayed the SFP ports as PowerDown when the SFP transceiver was removed and reinserted or the port was shut down and brought back up on the peer device.
|
||||||
|
|
||||||
|
## PAN-251661
|
||||||
|
|
||||||
|
Fixed an issue where a memory overwrite occurred during HTTP/2 header inflation.
|
||||||
|
|
||||||
|
## PAN-251563
|
||||||
|
|
||||||
|
Added CPLD enhancement to capture external power issues.
|
||||||
|
|
||||||
|
## PAN-240612
|
||||||
|
|
||||||
|
Fixed a kernel panic caused by a third-party issue.
|
||||||
|
|
||||||
|
## PAN-233191
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the Data Processing Card (DPC) restarted due to path monitor failure after QSFP28 disconnected from the Network Processing Card (NPC).
|
||||||
|
|
||||||
|
## PAN-226768
|
||||||
|
|
||||||
|
Fixed an issue where, when the GlobalProtect app was installed on iOS endpoints and the gateway was configured to accept cookies, the app remained in the **Connecting** stage after authentication, and the GlobalProtect log displayed the error message User is not in allow list. This occurred when the app was restarted or when the app attempted to reconnect after disconnection.
|
||||||
@@ -0,0 +1,95 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9-h14
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-264871
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the configd process stopped responding when viewing IP addresses on dynamic address groups with a large number of IP addresses.
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
Fixed an issue where decryption based traffic failed on Explicit Proxy nodes.
|
||||||
|
|
||||||
|
## PAN-262340
|
||||||
|
|
||||||
|
Fixed an issue where FQDN resolution failed for address objects, and all FQDN traffic was denied by the interzone-default policy rule.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
Fixed an issue where dereferencing a NULL pointer that occurred caused pan_task processes to stop responding.
|
||||||
|
|
||||||
|
## PAN-260928
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect failed to connect when using LDAP authentication with machine certificates with the error message You are not authorized to connect to GlobalProtect portal.
|
||||||
|
|
||||||
|
## PAN-260512
|
||||||
|
|
||||||
|
Fixed an issue where accessing the IP address of the device address group objects from the user interface caused the configd process to stop responding.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect portal was not accessible via a web browser and displayed the error ERR_EMPTY_RESPONSE.
|
||||||
|
|
||||||
|
## PAN-259002
|
||||||
|
|
||||||
|
Fixed an issue where frequent external dynamic list updates caused the configd process to restart.
|
||||||
|
|
||||||
|
## PAN-256077
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect client would disconnect consistently due to keep-alive timeouts when using an SSL-only tunnel.
|
||||||
|
|
||||||
|
## PAN-255619
|
||||||
|
|
||||||
|
Fixed an intermittent issue where file downloads from websites failed.
|
||||||
|
|
||||||
|
## PAN-255323
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the Network Processing Card (NPC), Data Processing Card (DPC), and Log forwarding Card (LFC) remained in a starting state after an unexpected power cycle.
|
||||||
|
|
||||||
|
## PAN-252669
|
||||||
|
|
||||||
|
Fixed an issue where the ikemgr process stopped responding with a SIGSEGV error.
|
||||||
|
|
||||||
|
## PAN-251929
|
||||||
|
|
||||||
|
Fixed an issue where inbound decryption did not work when FIPS self tests were turned on.
|
||||||
|
|
||||||
|
## PAN-250020
|
||||||
|
|
||||||
|
Fixed an issue where MLC2 verdict retrieval failed due to a regression in loopback data flag handling.
|
||||||
|
|
||||||
|
## PAN-248130
|
||||||
|
|
||||||
|
Fixed an issue where the **AND** operation under a Dynamic Address Group comparison did not work after upgrading the AWS plugin to 3.0.1.
|
||||||
|
|
||||||
|
## PAN-241044
|
||||||
|
|
||||||
|
Fixed an issue where traffic was denied by the interzone-default policy rule when a Security policy rule with an FQDN destination was configured.
|
||||||
|
|
||||||
|
## PAN-236133
|
||||||
|
|
||||||
|
Fixed an issue where SSL traffic was impacted when**SSL Command and Control detector** for Incline Cloud Analysis was set to **reset-both**, **reset-client**, **reset-server**, or **drop**.
|
||||||
|
|
||||||
|
## PAN-233681
|
||||||
|
|
||||||
|
Fixed an issue where the authd process on Prisma Access firewalls stopped responding after receiving the SIGUSR1 signal.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
Fixed an issue where sessions bypassed L7 inspection or ended unexpectedly with the error resources unavailable when the firewall incorrectly interpreted the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-222590
|
||||||
|
|
||||||
|
Fixed an issue where a semicolon appeared at the end of file names of data filtering logs.
|
||||||
|
|
||||||
|
## PAN-217198
|
||||||
|
|
||||||
|
Fixed an issue where Security policy rules did not display values for FQDN.
|
||||||
@@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9-h16
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-272809
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-0012](https://security.paloaltonetworks.com/CVE-2024-0012) ([PAN-SA-2024-0015](https://security.paloaltonetworks.com/PAN-SA-2024-0015)) and [CVE-2024-9474](https://security.paloaltonetworks.com/CVE-2024-9474).
|
||||||
|
|
||||||
|
## PAN-268314
|
||||||
|
|
||||||
|
Fixed an issue where new files were not sent to WildFire. With this fix, the WildFire reserved drive space has been increased for greater session caching capability.
|
||||||
|
|
||||||
|
## PAN-268002
|
||||||
|
|
||||||
|
Fixed an issue where URL filtering response pages were not displayed for sites that were blocked as a result of SSL/TLS handshake inspection.
|
||||||
|
|
||||||
|
## PAN-267535
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where DPDK allocated twice the amount of memory as requested for pre-allocation.
|
||||||
|
|
||||||
|
## PAN-257736
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where traffic to benign applications was was impacted by holding TCP sequential segments for MLC inspection and not releasing the full chain after a benign verdict was received.
|
||||||
|
|
||||||
|
## PAN-252036
|
||||||
|
|
||||||
|
Fixed an issue where, when the GlobalProtect portal was not configured, accessing the GlobalProtect gateway still loaded a portal malformed page.
|
||||||
|
|
||||||
|
## PAN-250787
|
||||||
|
|
||||||
|
Fixed an issue where network issues between the firewall and the log collector caused logrcvr process memory exhaustion.
|
||||||
|
|
||||||
|
## PAN-250394
|
||||||
|
|
||||||
|
Fixed an issue where a large amount of group data caused serialization errors and prevented synchronization.
|
||||||
|
|
||||||
|
## PAN-240251
|
||||||
|
|
||||||
|
Fixed an issue where the vldmgr process incorrectly restarted during an Elasticsearch restart.
|
||||||
|
|
||||||
|
## PAN-237010
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where local commits took longer than expected after an upgrade.
|
||||||
|
|
||||||
|
## PAN-229686
|
||||||
|
|
||||||
|
Fixed an issue where eBGP remained in an idle state after disabling and enabling BGP configurations.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
an issue where sessions bypassed L7 inspection or ended unexpectedly with the error resources unavailable when the firewall incorrectly interpreted the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-193285
|
||||||
|
|
||||||
|
Fixed an issue where the policy optimizer feature did not add entries back to the mongodb database after removing them during an upgrade or downgrade.
|
||||||
@@ -0,0 +1,123 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9-h18
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-268727
|
||||||
|
|
||||||
|
Fixed an issue where traffic was dropped when the accumulation proxy was enabled and header insertion modified packets.
|
||||||
|
|
||||||
|
## PAN-268314
|
||||||
|
|
||||||
|
Fixed an issue where new files were not sent to WildFire. With this fix, the WildFire reserved drive space has been increased for greater session caching capability.
|
||||||
|
|
||||||
|
## PAN-267704
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not send an ICMP error packet to Envoy when the MSS was exceeded.
|
||||||
|
|
||||||
|
## PAN-266427
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where, when a high number of SD-WAN branch sites or interfaces were not connected, SD-WAN processes and tund processes stopped responding due to a high probing rate.
|
||||||
|
|
||||||
|
## PAN-265900
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding due to a tund process or SD-WAN process restart.
|
||||||
|
|
||||||
|
## PAN-265742
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where the **OK** button on the GlobalProtect gateway configuration dialog box was not clickable.
|
||||||
|
|
||||||
|
## PAN-265111
|
||||||
|
|
||||||
|
Fixed an issue where fragmented SSL hello packets were reordered when going out of the SC/ZTT towards the datacenter.
|
||||||
|
|
||||||
|
## PAN-264169
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall sent correlated event logs to the syslog server using the management interface instead of the log interface.
|
||||||
|
|
||||||
|
## PAN-263973
|
||||||
|
|
||||||
|
Fixed an issue where log collectors had a low incoming log rate.
|
||||||
|
|
||||||
|
## PAN-262383
|
||||||
|
|
||||||
|
Fixed an issue where the firewall was unable to decompress the HTTP2 header, which caused the session to be classified as unknown-tcp instead of web-browsing.
|
||||||
|
|
||||||
|
## PAN-261673
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where, when Accelerated Networking was enabled, traffic was dropped because of the flow_parse_ip_hdr counter related to an Nvidia driver issue.
|
||||||
|
|
||||||
|
## PAN-260564
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in HA configurations where a network loop was detected by switches after suspending HA on the active firewall.
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Networking Cards (NC) experienced an internal link fault which caused path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-253213
|
||||||
|
|
||||||
|
Fixed an issue where the firewall sent HIP notifications every time it received a HIP report instead of every two hours.
|
||||||
|
|
||||||
|
## PAN-252730
|
||||||
|
|
||||||
|
Fixed an issue where the Elasticsearch status for a log collector group changed to red or yellow after performing a collector group push.
|
||||||
|
|
||||||
|
## PAN-246699
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the **Rule Usage** and **Apps Seen** under Security policy rules stopped incrementing.
|
||||||
|
|
||||||
|
## PAN-246420
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly during an upgrade.
|
||||||
|
|
||||||
|
## PAN-244950
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-2550](https://security.paloaltonetworks.com/CVE-2024-2550).
|
||||||
|
|
||||||
|
## PAN-221352
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-2550](https://security.paloaltonetworks.com/CVE-2024-2550).
|
||||||
|
|
||||||
|
## PAN-235877
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall failed to start up after upgrading PAN-OS due to system file corruption.
|
||||||
|
|
||||||
|
## PAN-226184
|
||||||
|
|
||||||
|
Fixed an issue where push operations from Panorama were slow due to the rasmgr process taking longer than expected.
|
||||||
|
|
||||||
|
## PAN-224833
|
||||||
|
|
||||||
|
Fixed an issue where the firewall dropped DHCPv6 relay packets if there were duplicate link-local addresses on different subinterfaces.
|
||||||
|
|
||||||
|
## PAN-216941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama appliances in Log Collector mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where Panorama stopped processing and saving logs.
|
||||||
@@ -0,0 +1,123 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9-h9
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-259480
|
||||||
|
|
||||||
|
Fixed an issue where the varrcvr process stopped responding after running out of memory due to how the process queued and dequeued files for WildFire file forwarding when a WildFire Analysis Security profile was enabled.
|
||||||
|
|
||||||
|
## PAN-259344
|
||||||
|
|
||||||
|
Fixed an issue where performing a configuration commit on a firewall locally or from Panorama caused a memory leak related to the configd process and resulted in a out-of-memory (OOM) condition.
|
||||||
|
|
||||||
|
## PAN-258941
|
||||||
|
|
||||||
|
Fixed an issue where some URLs were not accessible when connected to Prisma Access explicit proxy.
|
||||||
|
|
||||||
|
## PAN-258442
|
||||||
|
|
||||||
|
Fixed an issue where changes made to the split tunnel configuration on the Prisma Access gateway were not reflected on the GlobalProtect client.
|
||||||
|
|
||||||
|
## PAN-257919
|
||||||
|
|
||||||
|
Fixed an issue where, when using explicit proxy with SAML authentication, initiating SAML authentication with a non-GET request resulted in a **302 redirect** response instead of the expected **200 ok** response.
|
||||||
|
|
||||||
|
## PAN-257515
|
||||||
|
|
||||||
|
Fixed an issue where Possible Domain Fronting Detection for HTTP/2 generated false positives. With this change, domain fronting is limited to HTTP/1.
|
||||||
|
|
||||||
|
## PAN-257355
|
||||||
|
|
||||||
|
Fixed an issue where a false positive HTTP/TLS evasion alert was generated when the domain had DNS load balance.
|
||||||
|
|
||||||
|
## PAN-257197
|
||||||
|
|
||||||
|
Fixed an issue where ifType and ifSpeed were not populated in asynchronous mode of SNMP operations.
|
||||||
|
|
||||||
|
## PAN-256181
|
||||||
|
|
||||||
|
Fixed an issue where the management interface and front panel port interface statistics were not populated in asynchronous mode of SNMP operations.
|
||||||
|
|
||||||
|
## PAN-254422
|
||||||
|
|
||||||
|
Fixed an issue where the firewall required a restart when an SD-WAN policy rule was pushed from Panorama.
|
||||||
|
|
||||||
|
## PAN-254241
|
||||||
|
|
||||||
|
Fixed an issue where the firewall stopped responding due to a high number of SD-WAN probes being sent.
|
||||||
|
|
||||||
|
## PAN-252517
|
||||||
|
|
||||||
|
Fixed an issue where SNMP failed to respond to multiple Object Identifier (OID) queries in a single SNMP GET request.
|
||||||
|
|
||||||
|
## PAN-252214
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2024-3400](https://security.paloaltonetworks.com/CVE-2024-3400).
|
||||||
|
|
||||||
|
## PAN-251639
|
||||||
|
|
||||||
|
Fixed acn issue where an out-of-memory condition occurred due to a memory leak related to the varrvcr process when a WildFire Analysis security profile was enabled.
|
||||||
|
|
||||||
|
## PAN-251013
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where the **Virtual Router** and **Virtual System** configurations for the template incorrectly showed as **none**.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Fixed an issue where device telemetry failed after upgrading due to bundle generation failure.
|
||||||
|
|
||||||
|
## PAN-249814
|
||||||
|
|
||||||
|
Fixed an issue where multiple all_task processes stopped responding, which caused the dataplane to fail.
|
||||||
|
|
||||||
|
## PAN-247099
|
||||||
|
|
||||||
|
Fixed an issue where the firewall decrypted traffic unexpectedly when the client hello was spread across multiple packets.
|
||||||
|
|
||||||
|
## PAN-246960
|
||||||
|
|
||||||
|
Fixed an issue where firewalls failed to fetch content updates from the Wildfire Private Cloud due to an **Unsupported protocol** error.
|
||||||
|
|
||||||
|
## PAN-245125
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where file descriptors were not closed due to invalid configurations.
|
||||||
|
|
||||||
|
## PAN-244013
|
||||||
|
|
||||||
|
Fixed an issue where the web interface did not display newly added Anti-Spyware signatures or Vulnerability Signatures until you refreshed the browser or logged out or in via the web interface.
|
||||||
|
|
||||||
|
## PAN-242309
|
||||||
|
|
||||||
|
Fixed an issue where a higher byte count (s2c) was observed for DNS-Base application.
|
||||||
|
|
||||||
|
## PAN-239662
|
||||||
|
|
||||||
|
Fixed an issue with firewalls in active/passive high availability (HA) configurations where the NSSA default route from the active firewall was not generated to advertise even though the backbone area default route was advertised during a graceful restart.
|
||||||
|
|
||||||
|
## PAN-239143
|
||||||
|
|
||||||
|
Fixed an issue with accessing websites when URL filtering profiles were configured with the **block-continue** action and the server used HTTP/2.
|
||||||
|
|
||||||
|
## PAN-236909
|
||||||
|
|
||||||
|
Fixed an issue where, when you committed the first configuration change after booting up the firewall, the external dynamic list file download failed until the list was refreshed. This occurred when the configuration was pushed with a certificate profile.
|
||||||
|
|
||||||
|
## PAN-231440
|
||||||
|
|
||||||
|
Fixed an issue where, when a certificate profile was configured on an external dynamic list object but the profile had been deleted or did not exist, commits silently failed with the error Failed to refresh EDL config instead of showing the correct validation error message
|
||||||
|
|
||||||
|
## PAN-223418
|
||||||
|
|
||||||
|
Fixed an issue where heartbeats to the brdagent process were lost, resultng in the process not responding, which caused the firewall to reboot.
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where **Commit and Push** or **Push to Devices** operations failed when an external dynamic list was configured to check for updates every 5 minutes due to the commit and external dynamic fetch processes overlapping.
|
||||||
@@ -0,0 +1,119 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-250686
|
||||||
|
|
||||||
|
Fixed an issue where selective push operations did not work when more than one admin user simultaneously performed changes and partial commits on Panorama.
|
||||||
|
|
||||||
|
## PAN-247403
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the push scope CLI command took longer than expected, which caused the web interface to be slow.
|
||||||
|
|
||||||
|
## PAN-246431
|
||||||
|
|
||||||
|
Fixed an issue where a **Push to Device** operation remained at the state **None** when performing a selective push to device groups and templates that included both connected and disconnected firewalls.
|
||||||
|
|
||||||
|
## PAN-245701
|
||||||
|
|
||||||
|
Fixed an issue where the returned values to SNMP requests for data port statistics were incorrect.
|
||||||
|
|
||||||
|
## PAN-244836
|
||||||
|
|
||||||
|
A knob was introduced to toggle the default behavior of BGP in the Advanced Routing stack to not suppress duplicate updates. By default, the prefix updates are suppressed for optimization.
|
||||||
|
|
||||||
|
## PAN-244548
|
||||||
|
|
||||||
|
Fixed an issue where ECMP sessions changed destination MAC addresses mid-session, which caused connections to be reset.
|
||||||
|
|
||||||
|
## PAN-244493
|
||||||
|
|
||||||
|
Fixed a memory limitation with mapping subinterfaces to VPCE endpoints for GCP IPS, Amazon Web Services (AWS) integration with GWLB, and NSX service chain mapping.
|
||||||
|
|
||||||
|
## PAN-243463
|
||||||
|
|
||||||
|
Fixed an issue where high Enhanced Application Log traffic used excess system resources and caused processes to not work.
|
||||||
|
|
||||||
|
## PAN-242910
|
||||||
|
|
||||||
|
Fixed an issue where a custom based non-Superuser was unable to push to firewalls.
|
||||||
|
|
||||||
|
## PAN-242627
|
||||||
|
|
||||||
|
Fixed an issue where selective push did not work.
|
||||||
|
|
||||||
|
## PAN-241018
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed a Dataplane Development Kit (DPDK) issue where interfaces remained in a link-down stage after an Azure hot plug event.
|
||||||
|
|
||||||
|
## PAN-240477
|
||||||
|
|
||||||
|
Fixed a temporary hardware issue that caused PAN-SFP-PLUS-CU-5M to not be able to link up on PA-5400 Series, PA-3400 Series, and PA-1400 Series firewalls.
|
||||||
|
|
||||||
|
## PAN-240066
|
||||||
|
|
||||||
|
Fixed a duplicate MAC address issue where an ethernet interface sent out Gratuitous ARP (GARP) messages for an IP address that was not configured on it.
|
||||||
|
|
||||||
|
## PAN-239722
|
||||||
|
|
||||||
|
Fixed an issue where SNMP scans to the firewall took longer than expected and intermittently timed out.
|
||||||
|
|
||||||
|
## PAN-238643
|
||||||
|
|
||||||
|
Fixed an issue where a memory leak caused multiple processes to stop responding when VM Information Sources was configured.
|
||||||
|
|
||||||
|
## PAN-237991
|
||||||
|
|
||||||
|
Fixed an issue where the log collector sent fewer logs than expected to the syslog server.
|
||||||
|
|
||||||
|
## PAN-233692
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the configd process stopped, which caused performance issues.
|
||||||
|
|
||||||
|
## PAN-233684
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where **Push to Devices** or **Commit and Push** operations took longer than expected on the web interface.
|
||||||
|
|
||||||
|
## PAN-231439
|
||||||
|
|
||||||
|
Fixed an issue where, when a VoIP call using dynamic IP and NAT was put on hold, the audio became one-way due to early termination of NAT ports.
|
||||||
|
|
||||||
|
## PAN-230746
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where device groups with a large number of managed firewalls displayed the **Policy** page more slowly than expected.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
Fixed an issue where the Elasticsearch cluster health status displayed as yellow or red due to Elasticsearch SSH tunnel flaps.
|
||||||
|
|
||||||
|
## PAN-224500
|
||||||
|
|
||||||
|
Fixed an issue where IPv6 addresses in XFF were displayed in Traffic logs.
|
||||||
|
|
||||||
|
## PAN-222188
|
||||||
|
|
||||||
|
A CLI command was introduced to address an issue where SNMP monitoring performance was slower than expected, which resulted in snmpwalk timeouts.
|
||||||
|
|
||||||
|
## PAN-215430
|
||||||
|
|
||||||
|
Fixed an issue where dynamic IP address NAT with SIP intermittently failed to convert RTP Predict sessions.
|
||||||
|
|
||||||
|
## PAN-212553
|
||||||
|
|
||||||
|
Fixed an issue where the ikemgr process stopped responding due to memory corruption, which caused VPN tunnels to go down.
|
||||||
|
|
||||||
|
## PAN-207092
|
||||||
|
|
||||||
|
Fixed an issue where logging in using default credentials after changing to FIPS-CC for NSX-T firewalls did not work.
|
||||||
@@ -0,0 +1,986 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.0
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WIF-495
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, edits made to an existing data filtering profile (**Objects > DLP > Data Filtering Profiles**) can result in matching traffic not being detected by Enterprise DLP.
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-264281
|
||||||
|
|
||||||
|
When upgrading a ZTP firewall from PAN-OS 10.2 to PAN-OS 11.1 or later versions, if you use the **To SW Version** column to specify the target PAN-OS version, the upgrade process downloads and installs the intermediary base version containing an expired root certificate. This causes the ZTP firewall to lose connection with Panorama
|
||||||
|
|
||||||
|
**Workaround:** Follow the standard upgrade process from Panorama, which you use for non-ZTP firewalls, to upgrade to the target PAN-OS version that contains the valid root certificate.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-241536
|
||||||
|
|
||||||
|
On the Panorama management server, a user with an Admin Role is unable to modify or add filters to profiles under **Panorama** > **Network** > **Routing** > **Routing Profiles** > **Filters**, despite having the necessary read and write privileges.
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-229702
|
||||||
|
|
||||||
|
After upgrading a Panorama HA pair to PAN-OS 11.1, the ElasticSearch connectivity might fail to establish. The issue occurs because the client certificate on one of the Panorama devices does not have the necessary Extended Key Usage (EKU) set for server authentication, which is required for secure TLS communication.
|
||||||
|
|
||||||
|
**Workaround:**Contact Customer Support to renew the root client certificate.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
`admin>``debug elasticsearch es-restart optional all`
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-215778
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the M-600 appliance in Management Only mode, XML API Get requests for `/config` fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||||
|
|
||||||
|
`504 Gateway timeout`
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209937
|
||||||
|
|
||||||
|
Certificate-based authentication for administrator accounts may be unable to log into the Panorama or firewall web interface with the following error:
|
||||||
|
|
||||||
|
`Bad Request - Your browser sent a request that this server could not understand`
|
||||||
|
|
||||||
|
## PAN-208325
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||||
|
|
||||||
|
- M-300 and M-700
|
||||||
|
- PA-410 Firewall
|
||||||
|
- PA-440, PA-450, and PA-460 Firewalls
|
||||||
|
- PA-3400 Series
|
||||||
|
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||||
|
- PA-5450 Firewall
|
||||||
|
|
||||||
|
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||||
|
|
||||||
|
`admin>``request certificate fetch`
|
||||||
|
|
||||||
|
## PAN-207629
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, selective push fails to managed firewalls if the managed firewalls are enabled with multiple vsys and the Push Scope contains shared objects in device groups.
|
||||||
|
|
||||||
|
## PAN-206909
|
||||||
|
|
||||||
|
The Dedicated Log Collector is unable to reconnect to the Panorama management server if the `configd` process crashes. This results in the Dedicated Log Collector losing connectivity to Panorama despite the managed collector connection `Status` (**Panorama** > **Managed Collector**) displaying `connected` and the managed colletor `Health` status displaying as healthy.
|
||||||
|
|
||||||
|
This results in the local Panorama config and system logs not being forwarded to the Dedicated Log Collector. Firewall log forwarding to the disconnected Dedicated Log Collector is not impacted.
|
||||||
|
|
||||||
|
**Workaround:** Restart the `mgmtsrvr` process on the Dedicated Log Collector.
|
||||||
|
|
||||||
|
1. [Log in to the Dedicated Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli).
|
||||||
|
2. Confirm the Dedicated Log Collector is disconnected from Panorama.
|
||||||
|
`admin>``show panorama-status`
|
||||||
|
Verify the `Connected` status is `no`.
|
||||||
|
3. Restart the `mgmtsrvr` process.
|
||||||
|
`admin>``debug software restart process management-server`
|
||||||
|
|
||||||
|
## PAN-206268
|
||||||
|
|
||||||
|
On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (**Device** > **Setup** > **Management**) as part of a template or template stack configuration.
|
||||||
|
|
||||||
|
## PAN-206253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
For PA-3400 Series firewalls, the default log rate is set too low and the max configurable log rate is incorrectly capped resulting in the firewall not generating more than 6,826 logs per second.
|
||||||
|
|
||||||
|
## PAN-206243
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (**Monitor** > **Logs** > **System**) is generated each time the firewall reaches maximum disk usage capacity.
|
||||||
|
|
||||||
|
## PAN-205187
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
ElasticSearch may not start properly when a newly installed Panorama virtual appliance powers on for the first time, resulting in the Panorama virtual appliance being unable to query logs forwarded from the managed firewall to a Log Collector.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and start the PAN-OS software.
|
||||||
|
|
||||||
|
`admin>``request restart software`
|
||||||
|
|
||||||
|
## PAN-204663
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, you are unable to Context Switch from one managed firewall to another.
|
||||||
|
|
||||||
|
**Workaround:** After you Context Switch to a managed firewall, you must first Context Switch back to Panorama before you can continue to Context Switch to a different managed firewall.
|
||||||
|
|
||||||
|
## PAN-201855
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.
|
||||||
|
|
||||||
|
For example, you have template A, B, and C where templates A and B have certificates with the **Block Private Key Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||||
|
|
||||||
|
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||||
|
|
||||||
|
## PAN-199557
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in an Active/Passive high availability (HA) configuration, the `configd` process restarts due to a memory leak on the `Active` Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||||
|
|
||||||
|
**Workaround:** Manually reboot the `Active` Panorama HA peer.
|
||||||
|
|
||||||
|
## PAN-197341
|
||||||
|
|
||||||
|
On the Panorama management server, if you create multiple device group **Objects** with the same name in the Shared device group and any additional device groups (**Panorama** > **Device Groups**) under the same device group hierarchy that are used in one or more **Policies**, renaming the object with a shared name in any device group causes the object name to change in the policies where it is used. This issue applies only to device group objects that can be referenced in a Security policy rule.
|
||||||
|
|
||||||
|
For example:
|
||||||
|
|
||||||
|
1. You create a parent device group `DG-A` and a child device group `DG-B`.
|
||||||
|
2. You create address objects called `AddressObjA` in the `Shared`, `DG-A` and `DG-B` device groups and add `AddressObjA` to a Security policy rule under `DG-A` and `DG-B`.
|
||||||
|
3. Later, you change the `AddressObjA` name in the `Shared` device group to `AddressObjB`.
|
||||||
|
|
||||||
|
Changing the name of the address object in the `Shared` device group causes the references in the Policy rule to use the renamed `Shared` object instead of the device group object.
|
||||||
|
|
||||||
|
## PAN-197097
|
||||||
|
|
||||||
|
Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196720
|
||||||
|
|
||||||
|
During the CN-Series firewall deployment on Oracle OKEplatform, when you delete the deployment by deleting yamls, the MP/DP pods are stuck in Terminating state.
|
||||||
|
|
||||||
|
**Workaround:** Delete the CN-Series DP pods, MP pods, and then the pan-cni yaml file in a sequential order.
|
||||||
|
|
||||||
|
## PAN-194826
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
WF-500 appliance only
|
||||||
|
```
|
||||||
|
|
||||||
|
System log forwarding does not work over a TLS connection.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-193251
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
If SAML is configured as the authentication method for GlobalProtect, authentication on the Portal page is not successful in the browser.
|
||||||
|
|
||||||
|
**Workaround:** Use the GlobalProtect app installed on the endpoint to authenticate.
|
||||||
|
|
||||||
|
## PAN-192403
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
There is no commit warning in the web interface when configuring the management interface and logging interface in the same subnetwork. Having both interfaces in the same subnetwork can cause routing and connectivity issues.
|
||||||
|
|
||||||
|
## PAN-191570
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The Traffic Activity and SSL/TLS widgets in the **ACC** erroneously display `Report Error` if there is no SSL data to display.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-190435
|
||||||
|
|
||||||
|
When you **Commit** a configuration change, the **Task Manager** commit `Status` goes directly from `0%` to `Completed` and does accurately reflect the commit job progress.
|
||||||
|
|
||||||
|
## PAN-190311
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 and PA-220R firewalls and PA-800 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
There is an issue where management connectivity to the firewall is lost due to the expiration of the DHCP lease, which causes the IP configuration on the management port to be purged.
|
||||||
|
|
||||||
|
## PAN-189425
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, **Export Panorama and devices config bundle** (**Panorama** > **Setup** > **Operations**) fails to export. When the export fails, you are redirected to a new window and the following error is displayed:
|
||||||
|
|
||||||
|
`Failed to redirect error to /var/log/pan/appweb3-panmodule.log (Permission denied)`
|
||||||
|
|
||||||
|
## PAN-189395
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Running any version of PAN-OS 10.2 on a PA-400 Series firewall can cause the dataplane process to restart unexpectedly and trigger a crash.
|
||||||
|
|
||||||
|
## PAN-189380
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you successfully upgrade a PA-3000 Series firewall to PAN-OS 10.2.0 or later release and Enterprise data loss prevention (DLP) plugin 3.0.0 or later release, the first configuration push from the Panorama management server causes the firewall dataplane to crash.
|
||||||
|
|
||||||
|
**Workaround:** Restart the firewall to restore dataplane functionality.
|
||||||
|
|
||||||
|
1. [Log in to the firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli).
|
||||||
|
2. Restart the firewall.
|
||||||
|
`admin>` `request restart system`
|
||||||
|
|
||||||
|
## PAN-189361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Panorama is unable to distribute antivirus signature updates to firewalls with only an Advanced Threat Prevention license. Firewalls with previously installed and active Threat Prevention license are unaffected.
|
||||||
|
|
||||||
|
## PAN-189298
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On deploying the HA with 10.2.0-98 in Packet-mmap mode, the session sync for an existing session fails after restarting an active DP in Packet-mmap mode.
|
||||||
|
|
||||||
|
## PAN-189214
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the Advanced Threat Prevention license is present on a firewall without a Threat Prevention license, the antivirus signature update packages that are normally available to install under **Device** > **Dynamic Updates** are not displayed.
|
||||||
|
|
||||||
|
**Workaround:** Use the `request anti-virus upgrade {info | download | install}` CLI commands to retrieve a list of available antivirus updates and the download and installation status, download specific antivirus packages, and to install antivirus packages.Optionally, you can schedule recurring automatic updates using the following CLI command: `set deviceconfig system update-schedule anti-virus recurring`.
|
||||||
|
|
||||||
|
## PAN-189206
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Device Group and Template administrator roles don't support a context switch between the Panorama and firewall web interface.
|
||||||
|
|
||||||
|
**Workaround:** Use a Superuser or Panorama administrator role to context switch.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189106
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, you must uninstall the ZTP Plugin 2.0 before you can successfully downgrade to PAN-OS 10.1. After successful downgrade, you must reinstall the latest ZTP Plugin 1.0 version.
|
||||||
|
|
||||||
|
**Workaround:** Before you downgrade Panorama to PAN-OS 10.1, uninstall ZTP Plugin 2.0. After you successfully downgrade Panorama to PAN-OS 10.1, re-install ZTP Plugin 1.0 and re-enable ZTP functionality.
|
||||||
|
|
||||||
|
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html).
|
||||||
|
2. [Uninstall the ZTP Plugin](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/manage-firewalls/set-up-zero-touch-provisioning/uninstall-the-ztp-plugin.html).
|
||||||
|
3. Downgrade Panorama to PAN-OS 10.1.
|
||||||
|
4. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html).
|
||||||
|
5. [Install the ZTP plugin](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/manage-firewalls/set-up-zero-touch-provisioning/install-the-ztp-plugin/install-the-ztp-plugin-on-panorama.html).
|
||||||
|
6. Select **Panorama** > **Zero Touch Provisioning** and check (enable) **ZTP**.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-189057
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
HA configuration
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, Panorama enters a `non-functional` state due to `php.debug.log` life taking up too much space.
|
||||||
|
|
||||||
|
**Workaround:** Disable the debug flag for Panorama.
|
||||||
|
|
||||||
|
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface).
|
||||||
|
2. In the same browser you are logged into the Panorama web interface, enter the following URL.
|
||||||
|
`https://<panorama_ip>/debug`
|
||||||
|
3. Uncheck (disable) **Debug** or **Clear Debug**.
|
||||||
|
4. () Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.
|
||||||
|
|
||||||
|
## PAN-189032
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the firewall has Advanced Routing enabled, an OSPFv3 interface configured with the p2mp link type causes the commit to fail.
|
||||||
|
|
||||||
|
## PAN-188956
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After successful upgrade to PAN-OS 10.2, logging in to the firewall or Panorama web interface from the same Internet browser window or session from which the firewall or Panorama was upgraded displays the following error:
|
||||||
|
|
||||||
|
`Your login session has expired and you have been logged out for security reasons. Please log in again if you wish to continue.`
|
||||||
|
|
||||||
|
**Workaround:** The following are different ways to log in to the firewall or Panorama web interface after upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
- Close the browser and log in to the firewall or Panorama web interface from an entirely new browser session.
|
||||||
|
- Clear your browser cache for the browser from which you upgraded the firewall or Panorama.
|
||||||
|
- Log in to the firewall or Panorama web interface from the browser in Incognito mode.
|
||||||
|
If you upgraded the firewall or Panorama from a browser in Incognito mode, close the browser and log in to the firewall or Panorama web interface from an entirely new browser session.
|
||||||
|
- Log in to the firewall or Panorama web interface from a different browser than the one used to upgrade to PAN-OS.
|
||||||
|
|
||||||
|
## PAN-188904
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.
|
||||||
|
|
||||||
|
## PAN-188489
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, dynamic content updates are not automatically pushed to VM-Series firewalls licensed using the Panorama Software Firewall License plugin when **Automatically push content when software device registers to Panorama** (**Panorama** > **Templates** > **Add Stack**) is enabled.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-188064
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The SCP Server Profile configuration (**Devices** > **Server Profiles** > **SCP** are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.
|
||||||
|
|
||||||
|
## PAN-188052
|
||||||
|
|
||||||
|
Devices in FIPS-CC mode are unable to connect to servers utilizing ECDSA-based host keys that impacts exporting logs (**Device** > **Scheduled Log Export**), exporting configurations (**Device** > **Scheduled Config Export**), or the `scp export` command in the CLI.
|
||||||
|
|
||||||
|
**Workaround:** Use RSA-based host keys on the destination server.
|
||||||
|
|
||||||
|
## PAN-187846
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, a selective push (**Commit** > **Push to Devices** > **Push Changes Made By** and **Commit** > **Commit and Push** > **Commit and Push Changes Made By**) may push an incorrect configuration to managed firewalls causing the firewalls to display as *Out of Sync* if the Panorama pushed version for the Shared Policy and Template configuration (**Panorama** > **Managed Devices** > **Summary**) are 20 version or more older than the current local running configuration on Panorama.
|
||||||
|
|
||||||
|
To determine the current configuration version, select **Panorama** > **Config Audit**and expand the **Local Running config** menu to review the list of Panorama configuration versions.
|
||||||
|
|
||||||
|
**Workaround**: Push a more recent configuration to your managed firewalls before performing a selective push.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On PA-3400 & PA-5400 series firewalls (minus the PA-5450), the CLI and SNMP MIB walk do not display the Model and Serial-number of the Fan tray and PSUs.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-187234
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.
|
||||||
|
|
||||||
|
## PAN-186913
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, **Validate Device Group** (**Commit** > **Commit and Push** erroneously issues a CommitAll operation instead of a ValidateAll operation when multiple device groups are included in the push and results in no configuration validation.
|
||||||
|
|
||||||
|
**Workaround:** Validate device group configurations using one of the following methods.
|
||||||
|
|
||||||
|
- Select only one device group when you **Validate Device Group** for a **Commit and Push** to managed firewalls.
|
||||||
|
- To validate multiple device groups, select **Commit** > **Commit to Panorama** first. After the device group configuration is committed to Panorama, select **Commit** > **Push to Devices** and **Validate Device Group** to validate multiple device groups.
|
||||||
|
|
||||||
|
## PAN-186886
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Individual configuration objects cannot be viewed when you commit selective configuration changes (**Commit** > **Commit Changes Made By**) on a multi-vsys firewall.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-186262
|
||||||
|
|
||||||
|
The Panorama management server in Panorama or Log Collector mode may become unresponsive as Elasticsearch accumulates internal connections related to logging processes. The chances Panorama becomes unresponsive increases the longer Panorama remains powered on.
|
||||||
|
|
||||||
|
**Workaround:** Reboot Panorama if it becomes unresponsive.
|
||||||
|
|
||||||
|
## PAN-186137
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The management interface of the PA-3400 Series firewall incorrectly displays 10G port speed as an option. 10G speed is not supported on the PA-3400 Series firewall management port and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-186134
|
||||||
|
|
||||||
|
On the Panorama management server, performing a **Commit and Push** (**Commit > Commit and Push**) may intermittently not push the committed configuration changes to managed firewalls.
|
||||||
|
|
||||||
|
**Workaround:** Select **Commit > Push to Devices** to push the committed configuration changes to your managed firewalls.
|
||||||
|
|
||||||
|
## PAN-185966
|
||||||
|
|
||||||
|
The `debug skip-cert-renewal-check-syslog yes` command is not available on Log Collector CLI to stop the Dedicated Log Collector from trying to renew the device certificate and displaying the following error:
|
||||||
|
|
||||||
|
`No valid device certificate found`
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184708
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama managed firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
Scheduled report emails (**Monitor** > **PDF Reports** > **Email Scheduler**) are not emailed if:
|
||||||
|
|
||||||
|
- A scheduled report email contains a Report Group (**Monitor** > **PDF Reports** > **Report Group**) which includes a SaaS Application Usage report.
|
||||||
|
- A scheduled report contains only a SaaS Application Usage Report.
|
||||||
|
|
||||||
|
**Workaround:** To receive a scheduled report email for all other PDF report types:
|
||||||
|
|
||||||
|
1. Select **Monitor** > **PDF Reports** > **Report Groups** and remove all SaaS Application Usage reports from all Report Groups.
|
||||||
|
2. Select **Monitor** > **PDF Reports** > **Email Scheduler** and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select **Disable** and click **OK**.
|
||||||
|
Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
|
||||||
|
3. **Commit**.
|
||||||
|
() Select **Commit** > **Commit and Push**
|
||||||
|
|
||||||
|
## PAN-184702
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, an M-700 appliance in Log Collector mode fails to connect to Panorama when added as a managed collector (**Panorama > Managed Collectors**).
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the M-700 CLI](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli.html) and [recover the Log Collector connectivity to Panorama](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/recover-managed-device-connectivity-to-panorama.html).
|
||||||
|
|
||||||
|
## PAN-184474
|
||||||
|
|
||||||
|
When the firewall has Advanced Routing enabled, a static route stays active after the interface goes down.
|
||||||
|
|
||||||
|
**Workaround**: For firewalls that support Bidirectional Forwarding Detection (BFD), configure BFD for the static route.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183567
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, you must download and install the ZTP Plugin 2.0 after successful upgrade to PAN-OS 10.2. After upgrade to PAN-OS 10.2, the `show plugins installed` command does not display the ZTP plugin until you install ZTP Plugin 2.0.
|
||||||
|
|
||||||
|
**Workaround:** After Panorama successfully upgrades to PAN-OS 10.2, manually download and install the ZTP Plugin 2.0.
|
||||||
|
|
||||||
|
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html).
|
||||||
|
2. Select **Panorama** > **Plugins** and search for the `ztp` plugin.
|
||||||
|
3. **Download** and **Install** ZTP Plugin 2.0.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-182734
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||||
|
|
||||||
|
## PAN-182492
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The WildFire analysis report cannot be viewed from the firewall WildFire submission log entry page.
|
||||||
|
|
||||||
|
**Workaround**: You can retrieve the Wildfire analysis reports through the WildFire API or the WildFire portal.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-179420
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, a selective push (**Commit** > **Push to Devices** > **Push Changes Made By** and **Commit** > **Commit and Push** > **Commit and Push Changes Made By** to managed firewalls fails if you rename an existing device group, template, or template stack that was already pushed to your managed firewalls and you selectively committed specific configuration objects from the renamed device group, template, or template stack.
|
||||||
|
|
||||||
|
**Workaround:** After you rename the existing device group, template, or template stack, **Push** (**Commit** > **Push to Devices** all configuration changes for the named device group, template, or template stack.
|
||||||
|
|
||||||
|
## PAN-178195
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The URL filtering logs generated by traffic analyzed by Advanced URL filtering cloud inline categorization does not display the name of the URL.
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-176693
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The Activity (ACT) LEDs on the RJ-45 ports of the M-300 and M-700 appliances do not blink while processing network traffic.
|
||||||
|
|
||||||
|
## PAN-176156
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Executing `show running resource-monitor` with the `ingress-backlogs` option produces the following server error: `Dataplane is not up or invalid target-dp(*.dp*)`.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-172132
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved by PAN-189643. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
QoS fails to run on a tunnel interface (for example, tunnel.1).
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-171069
|
||||||
|
|
||||||
|
Local Log Collectors for Panorama management servers in active/passive high availability (HA) configuration cannot be added to the same Collector Group (**Panorama** > **Collector Groups**).
|
||||||
|
|
||||||
|
**Workaround:** Before you upgrade your Panorama servers to PAN-OS 10.1.0, configure HA (**Panorama** > **High Availability**), add the local Log Collectors of the HA peers to the same Collector Group, and upgrade to PAN 10.1.0.
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
|
|
||||||
|
## PAN-163676
|
||||||
|
|
||||||
|
Next-Gen Firewalls are unable to connect to a syslog server when the certificates required to connect to the syslog server are part of a Certificate Profile (**Device** > **Certificate Management** > **Certificate Profile**) if the **Use OCSP** setting is enabled to check the revocation status of certificates.
|
||||||
|
|
||||||
|
**Workaround:** Enable **Use CRL** to check the revocation status of certificates in the Certificate Profile.
|
||||||
@@ -0,0 +1,643 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-280196
|
||||||
|
|
||||||
|
After generating hipmatch/userid logs, the hipmatch logs written counter is missing from debug log-receiver statistics. This causes the firewall to match a HIP object but not on the HIP profile that contained the object.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.10-h2
|
||||||
|
```
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-286306
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||||
|
|
||||||
|
## PAN-286255
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.10-h17
|
||||||
|
```
|
||||||
|
|
||||||
|
When a firewall receives an unexpected termination request for certain SSL sessions , NGFW dataplane might experience a slow buffer resource leak.
|
||||||
|
|
||||||
|
**Workaround**: Disable accumulation proxy on the NGFW.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-282236
|
||||||
|
|
||||||
|
The firewall doesn't reassemble IPv6 packets correctly after they are fragmented.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||||
|
|
||||||
|
## PAN-275077
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
DNS Security intermittently logs malicious domain URLs as alert instead of taking a **sinkhole** action, even when configured to sinkhole malicious DNS domains.
|
||||||
|
|
||||||
|
## PAN-270549
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h2 through PAN-OS 10.2.10-h12) This issue is now resolved. See PAN-OS 10.2.10-h14 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Some TLS connections are not handled correctly leading to an instability in the dataplane of PAN-OS.
|
||||||
|
|
||||||
|
## PAN-269106
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
When using a cloud-based ML detection engine (MICA), the `wifclient` might crash during server cert verification for MICA gRPC connections and cause the dataplane to restart. On certain platforms, this might cause the firewall to reboot.
|
||||||
|
|
||||||
|
**Workaround**: Disable CRL using the following CLI command:`debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False`
|
||||||
|
|
||||||
|
## PAN-269052
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
Traffic might be blocked by a URL Filtering profile that isn't associated with the Security policy rule that the traffic matches.
|
||||||
|
|
||||||
|
## PAN-268823
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5250 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Applying filters under **Monitor** > **Log Display** either causes the logs to load slowly or not load at all.
|
||||||
|
|
||||||
|
## PAN-268815
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When using IoT Security, the `wifclient` might exit multiple times causing the firewall to reboot.
|
||||||
|
|
||||||
|
**Workaround**: Uninstall the IoT Security license and disable **Enable enhanced application logging** (**Device** > **Management** > **Cloud Logging** > **Cloud Logging Settings**).
|
||||||
|
|
||||||
|
## PAN-268260
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
On hardware firewalls where, when SSL decryption was enabled on layer 2, vwire, TAP, VLAN deployments, and Client Hello messages spanned multiple TCP segments, some SSL decryption sessions failed.
|
||||||
|
|
||||||
|
## PAN-267671
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
Exporting reports in PDF or CSV format and processing hourly scheduled report results can potentially trigger memory leaks. As a result, this can lead to process crashes and firewall reboots.
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h2 and 10.2.10-h3 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||||
|
|
||||||
|
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The command `show auth radius-require-msg-authentic` might return no output.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259997
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On PA-3410, PA-3420, and PA-3430 firewalls, the install fails when upgrading from PAN-OS 10.2.3-h3 and later 10.2 releases to PAN-OS 10.2.10 due the number of configured vsys zones exceeding the zone limit in PAN-OS 10.2.10.
|
||||||
|
|
||||||
|
**Workaround:** Before installing PAN-OS 10.2.10, reduce the number of security zones to 40 zones or fewer for PA-3410 and PA-3420 firewalls, and to 100 zones or fewer for PA-3430 firewalls.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-259733
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10-h2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Custom reports created in PAN-OS are not deleted as expected, resulting in high memory use by the reportd process. This can lead to issues, such as out-of-memory conditions, content installation failures, and unexpected firewall reboots.
|
||||||
|
|
||||||
|
## PAN-259344
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Performing a configuration commit on a firewall, either locally or from Panorama, causes a memory leak by the configd process and results in an out-of-memory (OOM) condition.
|
||||||
|
|
||||||
|
## PAN-258570
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.10-h9 only)This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The varrcvr process might progressively use more memory resulting in unexpected reboots when WildFire file forwarding is handling PE files.
|
||||||
|
|
||||||
|
## PAN-257957
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.12 Addressed Issues.Affects 10.2.10-h3 and later 10.2 releases.
|
||||||
|
```
|
||||||
|
|
||||||
|
If you enable FIPS-CC mode and use the PAP or CHAP authentication methods for your RADIUS server, the authd process may restart unexpectedly. To avoid this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- If you use PAN-OS 10.2.10-h3, 10.2.11, or an earlier version, configure the RADIUS server so that it does not send the message authenticator back to client.
|
||||||
|
- Use other protocols, such as LDAP, Kerberos, TACACS+, SAML, RADIUS EAP, instead of RADIUS PAP or CHAP.
|
||||||
|
- Change from FIPS mode to normal mode.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10-h7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,528 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.11
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||||
|
|
||||||
|
## PAN-265336
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11-h2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Copper ports flap when generating a technical support file, executing telemetry, or retrieving port status using a Management Data Input/Output (MDIO) read.
|
||||||
|
|
||||||
|
## PAN-264680
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-220 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
**Device** > **Setup** is not displayed when the Enterprise Data Loss Prevention (E-DLP) plugin is installed.
|
||||||
|
|
||||||
|
**Workaround:** Uninstall the Enterprise DLP plugin.
|
||||||
|
|
||||||
|
1. Log in to the firewall web interface.
|
||||||
|
2. Select **Device** > **Plugins**.
|
||||||
|
3. Search for `dlp`.
|
||||||
|
4. **Uninstall**.
|
||||||
|
|
||||||
|
## PAN-264580
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.11 results in the following error: `Target image validation failed with error invalid literal for int() with base 10`.
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||||
|
|
||||||
|
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The command `show auth radius-require-msg-authentic` might return no output.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-257957
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.12 Addressed Issues.Affects 10.2.11-h1 and later 10.2 releases.
|
||||||
|
```
|
||||||
|
|
||||||
|
If you enable FIPS-CC mode and use the PAP or CHAP authentication methods for your RADIUS server, the authd process may restart unexpectedly. To avoid this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- If you use PAN-OS 10.2.10-h3, 10.2.11, or an earlier version, configure the RADIUS server so that it does not send the message authenticator back to client.
|
||||||
|
- Use other protocols, such as LDAP, Kerberos, TACACS+, SAML, RADIUS EAP, instead of RADIUS PAP or CHAP.
|
||||||
|
- Change from FIPS mode to normal mode.
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```resolved
|
||||||
|
Fixed in PAN-OS 10.2.11. Affects 10.2.11-h2 and later 10.2 releases.
|
||||||
|
```
|
||||||
|
|
||||||
|
Networking cards can experience an internal link fault, causing path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in Traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11-h4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling the [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a JavaScript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on an M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to an M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 Series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific websites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (high availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the Traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the Advanced URL Filtering license, your license entitlements for PAN-DB and Advanced URL Filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,467 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.12
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
An SSL/TLS Client Hello may not be sent if the Client Hello arrives at the firewall in multiple TCP segments and the traffic is not subject to SSL decryption.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The command `show auth radius-require-msg-authentic` might return no output.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-257601
|
||||||
|
|
||||||
|
```resolved
|
||||||
|
Fixed in PAN-OS 10.2.11. Affects 10.2.11-h2 and later 10.2 releases.
|
||||||
|
```
|
||||||
|
|
||||||
|
Networking cards can experience an internal link fault, causing path monitoring failure on the Dataplane Processing Card (DPC).
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,622 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.13
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-297775
|
||||||
|
|
||||||
|
The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail.
|
||||||
|
|
||||||
|
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-293673
|
||||||
|
|
||||||
|
When the firewall generates a high volume of logs and attempts to export these logs to an FTP server, it may consume excessive memory leading to all PAN-OS processes crashing.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-289102
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
A race condition issue leads to a dataplane restart when a predict session is hit at the moment when it's timing out.
|
||||||
|
|
||||||
|
## PAN-288930
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h7 only) This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When ACE (App-ID Cloud Engine) is enabled, traffic from cloud applications might intermittently match an incorrect **cloud-apps** policy rule.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286306
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||||
|
|
||||||
|
## PAN-286255
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.13-h5 This issue is now resolved. See PAN-OS 10.2.13-h7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When a firewall receives an unexpected termination request for certain SSL sessions , NGFW dataplane might experience a slow buffer resource leak.
|
||||||
|
|
||||||
|
**Workaround**: Disable accumulation proxy on the NGFW.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||||
|
|
||||||
|
## PAN-285941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When netflow is enabled, the logrcvr process might get stuck, resulting in the local logging and log forwarding to stop functioning. Running debug log-receiver queue-stats on the CLI will show the "Logs discarded (queue full)" field incrementing over time.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-284066
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
After an upgrade, the `IF-MIB::ifInErrors` SNMP polled values display errors that don't match the results from the `show interface` CLI command.
|
||||||
|
|
||||||
|
## PAN-283467
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
The firewall might unexpectedly reboot and enter maintenance mode due to a ctd-agent out-of-memory (OOM) condition when undergoing advanced services load testing with a high volume of IoT EAL log forwarding.
|
||||||
|
|
||||||
|
**Workaround:** Limit the number of EAL logs generated by the firewall using the following CLI command: `debug iot eal key-value EAL_PENDING_BYTES=1000`.
|
||||||
|
|
||||||
|
## PAN-283331
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
Selective pushes to managed devices fail when the **User ID Master Device** is configured.
|
||||||
|
|
||||||
|
## PAN-282236
|
||||||
|
|
||||||
|
The firewall doesn't reassemble IPv6 packets correctly after they are fragmented.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279901
|
||||||
|
|
||||||
|
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||||
|
|
||||||
|
- The segmented Client Hello packets arrive out-of-order
|
||||||
|
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||||
|
- The first segment of the Client Hello packets is less than 5 bytes
|
||||||
|
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||||
|
|
||||||
|
## PAN-279746
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h1 through PAN-OS 10.2.13-h4) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
An SSL/TLS Client Hello may not be transmitted out of the firewall if the Client Hello arrives in multiple TCP segments and the traffic is not subject to SSL decryption (for example, SMTP over SSL).
|
||||||
|
|
||||||
|
## PAN-279604
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h3 only) This issue is now resolved. See PAN-OS 10.2.13-h4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The scheduled SaaS application usage reports are incorrectly generated and only the login page appears instead of the intended report content.
|
||||||
|
|
||||||
|
## PAN-275077
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
DNS Security intermittently logs malicious domain URLs as alert instead of taking a **sinkhole** action, even when configured to sinkhole malicious DNS domains.
|
||||||
|
|
||||||
|
## PAN-270849
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The configd process leaks a small amount of memory in every commit.
|
||||||
|
|
||||||
|
## PAN-269106
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When using a cloud-based ML detection engine (MICA), the `wifclient` might crash during server cert verification for MICA gRPC connections and cause the dataplane to restart. On certain platforms, this might cause the firewall to reboot.
|
||||||
|
|
||||||
|
**Workaround**: Disable CRL using the following CLI command:`debug iot eal key-value PAN_ICD_SERVER_CERT_USE_CRL=False`
|
||||||
|
|
||||||
|
## PAN-269052
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 and later 10.2.13 releases) This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
Traffic might be blocked by a URL Filtering profile that isn't associated with the Security policy rule that the traffic matches.
|
||||||
|
|
||||||
|
## PAN-268815
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h4 only) This issue is now resolved. See PAN-OS 10.2.13-h5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When using IoT Security, the `wifclient` might exit multiple times causing the firewall to reboot.
|
||||||
|
|
||||||
|
**Workaround**: Uninstall the IoT Security license and disable **Enable enhanced application logging** (**Device** > **Management** > **Cloud Logging** > **Cloud Logging Settings**).
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-261429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.15 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
The command `show auth radius-require-msg-authentic` might return no output.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,470 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.15
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-289102
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 Series, PA-5410, PA-5420, PA-5430, PA-5440, PA-5445, PA-3400 Series, PA-1400 Series, PA-400 Series, VM-Series, and CN-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
A race condition issue leads to a dataplane restart when a predict session is hit at the moment when it's timing out.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286306
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285941
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.13-h7 only) This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When netflow is enabled, the logrcvr process might get stuck, resulting in the local logging and log forwarding to stop functioning. Running debug log-receiver queue-stats on the CLI will show the "Logs discarded (queue full)" field incrementing over time.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-284066
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
After an upgrade, the `IF-MIB::ifInErrors` SNMP polled values display errors that don't match the results from the `show interface` CLI command.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279901
|
||||||
|
|
||||||
|
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||||
|
|
||||||
|
- The segmented Client Hello packets arrive out-of-order
|
||||||
|
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||||
|
- The first segment of the Client Hello packets is less than 5 bytes
|
||||||
|
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,369 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.16
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-297775
|
||||||
|
|
||||||
|
The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail.
|
||||||
|
|
||||||
|
**Workaround**: Change the vsys display name so that it doesn't reference an existing vsys ID.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-293673
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h4 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When the firewall generates a high volume of logs and attempts to export these logs to an FTP server, it may consume excessive memory leading to all PAN-OS processes crashing.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287803
|
||||||
|
|
||||||
|
Users might be unable to access some URLs due to issues involving the accumulation proxy and the Path Maximum Transmission Unit (MTU).
|
||||||
|
|
||||||
|
To address this issue, use one of the following workarounds:
|
||||||
|
|
||||||
|
- Configure the **Adjust TCP MSS** option for the egress interface to the unreachable server. The amount to adjust the maximum segment size depends on the path to the server.
|
||||||
|
- Disable the accumulation proxy using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286306
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When getting transceiver information from ESCC for SFP 25G modules, the transceiver code incorrectly displays `Unknown` instead of `25GBase-SR`.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-279901
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.16 and PAN-OS 10.2.16-h1)
|
||||||
|
```
|
||||||
|
|
||||||
|
When decryption is enabled, segmented Client Hello packets can cause website access issues and memory leaks under the following conditions:
|
||||||
|
|
||||||
|
- The segmented Client Hello packets arrive out-of-order
|
||||||
|
- The segmented Client Hello packets arrive out-of-order and can be reassembled into a complete Client Hello when the first contiguous segment is formed by NGFW
|
||||||
|
- The first segment of the Client Hello packets is less than 5 bytes
|
||||||
|
- A decryption policy rule excludes this traffic from decryption and a Security policy rule (URL filtering) denies this session
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,357 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.18
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-266900
|
||||||
|
|
||||||
|
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
@@ -0,0 +1,776 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.1
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
`admin>``debug elasticsearch es-restart optional all`
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-215778
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the M-600 appliance in Management Only mode, XML API Get requests for `/config` fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||||
|
|
||||||
|
`504 Gateway timeout`
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208325
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||||
|
|
||||||
|
- M-300 and M-700
|
||||||
|
- PA-410 Firewall
|
||||||
|
- PA-440, PA-450, and PA-460 Firewalls
|
||||||
|
- PA-3400 Series
|
||||||
|
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||||
|
- PA-5450 Firewall
|
||||||
|
|
||||||
|
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||||
|
|
||||||
|
`admin>``request certificate fetch`
|
||||||
|
|
||||||
|
## PAN-207629
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, selective push fails to managed firewalls if the managed firewalls are enabled with multiple vsys and the Push Scope contains shared objects in device groups.
|
||||||
|
|
||||||
|
## PAN-206268
|
||||||
|
|
||||||
|
On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (**Device** > **Setup** > **Management**) as part of a template or template stack configuration.
|
||||||
|
|
||||||
|
## PAN-206253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
For PA-3400 Series firewalls, the default log rate is set too low and the max configurable log rate is incorrectly capped resulting in the firewall not generating more than 6,826 logs per second.
|
||||||
|
|
||||||
|
## PAN-206243
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (**Monitor** > **Logs** > **System**) is generated each time the firewall reaches maximum disk usage capacity.
|
||||||
|
|
||||||
|
## PAN-205187
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
ElasticSearch may not start properly when a newly installed Panorama virtual appliance powers on for the first time, resulting in the Panorama virtual appliance being unable to query logs forwarded from the managed firewall to a Log Collector.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and start the PAN-OS software.
|
||||||
|
|
||||||
|
`admin>``request restart software`
|
||||||
|
|
||||||
|
## PAN-204663
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, you are unable to Context Switch from one managed firewall to another.
|
||||||
|
|
||||||
|
**Workaround:** After you Context Switch to a managed firewall, you must first Context Switch back to Panorama before you can continue to Context Switch to a different managed firewall.
|
||||||
|
|
||||||
|
## PAN-201855
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.
|
||||||
|
|
||||||
|
For example, you have template A, B, and C where templates A and B have certificates with the **Block Private Key Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||||
|
|
||||||
|
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||||
|
|
||||||
|
## PAN-199557
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in an Active/Passive high availability (HA) configuration, the `configd` process restarts due to a memory leak on the `Active` Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||||
|
|
||||||
|
**Workaround:** Manually reboot the `Active` Panorama HA peer.
|
||||||
|
|
||||||
|
## PAN-197097
|
||||||
|
|
||||||
|
Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-194826
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
WF-500 appliance only
|
||||||
|
```
|
||||||
|
|
||||||
|
System log forwarding does not work over a TLS connection.
|
||||||
|
|
||||||
|
## PAN-194708
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
URL filtering logs (**Monitor** > **Logs** > **URL Filtering**) erroneously truncate a 16KB Header value and do not display the Header values that follow the truncated 16KB header.
|
||||||
|
|
||||||
|
For example, a URL filtering log has 5 Headers. The second Header has a 16KB value. In the URL filtering log, the first header and the value are displayed, second Header value is truncated, and remaining three headers are not displayed.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-193251
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
If SAML is configured as the authentication method for GlobalProtect, authentication on the Portal page is not successful in the browser.
|
||||||
|
|
||||||
|
**Workaround:** Use the GlobalProtect app installed on the endpoint to authenticate.
|
||||||
|
|
||||||
|
## PAN-192403
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
There is no commit warning in the web interface when configuring the management interface and logging interface in the same subnetwork. Having both interfaces in the same subnetwork can cause routing and connectivity issues.
|
||||||
|
|
||||||
|
## PAN-190735
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain webpages that use chunked-encoded data transfers might not load properly when analyzed by Advanced URL Filtering cloud inline categorization.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-190435
|
||||||
|
|
||||||
|
When you **Commit** a configuration change, the **Task Manager** commit `Status` goes directly from `0%` to `Completed` and does accurately reflect the commit job progress.
|
||||||
|
|
||||||
|
## PAN-189425
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, **Export Panorama and devices config bundle** (**Panorama** > **Setup** > **Operations**) fails to export. When the export fails, you are redirected to a new window and the following error is displayed:
|
||||||
|
|
||||||
|
`Failed to redirect error to /var/log/pan/appweb3-panmodule.log (Permission denied)`
|
||||||
|
|
||||||
|
## PAN-189395
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Running any version of PAN-OS 10.2.1 on a PA-400 Series firewall can cause the dataplane process to restart unexpectedly and trigger a crash.
|
||||||
|
|
||||||
|
## PAN-189380
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you successfully upgrade a PA-3000 Series firewall to PAN-OS 10.2.0 or later release and Enterprise data loss prevention (DLP) plugin 3.0.0 or later release, the first configuration push from the Panorama management server causes the firewall dataplane to crash.
|
||||||
|
|
||||||
|
**Workaround:** Restart the firewall to restore dataplane functionality.
|
||||||
|
|
||||||
|
1. [Log in to the firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli).
|
||||||
|
2. Restart the firewall.
|
||||||
|
`admin>` `request restart system`
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-189057
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
HA configuration
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, Panorama enters a `non-functional` state due to `php.debug.log` life taking up too much space.
|
||||||
|
|
||||||
|
**Workaround:** Disable the debug flag for Panorama.
|
||||||
|
|
||||||
|
1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface).
|
||||||
|
2. In the same browser you are logged into the Panorama web interface, enter the following URL.
|
||||||
|
`https://<panorama_ip>/debug`
|
||||||
|
3. Uncheck (disable) **Debug** or **Clear Debug**.
|
||||||
|
4. () Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.
|
||||||
|
|
||||||
|
## PAN-188904
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.
|
||||||
|
|
||||||
|
## PAN-188489
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, dynamic content updates are not automatically pushed to VM-Series firewalls licensed using the Panorama Software Firewall License plugin when **Automatically push content when software device registers to Panorama** (**Panorama** > **Templates** > **Add Stack**) is enabled.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-188064
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The SCP Server Profile configuration (**Devices** > **Server Profiles** > **SCP** are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187429
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On PA-3400 & PA-5400 series firewalls (minus the PA-5450), the CLI and SNMP MIB walk do not display the Model and Serial-number of the Fan tray and PSUs.
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-187234
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.
|
||||||
|
|
||||||
|
## PAN-186913
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, **Validate Device Group** (**Commit** > **Commit and Push** erroneously issues a CommitAll operation instead of a ValidateAll operation when multiple device groups are included in the push and results in no configuration validation.
|
||||||
|
|
||||||
|
**Workaround:** Validate device group configurations using one of the following methods.
|
||||||
|
|
||||||
|
- Select only one device group when you **Validate Device Group** for a **Commit and Push** to managed firewalls.
|
||||||
|
- To validate multiple device groups, select **Commit** > **Commit to Panorama** first. After the device group configuration is committed to Panorama, select **Commit** > **Push to Devices** and **Validate Device Group** to validate multiple device groups.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-186262
|
||||||
|
|
||||||
|
The Panorama management server in Panorama or Log Collector mode may become unresponsive as Elasticsearch accumulates internal connections related to logging processes. The chances Panorama becomes unresponsive increases the longer Panorama remains powered on.
|
||||||
|
|
||||||
|
**Workaround:** Reboot Panorama if it becomes unresponsive.
|
||||||
|
|
||||||
|
## PAN-186134
|
||||||
|
|
||||||
|
On the Panorama management server, performing a **Commit and Push** (**Commit > Commit and Push**) may intermittently not push the committed configuration changes to managed firewalls.
|
||||||
|
|
||||||
|
**Workaround:** Select **Commit > Push to Devices** to push the committed configuration changes to your managed firewalls.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184708
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Panorama managed firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
Scheduled report emails (**Monitor** > **PDF Reports** > **Email Scheduler**) are not emailed if:
|
||||||
|
|
||||||
|
- A scheduled report email contains a Report Group (**Monitor** > **PDF Reports** > **Report Group**) which includes a SaaS Application Usage report.
|
||||||
|
- A scheduled report contains only a SaaS Application Usage Report.
|
||||||
|
|
||||||
|
**Workaround:** To receive a scheduled report email for all other PDF report types:
|
||||||
|
|
||||||
|
1. Select **Monitor** > **PDF Reports** > **Report Groups** and remove all SaaS Application Usage reports from all Report Groups.
|
||||||
|
2. Select **Monitor** > **PDF Reports** > **Email Scheduler** and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select **Disable** and click **OK**.
|
||||||
|
Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
|
||||||
|
3. **Commit**.
|
||||||
|
() Select **Commit** > **Commit and Push**
|
||||||
|
|
||||||
|
## PAN-184702
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, an M-700 appliance in Log Collector mode fails to connect to Panorama when added as a managed collector (**Panorama > Managed Collectors**).
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the M-700 CLI](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli.html) and [recover the Log Collector connectivity to Panorama](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/recover-managed-device-connectivity-to-panorama.html).
|
||||||
|
|
||||||
|
## PAN-184474
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the firewall has Advanced Routing enabled, a static route stays active after the interface goes down.
|
||||||
|
|
||||||
|
**Workaround**: For firewalls that support Bidirectional Forwarding Detection (BFD), configure BFD for the static route.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-182734
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-176156
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
Executing `show running resource-monitor` with the `ingress-backlogs` option produces the following server error: `Dataplane is not up or invalid target-dp(*.dp*)`.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-172132
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved by PAN-189643. See PAN-OS 10.2.4 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
QoS fails to run on a tunnel interface (for example, tunnel.1).
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,632 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.4
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-227342
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
In an Active/Active High Availability (HA) setup, enabling hardware offload can result in web traffic being blocked.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
`admin>``debug elasticsearch es-restart optional all`
|
||||||
|
|
||||||
|
## PAN-220180
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-216821
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The `reportd` process crashes after you successfully upgrade an M-200 appliance to PAN-OS 10.2.4.
|
||||||
|
|
||||||
|
## PAN-215778
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the M-600 appliance in Management Only mode, XML API Get requests for `/config` fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.
|
||||||
|
|
||||||
|
`504 Gateway timeout`
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212978
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The Palo Alto Networks firewall stops responding when executing an SD-WAN debug operational CLI command.
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-210366
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.4-h3 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in a high availability (HA) configuration, the primary HA peer may enter a `primary-non-functional` state and generate a system log (**Monitor** > **Logs** > **System**) with the following message:
|
||||||
|
|
||||||
|
`High root partition usage: going to state Non-Functional`
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-208325
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).
|
||||||
|
|
||||||
|
- M-300 and M-700
|
||||||
|
- PA-410 Firewall
|
||||||
|
- PA-440, PA-450, and PA-460 Firewalls
|
||||||
|
- PA-3400 Series
|
||||||
|
- PA-5410, PA-5420, and PA-5430 Firewalls
|
||||||
|
- PA-5450 Firewall
|
||||||
|
|
||||||
|
**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.
|
||||||
|
|
||||||
|
`admin>``request certificate fetch`
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||||
|
|
||||||
|
## PAN-201855
|
||||||
|
|
||||||
|
On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.
|
||||||
|
|
||||||
|
For example, you have template A, B, and C where templates A and B have certificates with the **Block Private Key Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.
|
||||||
|
|
||||||
|
**Workaround:** After cloning a template, delete and re-import the corrupted certificates.
|
||||||
|
|
||||||
|
## PAN-199557
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in an Active/Passive high availability (HA) configuration, the `configd` process restarts due to a memory leak on the `Active` Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.
|
||||||
|
|
||||||
|
**Workaround:** Manually reboot the `Active` Panorama HA peer.
|
||||||
|
|
||||||
|
## PAN-198708
|
||||||
|
|
||||||
|
On the Panorama management server, the `File Type` field does not display any data when you view the Detailed Log View in the Data Filtering log (**Monitor** > **Logs** > **Data Filtering** > **<select log>** > **DLP**).
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-196146
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-190435
|
||||||
|
|
||||||
|
When you **Commit** a configuration change, the **Task Manager** commit `Status` goes directly from `0%` to `Completed` and does accurately reflect the commit job progress.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-182734
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
|
|
||||||
|
## PAN-160633
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3200 Series, PA-5200 Series, and PA-7000 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
The dataplane restarts repeatedly due to internal path monitoring failures until a power cycle.
|
||||||
@@ -0,0 +1,639 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.6
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-304756
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h18 Addressed Issuesand PAN-OS 10.2.16-h6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After you disable the shared optimization feature in Panorama, ensure that you perform a full configuration push to all managed multi-vsys devices to re-establish a baseline. Failure to include every device group associated with the multi-vsys device during this push may result in incomplete or inconsistent configurations across virtual systems.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-244648
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5200 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
After a factory reset, the firewall may get stuck in maintenance mode and be unable to load the boot image. The firewall fails to enable FIPS-CC mode during this time.
|
||||||
|
|
||||||
|
**Workaround:** The following workaround allows the firewall to boot in normal mode but does not apply to FIPS-CC mode. Attempting to enable FIPS-CC mode after using this workaround will cause the firewall to reboot and re-enter maintenace mode.
|
||||||
|
|
||||||
|
1. Enter maintenance mode.
|
||||||
|
2. Select **Disk Image** > **Advanced Options**.
|
||||||
|
3. Select **Bootstrap** with the options `panos-10.2.8`, `maint`, and `maint`.
|
||||||
|
4. Select **Bootstrap** with the options `panos-10.2.8`, `sysroot0`, and `panos`.
|
||||||
|
5. Select **Bootstrap** with the option `sysroot0`.
|
||||||
|
6. Select **Reboot**.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-234929
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The tabs in the **ACC**, such as **Network Activity**, **Threat Activity**, and **Blocked Activity**, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-225337
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:
|
||||||
|
|
||||||
|
1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called `SharedAO1` and a vsys-specific address object also called `SharedAO1`.
|
||||||
|
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (`SharedAO1`) in a **Shared** address group called `SharedAG1`.
|
||||||
|
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (`SharedAG1`) in a vsys-specific policy rule.
|
||||||
|
|
||||||
|
**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:
|
||||||
|
|
||||||
|
- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
|
||||||
|
This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
|
||||||
|
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
|
||||||
|
This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** `SharedAO1` object was `10.1.1.1` and the device group specific `SharedAO1` was `10.2.2.2`, the `10.1.1.1` IP address takes precedence.
|
||||||
|
|
||||||
|
Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-227368
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The GlobalProtect app cannot connect to a portal or gateway and GlobalProtect Clientless VPN users cannot access applications if authentication takes longer than 20 seconds.
|
||||||
|
|
||||||
|
**Workaround:** Increase the TCP handshake timeout to the maximum value of 60 seconds.
|
||||||
|
|
||||||
|
## PAN-226768
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the GlobalProtect app is installed on iOS endpoints and the gateway is configured to accept cookies, the app stays in `Connecting` stage after authentication and the GlobalProtect log displays the error message, **User is not in allow list**. This happens when the app is restarted or when the app tries to reconnect after disconnection.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-223488
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.
|
||||||
|
|
||||||
|
## PAN-223457
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
If the number of group queries exceeds the Okta rate limit threshold, the firewall clears the cache for the groups. To avoid encountering this issue, disable the Okta rate limit.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222418
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The firewall intermittently records a reconnection message to the authentication server as a error, even if no disconnection occurs.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221857
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Users are unable to log in to the GlobalProtect app using SAML authentication after the app is upgraded to 10.2.3-h4 and the GlobalProtect logs display the following error message: **Username from SAML SSO response is different from the input.**.
|
||||||
|
|
||||||
|
## PAN-221126
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Email server profiles (**Device** > **Server Profiles** > **Email** and **Panorama** > **Server Profiles** > **Email**) to forward logs as email notifications are not forwarded in a readable format.
|
||||||
|
|
||||||
|
**Workaround:** Use a **Custom Log Format** to forward logs as email notifications in a readable format.
|
||||||
|
|
||||||
|
## PAN-221015
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On M-600 appliances in Panorama or Log Collector mode, the `es-1` and `es-2` ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector `ES` health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.
|
||||||
|
|
||||||
|
`admin>``debug elasticsearch es-restart optional all`
|
||||||
|
|
||||||
|
## PAN-220180
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-218521
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-196146
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-193004
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama management server fails to delete old IP Tag data. This causes the `/opt/pancfg` partition to reach maximum capacity which impacts Panorama performance.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,609 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-273730
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000 Series only
|
||||||
|
```
|
||||||
|
|
||||||
|
The web interface is unresponsive after upgrading to PAN-OS 10.2.7-h18. The following error is generated: `PHP Fatal error: require(): Failed opening required`
|
||||||
|
|
||||||
|
**Workaround:** Use the CLI to downgrade or upgrade to another version.
|
||||||
|
|
||||||
|
## PAN-262263
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 and PA-5400 Series firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
The links on the firewall's RJ-45 ports may go up and down additional times during a reboot, causing unexpected downtime.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-244673
|
||||||
|
|
||||||
|
Upgrading a flexible-vCPU VM-Series firewall HA deployment from 10.1.x directly to 10.2.3 or later causes the active HA peer to become unresponsive. In this scenario, the upgraded firewall then becomes the active peer.
|
||||||
|
|
||||||
|
**Workaround**: Upgrade the VM-Series firewalls to PAN-OS 10.2.2 before upgrading to the latest PAN-OS 10.2.x version.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-242910
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PAN-OS 10.2.7, 10.2.7-h1, and 10.2.7-h3 only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, Panorama administrators (**Panorama** > **Administrators**) that are assigned a custom Panorama admin role (**Panorama** > **Admin Roles**) with **Push All Changes** enabled are unable to push configuration changes to managed firewalls when **Managed Devices** and **Push For Other Admins** are disabled.
|
||||||
|
|
||||||
|
## PAN-242837
|
||||||
|
|
||||||
|
Default login credentials and SSH fail after enabling FIPS-CC Mode on a firewall or Panorama after converting through the Maintenance Recovery Tool (MRT). The firewall or Panorama becomes stuck and requires a factory reset to recover.
|
||||||
|
|
||||||
|
## PAN-242561
|
||||||
|
|
||||||
|
On the PAN-OS 10.2.7-h3 version, GlobalProtect tunnel might disconnect shortly after being established when SSL is used as a transport protocol.
|
||||||
|
|
||||||
|
**Workaround**: Disable Internet Protocol version 6 (TCP/IPv6) on the PANGP Virtual Network Adapter.
|
||||||
|
|
||||||
|
## PAN-238769
|
||||||
|
|
||||||
|
FIPS-CC VM only. Upgrading to 10.1.10-h2 or 10.1.11 will change all locally created security Policy actions to Deny. Re-load the back-up config taken before upgrading or the last version to get the previous config back. Also, Unable to login to FIPSCC Mode devices with default credentials after converting the mode for 10.1.12 release , 10.2.7 release , 11.1.0 , 11.1.1, 11.0.3 versions.
|
||||||
|
|
||||||
|
## PAN-234929
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.7-h3 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The tabs in the **ACC**, such as **Network Activity**, **Threat Activity**, and **Blocked Activity**, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||||
|
|
||||||
|
## PAN-228273
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the `show log-collector-es-cluster health` command displays the `status` is `red`. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.
|
||||||
|
|
||||||
|
## PAN-227344
|
||||||
|
|
||||||
|
On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-226768
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When the GlobalProtect app is installed on iOS endpoints and the gateway is configured to accept cookies, the app stays in `Connecting` stage after authentication and the GlobalProtect log displays the error message, **User is not in allow list**. This happens when the app is restarted or when the app tries to reconnect after disconnection.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-223457
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
If the number of group queries exceeds the Okta rate limit threshold, the firewall clears the cache for the groups. To avoid encountering this issue, disable the Okta rate limit.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-222418
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The firewall intermittently records a reconnection message to the authentication server as a error, even if no disconnection occurs.
|
||||||
|
|
||||||
|
## PAN-222253
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-221857
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Users are unable to log in to the GlobalProtect app using SAML authentication after the app is upgraded to 10.2.3-h4 and the GlobalProtect logs display the following error message: **Username from SAML SSO response is different from the input.**.
|
||||||
|
|
||||||
|
## PAN-221033
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The firewall is responding to an ARP request for an IP address in the firewall's NAT address pool when that IP address isn't in the same subnet as the IP address of the ingress interface.
|
||||||
|
|
||||||
|
## PAN-220180
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Configured botnet reports (**Monitor** > **Botnet**) are not generated.
|
||||||
|
|
||||||
|
## PAN-219644
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-215082
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-196146
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The VM-Series firewall on Azure does not boot up with a hostname (specified in an init-cgf.txt or user data) when bootstrapped.
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-185286
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,525 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.8
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.8-h10
|
||||||
|
```
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-287056
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A BGP export policy rule that matches on a next hop fails to block the advertisement of static routes, and the firewall incorrectly matches the egress interface IP address instead of the original next-hop IP address of the static route, which causes the deny rule to fail.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-255868
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3400 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
After enabling kernel data collection during a silent reboot, the firewall fails and reboots to maintenance mode.
|
||||||
|
|
||||||
|
**Workaround:** To recover the firewall, initiate a reboot from maintenance mode.
|
||||||
|
|
||||||
|
## PAN-251895
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When Inline Cloud Analysis features are enabled, the firewall experiences a slow packet buffer leak, resulting in poor performance and dropped traffic.
|
||||||
|
|
||||||
|
**Workaround:** Disable WildFire Inline Cloud Analysis and Advanced Threat Prevention Inline Cloud Analysis on the firewall.
|
||||||
|
|
||||||
|
## PAN-250062
|
||||||
|
|
||||||
|
Device telemetry might fail at configured intervals due to bundle generation issues.
|
||||||
|
|
||||||
|
## PAN-243951
|
||||||
|
|
||||||
|
On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as `out-of-sync` on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.
|
||||||
|
|
||||||
|
**Workaround:** Manually synchronize the Panorama HA peers.
|
||||||
|
|
||||||
|
1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
|
||||||
|
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
|
||||||
|
On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now `out-of-sync`.
|
||||||
|
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
|
||||||
|
*request high-availability sync-to-remote running-config*
|
||||||
|
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.
|
||||||
|
|
||||||
|
## PAN-242910
|
||||||
|
|
||||||
|
On the Panorama management server, Panorama administrators (**Panorama** > **Administrators**) that are assigned a custom Panorama admin role (**Panorama** > **Admin Roles**) with **Push All Changes** enabled are unable to push configuration changes to managed firewalls when **Managed Devices** and **Push For Other Admins** are disabled.
|
||||||
|
|
||||||
|
## PAN-242627
|
||||||
|
|
||||||
|
On the Panorama management server, selective configuration pushes fail with the following error message even when a full configuration push from Panorama was previously performed:Failed to generate selective push configuration. Schema validation failed. Please try a full push
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234408
|
||||||
|
|
||||||
|
Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-228515
|
||||||
|
|
||||||
|
The EleasticSearch SSH flaps on the M-600 appliance in Panorama or Log Collector mode. This causes logs to not display on the Panorama management server (**Monitor** > **Logs**) and the Log Collector health status (**Panorama** > **Managed Collectors** > **Status**) to display as degraded.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.8-h13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
@@ -0,0 +1,500 @@
|
|||||||
|
---
|
||||||
|
type: Known
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.9
|
||||||
|
source: common-crawl
|
||||||
|
crawl: CC-MAIN-2026-12
|
||||||
|
---
|
||||||
|
|
||||||
|
## WF500-5854
|
||||||
|
|
||||||
|
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
||||||
|
|
||||||
|
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
||||||
|
|
||||||
|
## WF500-5843
|
||||||
|
|
||||||
|
In a WildFire appliance cluster, issuing the `show cluster-all peers` CLI command when a node within the cluster is being rebooted generates the following error: `Server error : An error occured.`
|
||||||
|
|
||||||
|
## WF500-5840
|
||||||
|
|
||||||
|
The sample analysis statistics that are returned when issuing the `show wildfire local statistics` CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
||||||
|
|
||||||
|
## WF500-5823
|
||||||
|
|
||||||
|
The following WildFire appliance CLI command does not return a signature generation status as expected: `show wildfire global signature-status`. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
||||||
|
|
||||||
|
## WF500-5781
|
||||||
|
|
||||||
|
The WildFire appliance might erroneously generate and log the following device certification error: `Device certificate is missing or invalid. It cannot be renewed.`
|
||||||
|
|
||||||
|
## WF500-5754
|
||||||
|
|
||||||
|
In WildFire appliance clusters, issuing the `show cluster controller` CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
||||||
|
|
||||||
|
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
||||||
|
|
||||||
|
## WF500-5632
|
||||||
|
|
||||||
|
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297295
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls in Microsoft Azure environments only
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a `segfault` error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
||||||
|
|
||||||
|
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
||||||
|
|
||||||
|
- D3_v2/DS3_v2 to D8ds_v5
|
||||||
|
- D4_v2/DS4_v2 to D8ds_v5
|
||||||
|
- D5_v2/DS5_v2 to D16ds_v5
|
||||||
|
|
||||||
|
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
||||||
|
|
||||||
|
## PAN-295255
|
||||||
|
|
||||||
|
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
||||||
|
|
||||||
|
## PAN-292344
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.9-h7
|
||||||
|
```
|
||||||
|
|
||||||
|
When upgrading from PAN-OS 10.2.9-h1 to PAN-OS 10.2.13-h5, the firewall reboots repeatedly and enters maintenance mode.
|
||||||
|
|
||||||
|
## PAN-291716
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.
|
||||||
|
|
||||||
|
## PAN-291288
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.
|
||||||
|
|
||||||
|
## PAN-290996
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.16-h1 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
When performing an SNMP walk, the Connections Per Second (CPS) counters incorrectly return a value of 0 for each virtual system (VSYS), despite the firewall actively processing connections.
|
||||||
|
|
||||||
|
## PAN-290088
|
||||||
|
|
||||||
|
When pushing configurations from Panorama to a firewall, a memory leak might occur in the firewall's configd process, particularly when the configurations contain shared policies. Each configuration push causes the configd process to consume additional memory that is not released after the commit completes.
|
||||||
|
|
||||||
|
## PAN-288097
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.
|
||||||
|
|
||||||
|
## PAN-287871
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue affects PAN-OS 10.2.9-h9
|
||||||
|
```
|
||||||
|
|
||||||
|
When SSL Inbound Inspection is enabled and the firewall receives fragmented Client Hello packets that include the TCP timestamp option, the Client Hello message is forwarded to the destination server without the timestamp option.
|
||||||
|
|
||||||
|
## PAN-286231
|
||||||
|
|
||||||
|
When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.
|
||||||
|
|
||||||
|
This issue is more likely to occur in the following scenarios:
|
||||||
|
|
||||||
|
- When you run **Commit and Push** operations as a single action.
|
||||||
|
- When you trigger multiple parallel commit-all jobs at the same time.
|
||||||
|
- Device groups and templates have different configuration synchronization versions.
|
||||||
|
|
||||||
|
**Workaround:** Perform one of the following steps:
|
||||||
|
|
||||||
|
- Perform commit and push as two separate, sequential steps.
|
||||||
|
- Perform a full push instead of selective push.
|
||||||
|
|
||||||
|
## PAN-285894
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13-h10 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
If the Preserve Pre-NAT feature is enabled, dataplane crashes may occur, which could result in firewall reboots.
|
||||||
|
|
||||||
|
**Workaround:** Disable the Preserve Pre-NAT feature using the `set deviceconfig setting preserve-prenat-feature no` CLI command.
|
||||||
|
|
||||||
|
## PAN-284073
|
||||||
|
|
||||||
|
The firewall web interface becomes inaccessible and commits fail.
|
||||||
|
|
||||||
|
## PAN-284067
|
||||||
|
|
||||||
|
A cumulative memory leak in the `devsrvr` process gets progressively worse whenever the CLI command `show running application statistics` is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
||||||
|
|
||||||
|
**Workaround:** Avoid using the CLI command: `show running application statistics`.
|
||||||
|
|
||||||
|
## PAN-281370
|
||||||
|
|
||||||
|
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
||||||
|
|
||||||
|
## PAN-262287
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.13 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Dereferencing a NULL pointer that occurs might cause pan_task processes to crash.
|
||||||
|
|
||||||
|
## PAN-263226
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
(PAN-OS 10.2.9-h9 only)
|
||||||
|
```
|
||||||
|
|
||||||
|
When SSL decryption is enabled and Client Hello messages span multiple TCP segments, elements from the proxy_l2info memory pool may not be freed properly. Memory leaks in this pool cause some SSL decryption sessions to fail.
|
||||||
|
|
||||||
|
**Workaround:** Disable Client Hello accumulation using the `debug dataplane set ssl-decrypt accumulate-client-hello disable yes` CLI command.
|
||||||
|
|
||||||
|
## PAN-260851
|
||||||
|
|
||||||
|
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
||||||
|
|
||||||
|
## PAN-259769
|
||||||
|
|
||||||
|
GlobalProtect portal is not accessible via a web browser and the app displays the error `ERR_EMPTY_RESPONSE`.
|
||||||
|
|
||||||
|
## PAN-251895
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When Inline Cloud Analysis features are enabled, the firewall experiences a slow packet buffer leak, resulting in poor performance and dropped traffic.
|
||||||
|
|
||||||
|
**Workaround:**Disable WildFire Inline Cloud Analysis and Advanced Threat Prevention Inline Cloud Analysis on the firewall.
|
||||||
|
|
||||||
|
## PAN-251639
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See. PAN-OS 10.2.9-h9 Addressed Issues. This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
An out of memory condition might occur due to a memory leak in the varrcvr process when a Wildfire Analysis security profile is enabled.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- `db-serialno can be at most 40 characters`
|
||||||
|
- `db-serialno is invalid`
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:`delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>`
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:`delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>`
|
||||||
|
|
||||||
|
## PAN-234015
|
||||||
|
|
||||||
|
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
||||||
|
|
||||||
|
## PAN-223365
|
||||||
|
|
||||||
|
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
||||||
|
|
||||||
|
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
||||||
|
|
||||||
|
`admin``debug elasticsearch es-restart all`
|
||||||
|
|
||||||
|
## PAN-229865
|
||||||
|
|
||||||
|
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
||||||
|
|
||||||
|
## PAN-226361
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.9-h14 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Sessions might end unexpectedly with the error `resources-unavailable` when the firewall incorrectly interprets the Content and Threat Detection (CTD) global packet queue as being full.
|
||||||
|
|
||||||
|
## PAN-223677
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
||||||
|
```
|
||||||
|
|
||||||
|
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
||||||
|
|
||||||
|
## PAN-222586
|
||||||
|
|
||||||
|
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
||||||
|
|
||||||
|
## PAN-221775
|
||||||
|
|
||||||
|
A `Malformed Request` error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the `Password` includes an ampersand (&).
|
||||||
|
|
||||||
|
## PAN-217307
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The following Security policy rule (**Policies** > **Security**) filters return no results:
|
||||||
|
|
||||||
|
`log-start eq no`
|
||||||
|
|
||||||
|
`log-end eq no`
|
||||||
|
|
||||||
|
`log-end eq yes`
|
||||||
|
|
||||||
|
## PAN-213746
|
||||||
|
|
||||||
|
On the Panorama management server, the **Hostkey** displayed as `undefined undefined` if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
||||||
|
|
||||||
|
## PAN-213119
|
||||||
|
|
||||||
|
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
||||||
|
|
||||||
|
`show -> dis-block-table is unexpected`
|
||||||
|
|
||||||
|
## PAN-212889
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying `no data to display` when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
||||||
|
|
||||||
|
## PAN-212533
|
||||||
|
|
||||||
|
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from `Superuser` to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
||||||
|
|
||||||
|
## PAN-211531
|
||||||
|
|
||||||
|
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
||||||
|
|
||||||
|
## PAN-209288
|
||||||
|
|
||||||
|
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
||||||
|
|
||||||
|
## PAN-208622
|
||||||
|
|
||||||
|
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to `Block` to a Security policy rule (**Policies** > **Security**).
|
||||||
|
|
||||||
|
## PAN-204689
|
||||||
|
|
||||||
|
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
||||||
|
|
||||||
|
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
||||||
|
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
||||||
|
|
||||||
|
## PAN-196758
|
||||||
|
|
||||||
|
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
||||||
|
|
||||||
|
## PAN-196504
|
||||||
|
|
||||||
|
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
||||||
|
|
||||||
|
## PAN-194996
|
||||||
|
|
||||||
|
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
||||||
|
|
||||||
|
**Workaround**: Retry the operation.
|
||||||
|
|
||||||
|
## PAN-194519
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
||||||
|
|
||||||
|
## PAN-194515
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
||||||
|
|
||||||
|
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
||||||
|
|
||||||
|
## PAN-194424
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
||||||
|
|
||||||
|
**Workaround:** Restart the log receiver service by running the following CLI command:
|
||||||
|
|
||||||
|
`debug software restart process log-receiver`
|
||||||
|
|
||||||
|
## PAN-194202
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
||||||
|
|
||||||
|
## PAN-190727
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
||||||
|
|
||||||
|
## PAN-189111
|
||||||
|
|
||||||
|
After deleting an MP pod and it comes up, the `show routing` command output appears empty and traffic stops working.
|
||||||
|
|
||||||
|
## PAN-189076
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
||||||
|
|
||||||
|
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
||||||
|
|
||||||
|
## PAN-188358
|
||||||
|
|
||||||
|
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
||||||
|
|
||||||
|
## PAN-187685
|
||||||
|
|
||||||
|
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
||||||
|
|
||||||
|
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
||||||
|
|
||||||
|
## PAN-187643
|
||||||
|
|
||||||
|
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
||||||
|
|
||||||
|
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
||||||
|
|
||||||
|
## PAN-187612
|
||||||
|
|
||||||
|
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
||||||
|
|
||||||
|
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
||||||
|
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
||||||
|
|
||||||
|
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
||||||
|
|
||||||
|
`admin > request plugins dlp reset`
|
||||||
|
|
||||||
|
## PAN-187407
|
||||||
|
|
||||||
|
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
||||||
|
|
||||||
|
## PAN-187370
|
||||||
|
|
||||||
|
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
||||||
|
|
||||||
|
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
||||||
|
|
||||||
|
## PAN-186283
|
||||||
|
|
||||||
|
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
||||||
|
|
||||||
|
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
||||||
|
|
||||||
|
## PAN-186282
|
||||||
|
|
||||||
|
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
||||||
|
|
||||||
|
**Workaround:** Reboot the Panorama HA pair.
|
||||||
|
|
||||||
|
## PAN-184406
|
||||||
|
|
||||||
|
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
||||||
|
|
||||||
|
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
||||||
|
|
||||||
|
## PAN-183404
|
||||||
|
|
||||||
|
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
||||||
|
|
||||||
|
## PAN-181933
|
||||||
|
|
||||||
|
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
||||||
|
|
||||||
|
## PAN-181823
|
||||||
|
|
||||||
|
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
||||||
|
|
||||||
|
## PAN-180661
|
||||||
|
|
||||||
|
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays `commit time out` as the reason the commit failed.
|
||||||
|
|
||||||
|
## PAN-180104
|
||||||
|
|
||||||
|
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
||||||
|
|
||||||
|
## PAN-178194
|
||||||
|
|
||||||
|
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
||||||
|
|
||||||
|
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
||||||
|
|
||||||
|
- Define URL exceptions for specific web sites—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-category-exception`
|
||||||
|
|
||||||
|
- Configuration settings for each inline ML model—
|
||||||
|
`admin#``set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled`
|
||||||
|
|
||||||
|
## PAN-177455
|
||||||
|
|
||||||
|
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
||||||
|
|
||||||
|
## PAN-175915
|
||||||
|
|
||||||
|
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
||||||
|
|
||||||
|
## PAN-174982
|
||||||
|
|
||||||
|
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
||||||
|
|
||||||
|
## PAN-172274
|
||||||
|
|
||||||
|
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
||||||
|
|
||||||
|
**Workaround:** Issue the following command to retrieve and update the licenses: `license request fetch`.
|
||||||
|
|
||||||
|
## PAN-171938
|
||||||
|
|
||||||
|
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
||||||
|
|
||||||
|
## PAN-164885
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
|
||||||
+83
-2
@@ -231,9 +231,90 @@
|
|||||||
"10.2.0-h1_2026-03-20.md",
|
"10.2.0-h1_2026-03-20.md",
|
||||||
"10.2.0-h2_2026-03-20.md",
|
"10.2.0-h2_2026-03-20.md",
|
||||||
"10.2.0-h3_2026-03-20.md",
|
"10.2.0-h3_2026-03-20.md",
|
||||||
"10.2.0-h4_2026-03-20.md"
|
"10.2.0-h4_2026-03-20.md",
|
||||||
|
"10.2.1_2026-03-16.md",
|
||||||
|
"10.2.1-h1_2026-03-16.md",
|
||||||
|
"10.2.1-h2_2026-03-16.md",
|
||||||
|
"10.2.1-h3_2026-03-16.md",
|
||||||
|
"10.2.2-h1_2026-03-16.md",
|
||||||
|
"10.2.2-h4_2026-03-16.md",
|
||||||
|
"10.2.2-h5_2026-03-16.md",
|
||||||
|
"10.2.2-h6_2026-03-16.md",
|
||||||
|
"10.2.3-h4_2026-03-16.md",
|
||||||
|
"10.2.3-h9_2026-03-16.md",
|
||||||
|
"10.2.3-h11_2026-03-16.md",
|
||||||
|
"10.2.3-h12_2026-03-16.md",
|
||||||
|
"10.2.3-h13_2026-03-16.md",
|
||||||
|
"10.2.3-h14_2026-03-16.md",
|
||||||
|
"10.2.4_2026-03-16.md",
|
||||||
|
"10.2.4-h3_2026-03-16.md",
|
||||||
|
"10.2.4-h4_2026-03-16.md",
|
||||||
|
"10.2.4-h10_2026-03-16.md",
|
||||||
|
"10.2.4-h32_2026-03-16.md",
|
||||||
|
"10.2.5-h1_2026-03-16.md",
|
||||||
|
"10.2.5-h6_2026-03-16.md",
|
||||||
|
"10.2.6_2026-03-16.md",
|
||||||
|
"10.2.6-h1_2026-03-16.md",
|
||||||
|
"10.2.6-h3_2026-03-16.md",
|
||||||
|
"10.2.7_2026-03-16.md",
|
||||||
|
"10.2.7-h3_2026-03-16.md",
|
||||||
|
"10.2.7-h12_2026-03-16.md",
|
||||||
|
"10.2.7-h16_2026-03-16.md",
|
||||||
|
"10.2.7-h18_2026-03-16.md",
|
||||||
|
"10.2.7-h19_2026-03-16.md",
|
||||||
|
"10.2.8_2026-03-16.md",
|
||||||
|
"10.2.8-h13_2026-03-16.md",
|
||||||
|
"10.2.8-h18_2026-03-16.md",
|
||||||
|
"10.2.9_2026-03-16.md",
|
||||||
|
"10.2.9-h9_2026-03-16.md",
|
||||||
|
"10.2.9-h11_2026-03-16.md",
|
||||||
|
"10.2.9-h14_2026-03-16.md",
|
||||||
|
"10.2.9-h16_2026-03-16.md",
|
||||||
|
"10.2.9-h18_2026-03-16.md",
|
||||||
|
"10.2.10_2026-03-16.md",
|
||||||
|
"10.2.10-h4_2026-03-16.md",
|
||||||
|
"10.2.10-h5_2026-03-16.md",
|
||||||
|
"10.2.10-h7_2026-03-16.md",
|
||||||
|
"10.2.10-h9_2026-03-16.md",
|
||||||
|
"10.2.10-h10_2026-03-16.md",
|
||||||
|
"10.2.10-h14_2026-03-16.md",
|
||||||
|
"10.2.10-h17_2026-03-16.md",
|
||||||
|
"10.2.10-h18_2026-03-16.md",
|
||||||
|
"10.2.10-h21_2026-03-16.md",
|
||||||
|
"10.2.11_2026-03-16.md",
|
||||||
|
"10.2.11-h1_2026-03-16.md",
|
||||||
|
"10.2.11-h6_2026-03-16.md",
|
||||||
|
"10.2.11-h10_2026-03-16.md",
|
||||||
|
"10.2.11-h12_2026-03-16.md",
|
||||||
|
"10.2.12_2026-03-16.md",
|
||||||
|
"10.2.13_2026-03-16.md",
|
||||||
|
"10.2.13-h1_2026-03-16.md",
|
||||||
|
"10.2.13-h2_2026-03-16.md",
|
||||||
|
"10.2.13-h3_2026-03-16.md",
|
||||||
|
"10.2.13-h5_2026-03-16.md",
|
||||||
|
"10.2.13-h7_2026-03-16.md",
|
||||||
|
"10.2.14-h1_2026-03-16.md",
|
||||||
|
"10.2.15_2026-03-16.md",
|
||||||
|
"10.2.16_2026-03-16.md",
|
||||||
|
"10.2.18_2026-03-16.md",
|
||||||
|
"10.2.18-h1_2026-03-16.md"
|
||||||
],
|
],
|
||||||
"known": []
|
"known": [
|
||||||
|
"10.2.0_2026-03-16.md",
|
||||||
|
"10.2.1_2026-03-16.md",
|
||||||
|
"10.2.4_2026-03-16.md",
|
||||||
|
"10.2.6_2026-03-16.md",
|
||||||
|
"10.2.7_2026-03-16.md",
|
||||||
|
"10.2.8_2026-03-16.md",
|
||||||
|
"10.2.9_2026-03-16.md",
|
||||||
|
"10.2.10_2026-03-16.md",
|
||||||
|
"10.2.11_2026-03-16.md",
|
||||||
|
"10.2.12_2026-03-16.md",
|
||||||
|
"10.2.13_2026-03-16.md",
|
||||||
|
"10.2.15_2026-03-16.md",
|
||||||
|
"10.2.16_2026-03-16.md",
|
||||||
|
"10.2.18_2026-03-16.md"
|
||||||
|
]
|
||||||
},
|
},
|
||||||
"10.1": {
|
"10.1": {
|
||||||
"addressed": [],
|
"addressed": [],
|
||||||
|
|||||||
Reference in New Issue
Block a user