Palo Alto Networks Release Notes

The following table lists the addressed issues in Prisma Agent 26.4.2 macOS and Windows.

Addressed issues

ISSUE ID DESCRIPTION PANG-15145 Fixed an issue on macOS endpoints where the Prisma Agent cycled through all available gateways without connecting after a portal switch. The agent now correctly establishes a tunnel after switching portals. PANG-15111 Fixed an issue on Windows endpoints where the Prisma Agent became stuck in the Connecting state after waking from modern standby. The agent now correctly resumes connectivity after wake. PANG-15030 Fixed an issue on Windows endpoints where HIP submission failed after upgrading if a previous OPSWAT update had installed a newer version of the HIP compliance libraries than the version bundled with the upgrade. HIP compliance checks now succeed after upgrade. PANG-14967 Fixed an issue on Windows endpoints where network connectivity was lost after the Prisma Agent established an IPsec tunnel. Split-DNS queries failed because the agent used the tunnel's virtual IP address as the source before it was fully configured on the network adapter. The agent now waits for the virtual adapter address to be ready before signaling tunnel connectivity. PANG-14924 Fixed an issue on macOS endpoints where users were unable to establish a tunnel after clicking Login when SAML authentication was required. The Prisma Agent now correctly establishes the tunnel after SAML authentication. Original source

The following table lists the addressed issues in Prisma Agent 26.4.1 for macOS and Windows.

ISSUE ID DESCRIPTION PANG-14811 Fixed an issue on macOS endpoints where Cisco AnyConnect VPN's secondary UDP/DTLS 1.2 tunnel was terminated shortly after being established when Prisma Agent was installed and disabled or you were signed out. The primary TLS-based TCP tunnel was not affected. PANG-14481 Fixed an issue on macOS endpoints where the HIP report did not include CrowdStrike Falcon's definition version. HIP policies that required a valid CrowdStrike Falcon definition version failed, which could deny or restrict network access even when CrowdStrike was installed and up to date. Original source

ISSUE ID
DESCRIPTION

PANG-11395

Fixed an issue where the Prisma Agent on Windows 11 laptops did not reauthenticate with the internal gateway when transitioning between network interfaces (for example, from Wi-Fi to LAN) and temporarily having more than one active network interface. This prevented the IP-user mapping from being updated on the NGFW firewall, causing traffic from the user's IP to be unrecognized.

PANG-11328

Fixed an issue where DNS resolution failed for Microsoft 365 services (MS Teams and Outlook) running Prisma Agents on dual-stack Windows devices.

PANG-11311

Fixed an issue where the Prisma Agent displayed an erroneous "Your connectivity might be affected. Please try again or contact your administrator" error notification when a user manually disconnected from an on-demand connection.

PANG-11293

Fixed an issue where Prisma Agent version 26.1 was unable to retrieve the status of disk encryption for Host Information Profile (HIP) reports, causing HIP checks to fail and denying access to private applications.

PANG-11284

Fixed an issue where, after upgrading to Prisma Agent version 26.1.1.10 on Windows, users attempting to log in with Microsoft Entra SSO experienced login failures and HIP check compliance errors (Error 53000) because the embedded browser incorrectly prompted for a plugin installation.

PANG-11274

Fixed an issue on macOS devices where gateway connections would fail or experience significant delays after waking from sleep. This occurred because the Prisma Agent service (daemon) attempted to access client certificates in the login keychain through the user interface (UI) while the UI was still asleep. These requests would queue up and process sequentially once the UI woke, causing older requests to time out and preventing timely gateway connections.

Original source

The following are addressed issues in the OpenConfig 2.1.6 version of the plugin.

PLUG-23324

Fixed a security issue where authenticated gNMI users could execute arbitrary PAN-OS® operational commands through the gNMI XML API handler without command-level authorization.

PLUG-23275

Fixed a security issue where authenticated gNMI users could read or delete files outside of the permitted directories through the streaming telemetry file upload handlers.

PLUG-23370

Fixed an issue where PHP package dependencies were downloaded over plaintext HTTP with TLS disabled during plugin builds. TLS is now enabled and repository URLs use HTTPS.

PLUG-10983

Fixed an issue where subscribing to the components/component/subcomponents/subcomponent/state path returned internal filesystem mount paths as subcomponent names instead of the expected hardware component data, resulting in fewer valid entries than expected in the gNMI subscribe response.

PLUG-24750

Added OpenConfig leaf-path support for additional SNMP OIDs to achieve parity with SNMP-based monitoring, including system uptime (system/state/up-time), hardware component serial number (components/component/state/serial-no), hardware component part number (components/component/state/part-no), HA mode (ha-groups/ha-group/state/ha-mode), LACP system ID (lacp/interfaces/interface/members/member/state/system-id), and BGP peer session state, admin status, remote AS, remote address, and local address.

PLUG-24679

Added OpenConfig subscribe and get RPC support for the interfaces/interface/state/last-change leaf path, which reports the timestamp of the most recent interface operational state change.

Original source

PAN-OS 10.2.8-h15 Addressed Issues

ISSUE ID | DESCRIPTION

PAN-272809 | A fix was made to address CVE-2024-0012 (PAN-SA-2024-0015) and CVE-2024-9474.

PAN-268823 | Fixed an issue where Monitor > Log Display did not display all logs when you applied a filter.

PAN-262287 | Fixed an issue where dereferencing a NULL pointer that occurred caused pan_task processes to stop responding.

PAN-244894 | Fixed an issue where turning off mprelay logging caused mprelay heartbeat failure.

PAN-244227 | Fixed an issue where inconsistent FIB entries across the dataplane were not detected.

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

Original source

The following list includes only outstanding known issues specific to PAN-OS® 10.2.11. This list includes issues specific to Panorama™, GlobalProtect™, VM-Series plugins, and WildFire®, as well as known issues that apply more generally or that are not identified by an issue ID.

ISSUE ID
DESCRIPTION

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-306555
This issue is now resolved. See PAN-OS 10.2.18-h8 Addressed Issues.
A race condition may cause the dataplane to restart unexpectedly when a zip decompression offload result is returned for a session that has already closed. The session state is not validated before processing the result because the offload result does not follow the fastpath where these checks are normally performed. Workaround: Disable zip hardware offloading (may cause higher CPU usage).

PAN-304756
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
(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-295803
A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.

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
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
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
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
This issue is now resolved. See PAN-OS 10.2.18 Addressed Issues.
(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 commit and push as two separate, sequential steps, or perform a full push instead of selective push.

PAN-285894
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-273158
(PA-7000 Series firewalls only) Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-jumbo packets may cause silent packet drops or application slowness.

PAN-265336
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
This issue is now resolved. See PAN-OS 10.2.11-h3 Addressed Issues.
(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. Log in to the firewall web interface. Select Device > Plugins. Search for dlp. Uninstall.

PAN-264580
(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
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
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
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
Fixed in PAN-OS 10.2.11. Affects 10.2.11-h2 and later 10.2 releases.
(PA-5450 firewalls only) 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 serialno . Revoke satellite certificates: delete sslmgr-store satellite-info-revoke-certificate portal serialno .

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 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
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
(PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls) By enabling the 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
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
(PA-5450 firewall only) Trying to configure a custom payload format under Device > Server Profiles > HTTP yields a JavaScript error.

PAN-194515
(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
(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
(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
(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 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 mlav-category-exception; Configuration settings for each inline ML model— admin# set profiles url-filtering 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).

Original source

The following list includes only outstanding known issues specific to PAN-OS® 10.2.0. This list includes issues specific to Panorama™, GlobalProtect™, VM-Series plugins, CN-Series firewall, and WildFire®, as well as known issues that apply more generally or that are not identified by an issue ID.

ISSUE ID
DESCRIPTION

WIF-495
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-306555
This issue is now resolved. See PAN-OS 10.2.18-h8 Addressed Issues.
A race condition may cause the dataplane to restart unexpectedly when a zip decompression offload result is returned for a session that has already closed. The session state is not validated before processing the result because the offload result does not follow the fastpath where these checks are normally performed. Workaround: Disable zip hardware offloading (may cause higher CPU usage).

PAN-304756
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
(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-295803
A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.

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
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
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
(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-273158
(PA-7000 Series firewalls only) Due to an incorrect configuration on the ASIC, receiving a mix of jumbo and non-jumbo packets may cause silent packet drops or application slowness.

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. Log in to the Panorama web interface on the active HA peer. 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. Log in to the primary HA peer Panorama CLI and trigger a manual synchronization between the active and secondary HA peers. request high-availability sync-to-remote running-config 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
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: 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. Reference the Shared object in another Shared configuration. For example, reference the Shared address object (SharedAO1) in a Shared address group called SharedAG1. 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
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 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
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 >) 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
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 experiencing degraded ElasticSearch health and restart all ElasticSearch processes. admin> debug elasticsearch es-restart optional all Copy

PAN-219644
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
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
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
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 supported on the M-600 appliance. 504 Gateway timeout

PAN-215082
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
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
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 or Panorama CLI and fetch the device certificate. admin> request certificate fetch

PAN-207629
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. Log in to the Dedicated Log Collector CLI. Confirm the Dedicated Log Collector is disconnected from Panorama. admin> show panorama-status Verify the Connected status is no. 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
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
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
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 and start the PAN-OS software. admin> request restart software

PAN-204663
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
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
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: You create a parent device group DG-A and a child device group DG-B. 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. 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
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
(WF-500 appliance only) System log forwarding does not work over a TLS connection.

PAN-194519
(PA-5450 firewall only) Trying to configure a custom payload format under Device > Server Profiles > HTTP yields a Javascript error.

PAN-194515
(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
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
(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
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
(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
This issue is now resolved. See PAN-OS 10.2.1 Addressed Issues.
(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
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
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
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. Log in to the firewall CLI. Restart the firewall. admin> request restart system

PAN-189361
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
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
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
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
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. Log in to the Panorama web interface. Uninstall the ZTP Plugin. Downgrade Panorama to PAN-OS 10.1. Log in to the Panorama web interface. Install the ZTP plugin. 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
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
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. Log in to the Panorama web interface. In the same browser you are logged into the Panorama web interface, enter the following URL. https:///debug Uncheck (disable) Debug or Clear Debug. (HA configuration) Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.

PAN-189032
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
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
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
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
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
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 Auditand 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 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
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
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
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
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
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
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
(PA-5400 Series firewalls only) On the Panorama management server, the device health resources (Panorama >Managed Devices > Health) do not populate.

PAN-184708
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
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: Select Monitor > PDF Reports > Report Groups and remove all SaaS Application Usage reports from all Report Groups. 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. Commit. (Panorama managed firewalls) Select Commit >Commit and Push

PAN-184702
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 and recover the Log Collector connectivity to Panorama.

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
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. Log in to the Panorama web interface. Select Panorama > Plugins and search for the ztp plugin. 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
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
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
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
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
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
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
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
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
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.

Original source

Resolved Issues

PAN-246431

This issue is resolved in this hotfix but not in PAN-OS 10.2.8.

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-242910

This issue is resolved in this hotfix but not in PAN-OS 10.2.8.

Fixed an issue where a custom based non Superuser was unable to push to firewalls.

PAN-242627

This issue is resolved in this hotfix but not in PAN-OS 10.2.8.

Fixed an issue where selective push did not work.

PAN-242561

Fixed an issue where GlobalProtect tunnels disconnected shortly after being established when SSL was used as the transfer protocol.

PAN-242027

Fixed an issue where the all-task process repeatedly restarted during memory allocation failures.

PAN-239367

Fixed an issue on the firewall where a memory leak associated with the logrcvr process occurred.

PAN-238643

This issue is resolved in this hotfix but not in PAN-OS 10.2.8.

Fixed an issue where a memory leak caused multiple processes to stop responding when VM Information Sources was configured.

PAN-237208

Fixed an issue where the reportd process stopped and the firewall rebooted.

PAN-235840

Fixed an issue where, after a configuration push from Panorama to managed firewalls, the status displayed as None and the push took longer than expected.

PAN-233789

Fixed an issue with commit and push and push operations where the user was not correctly bound to the scope, which caused all device groups to be selected for a selective push.

PAN-231148

Fixed an issue where no DHCP option list was defined when using GlobalProtect.

PAN-229090

Fixed an issue where the logrcvr process stopped responding during memory allocation failures.

PAN-228515

This issue is resolved in this hotfix but not in PAN-OS 10.2.8.

Fixed an issue where the Elasticsearch cluster health status displayed as yellow or red due to Elasticsearch SSH tunnel flaps.

PAN-223259

Fixed an issue where selective pushes failed with the error message Failed to generate selective push configuration. Unable to retrieve last in-sync configuration for the device, either a push was never done or version is too old. Please try a full push.

PAN-217293

Fixed a rare issue where URLs were not accessible when the header length was greater than 16,000 over HTTP/2.

PAN-199070

Fixed an issue where the all_task and pan_task processes stopped responding, which impacted traffic.

Original source

The following table lists the addressed issues in PAN-OS 10.2.18-h8.

ISSUE ID — DESCRIPTION

• — Fixes were made to address the following CVEs:
  • CVE-2026-0283
  • CVE-2026-0287
  • CVE-2026-0288
  • CVE-2026-0286
  • CVE-2026-0285
  • CVE-2026-0280
  • CVE-2026-0284
• PAN-317466 — Fixed an issue where SIP sessions stopped progressing after the firewall received fragmented packets, fragmented at header field.
• PAN-306555 — Fixed an issue where the firewall stopped responding, which led to service outages.
• PAN-295803 — Addressed a memory leak issue under sc3 and automatic commit recovery (ACR) code path.

Original source

PAN-OS 11.2.7-h1 Addressed Issues

PAN-294436

Fixed an issue where polling failed for ethernet interfaces due to the physical port counters read from the MAC being 0.

PAN-293842

Fixed an issue where the hybrid-SWG service proxy stopped working after upgrading to PAN-OS 11.1.6-h13 due to the firewall failing to establish the listening interface.

PAN-293673

Fixed an issue where the firewall stopped all tasks due to an OOM condition caused by a scheduled log export using FTP to an external FTP server.

PAN-292503

Fixed an issue on the firewall where the source and destination NAT IP addresses did not display in traffic and threat logs.

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-290996

Fixed an issue where SNMP walks returned a value of 0 for the CPS (Connections Per Second) per vsys on firewalls after upgrading to PAN-OS 11.1.6-h3, even when active connections were present.

PAN-290088

Fixed an issue where a memory leak occurred related to the configd process when pushing configurations from Panorama to a firewall. This occurred when the configurations contained shared policy rules.

PAN-289714

(Prisma Access only) Fixed an issue where persistent commit failures occurred due to a missing transformation script when downgrading from PAN-OS 10.2.0 to PAN-OS 10.1.0.

PAN-289268

Fixed an issue where internet access through Secure Web Gateway (SWG) proxy nodes did not work when the default internet access policy rule source user was not known-user.

PAN-288939

Fixed an issue where the logrcvr process stopped responding due to an invalid SSL context being used for socket communication, which caused commits to fail.

PAN-284878

(Firewalls in active/passive HA configurations only) Fixed an issue where commits failed due the useridd process restarting.

PAN-284003

Fixed an issue where clients did not receive a valid response when when searching a website due to a compression error.

PAN-280409

Fixed an issue where the popup window did not appear as expected for Clientless VPN users.

PAN-279901

An issue was fixed where the firewall dropped fragmented TLS ClientHello packets, which blocked access to certain websites. This occurred because the packets arrived truncated, in varying sizes and orders, and the firewall's heuristics failed to handle them correctly. To enable this fix, run:

debug dataplane set ssl-decrypt accumulate-client-hello disjoined yes

PAN-279690

Fixed an issue where the the all_pktproc process stopped responding, which caused the firewall to unexpectedly restart.

PAN-279415

Fixed an issue where service routes configured to use a data plane interface incorrectly used the management plane interface for traffic transmission. This issue affected syslog and CRL status traffic when a custom service route was not configured.

PAN-276616

Fixed an issue on the firewall where half-duplex settings on Ethernet were not visible.

PAN-271810

Fixed an issue where auto-negotiation advertised and negotiated 10/100 half and full duplex.

PAN-268787

Fixed an issue where users were unable to log in to Panorama and the following error message was displayed: Timed out while getting config lock. Please try again. This occurred when pushing configurations to a large number of devices.

PAN-255860

(PA-5200 firewalls only) Fixed an issue where the all_pktproc process stopped responding when the firewall was under a heavy traffic load.

PAN-252706

Fixed an issue where the URL filtering response page for Continue and Override did not work with IPv6 Router Advertisement (RA) or Multicast Listener Query (MLQ) for IPv6-to-IPv6 and IPv6-to-IPv4 traffic.

Original source

Cortex XSOAR combines security orchestration, incident management, and interactive investigation into a seamless experience. The orchestration engine is designed to automate security product tasks and weave in human analyst tasks and workflows.

To install this version, see the following:

• Single Server Installation
• Multi-Tenant Installation

If upgrading from an earlier version, including how to install and download, see Upgrade Your Installation.

This Cortex XSOAR version introduces several new features and fixes existing issues. The release notes describe these changes, as well as any known issues.

• New Features
• Addressed Issues
• Known Issues

Original source

Prisma Agent version 26.4 has the following known issues:

Prisma Agent 26.4 (Linux) Known Issues

ISSUE ID DESCRIPTION PANG-15306 DNS-over-TCP to any upstream server is not exempt from fail-safe enforcement when the tunnel is down. This can occur regardless of whether IPv4 or IPv6 DNS servers are configured, whenever the system resolver uses TCP, such as when a UDP DNS response is truncated or TCP is otherwise required. Workaround: Configure the system resolver to prefer IPv4 DNS servers. PANG-15265 On Linux endpoints, container-to-container traffic on Podman networks and Docker bridge networks with names that do not start with br-, docker, or virbr is tunneled through Prisma Agent instead of bypassed as local LAN traffic. This includes Podman's default bridge network and any custom-named bridge network. PANG-15263 On Linux endpoints, containers that were running while the tunnel was connected may experience a 5-second delay on DNS lookups after the Prisma Agent service is restarted while disconnected. DNS resolution returns to normal after the agent reconnects and disconnects again normally. PANG-15262 On Linux endpoints, two issues occur when switching between network interfaces. When you disconnect from a wired network while Wi-Fi is also connected, the agent may remain in "Connected internally" status even though the internal network is no longer reachable. When you connect to a wired network from Wi-Fi, the user location is not re-detected and forwarding profile rules scoped to that location are not applied. Workaround: Run pacli traffic user-location refresh or manually reconnect to re-detect user location. PANG-15254 On Linux endpoints, after you disconnect from a Prisma Access gateway behind a Network Load Balancer (NLB), the gateway may continue to show you as connected. The logout request times out because it is sent to an internal tunnel address that is no longer reachable after the tunnel closes. PANG-15246 On Linux endpoints, if your sign-in to the endpoint management portal falls back to SAML authentication after a certificate attempt, subsequent gateway connections skip the PKCS#11 PIN prompt and send no client certificate. Gateways that require a client certificate reject the connection. This behavior persists across service restarts until you sign out and sign back in. PANG-15244 On Linux endpoints, when the authentication mode requires a client certificate with SAML fallback and no certificate is present, clicking the session expiry banner to re-authenticate displays a "Certificate validation failed" error instead of opening the SAML browser flow. Re-authentication cannot be completed from the session expiry banner. Workaround: Sign out and sign back in to re-authenticate. PANG-15238 On Fedora and RHEL Linux endpoints on private IP networks, connecting in "Best Gateway Available" mode may immediately fail and return a Disconnected state. Connecting to a specific gateway by name succeeds. Workaround: Connect to a specific gateway by name instead of using Best Available. PANG-15231 On KDE desktops, session timeout notifications may remain visible in the notification center after you sign out. Additionally, "Unable to Connect" error notifications accumulate as separate entries in the notification center rather than replacing each other, requiring you to dismiss each one individually. PANG-15166 On KDE desktops, when MFA is required to access a protected resource, clicking OK in the MFA dialog closes the dialog but does not automatically bring a browser window to the foreground. Workaround: If a browser window is already open, switch to it to complete MFA. If no browser is open, it launches automatically. PANG-15148 On Linux endpoints, the active gateway tunnel may disconnect and reconnect repeatedly during normal use, even when the network connection is working. The agent incorrectly interprets a single transient network check failure as a full loss of connectivity and tears down the tunnel unnecessarily. PANG-15130 On Linux endpoints, when a forwarding profile uses user-location rules, the first connection opened immediately after the agent detects the user location may be routed to the wrong destination. Subsequent connections to the same destination are routed correctly. PANG-15102 On Linux endpoints, upgrading from Prisma Agent 26.3 to 26.4.0.35 while the tunnel is connected may leave network routing and DNS configuration in an inconsistent state. After the upgrade, DNS resolution may stop working. The agent interface may also become unresponsive during the upgrade process. Workaround: Restart the system after upgrading to restore network connectivity and DNS resolution. PANG-15088 On Linux endpoints, if the system was connected to an internal network before entering sleep mode for more than 30 minutes, the agent does not reconnect automatically after the system wakes and moves to an external network. Workaround: Manually reconnect by clicking Connect in the Prisma Agent interface or running pacli connect. PANG-15077 On Linux endpoints, when a PKCS#11 or TPM client certificate with a PIN is used for authentication, the agent cannot reconnect automatically after a reboot or service restart. You must enter the certificate PIN each time the system restarts. PANG-15070 On Linux endpoints, if you change the system color scheme between dark and light mode while an MFA authentication dialog is open, the dialog retains its original colors and does not update to match the new theme. PANG-15069 On Linux endpoints, running sudo pacli switchto PAA to switch from GlobalProtect to Prisma Agent always returns an error and leaves both agents disabled. The endpoint has no active tunnel until you manually re-enable Prisma Agent. PANG-15041 On Linux endpoints, TPM2 PKCS#11 tokens created using tpm2_ptool without specifying a custom path are stored in the user's personal directory and are not visible to Prisma Agent. The agent service runs as root and reads the system-wide token store at /etc/tpm2_pkcs11 instead. Workaround: Create TPM2 tokens in the system-wide store as root, or set the tpm_store_path configuration value to point to your token store location: sudo tpm2_ptool init --path /etc/tpm2_pkcs11 PANG-15021 On RHEL 9.8 x86_64 endpoints, the Prisma Agent interface does not support dark mode. PANG-14994 On Linux endpoints, when you authenticate using a client certificate, the session expiry notification banner is not displayed before your session times out. The session expires without warning and you are disconnected. PANG-14966 On Linux endpoints, if you initially authenticated using SAML and later added client certificates to the system certificate store, clicking the session expiry banner to re-authenticate fails with a certificate error. The session expiry banner is disabled after the failure and cannot be used to retry authentication. Workaround: Sign out and sign back in to re-authenticate with your client certificate. PANG-14957 On Linux endpoints connecting to on-premises GlobalProtect gateways running PAN-OS 12.1.x, the tunnel may disconnect approximately every 60 seconds with a "Login failed: invalid gateway auth token" error. The agent reconnects automatically but disconnects again at the same interval. PANG-14954 On Linux endpoints, the first connection attempt after restarting the Prisma Agent service may return to a disconnected state with no error message displayed due to a stale cached token. A second connection attempt completes successfully. Workaround: Click Connect or Log In a second time to complete the connection. PANG-14581 On Linux endpoints, the first connection attempt to an IPv6 address using a literal IP address fails immediately when the tunnel is disconnected or when the address is covered by a Direct forwarding rule. Subsequent connection attempts to the same address succeed. Connections to hostnames are not affected. Applications that retry automatically, such as browsers, are not affected; command-line tools and scripts that dial IPv6 literal addresses directly without retrying will encounter the failure. PANG-14518 On Linux endpoints, rapidly switching between gateways may briefly put the agent in a Disconnected state before it reconnects to the selected gateway. The agent recovers automatically.

Prisma Agent 26.4 (iOS) Known Issues

ISSUE ID DESCRIPTION PANG-15575 On iOS endpoints, when a full tunnel is configured with an internal DNS server, the Host Information Profile (HIP) report cannot be sent to the endpoint management portal after the tunnel connects. When the tunnel is up, iOS routes DNS through the internal DNS server, which is only reachable through the tunnel. Because the HIP report upload goes directly outside the tunnel, it cannot resolve the endpoint management portal hostname and the upload does not complete. The gateway HIP check still passes. PANG-15420 On iOS endpoints, when you disconnect from an active VPN session, the Prisma Agent app does not send a logout notification to the gateway. The gateway session remains active until it times out on the server side, which may result in inaccurate active session counts. PANG-15419 On iOS endpoints, when the gateway resolves to an IPv6 address, IPSec tunnel establishment times out after approximately 5 seconds and the Prisma Agent app falls back to SSL VPN. IPSec connects successfully when the gateway resolves to an IPv4 address. PANG-15146 On iOS endpoints in Always-On mode, Prisma Agent connection failure notifications are not consistently received even when the notification setting is enabled. PANG-15129 On iOS endpoints connected to a Prisma Access gateway behind a Network Load Balancer (NLB), the IP address in the Prisma Agent app's Settings screen displays as 127.127.127.127 instead of the actual gateway IP address.

Prisma Agent 26.4 (Android) Known Issues

ISSUE ID DESCRIPTION PANG-15590 On Chrome OS endpoints, system notifications are not delivered when the Prisma Agent window is unfocused. An unfocused app window should behave the same as a backgrounded app and deliver system notifications. PANG-15552 On Android endpoints, when you enter an incorrect endpoint management portal address, the Prisma Agent app displays "Failed to enroll error: Failed to resolve " instead of "Please check your network connection and ensure the server address is correct." PANG-15514 On Android endpoints, sign-in notifications are received even when the notification setting is disabled, when LDAP authentication is configured. PANG-15405 On Android endpoints, when the Prisma Agent connects to a gateway over an IPv6 underlay, the gateway reports the client's public IP address as 0.0.0.0 and the source region as empty. PANG-15404 On Android endpoints, when the gateway is reached over an IPv6 underlay, IPSec tunnel establishment times out and the Prisma Agent app falls back to SSL VPN. SSL VPN then connects successfully. PANG-15131 On Android endpoints connected to a Prisma Access gateway behind a Network Load Balancer (NLB), the IP address in the Prisma Agent app's Settings screen displays as 127.127.127.127 instead of the actual gateway IP address. PANG-14998 On Android endpoints, after the Prisma Agent disconnects, the gateway continues to show the user session as active. The agent continues sending keepalive messages while in a disconnected state, which prevents the gateway from terminating the session. Original source