Process new reference files
This commit is contained in:
@@ -0,0 +1,9 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: GlobalProtect
|
||||||
|
version: 6.3.3-h11
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2026-0251](https://security.paloaltonetworks.com/CVE-2026-0251) (Windows and macOS).
|
||||||
@@ -0,0 +1,21 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: GlobalProtect
|
||||||
|
version: 6.3.3-h9
|
||||||
|
---
|
||||||
|
|
||||||
|
## GPC-25889
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect clients, particularly when connected to Prisma Access, were unable to extend their VPN session. When the 'Extend Session' or 'Refresh connection' option was selected, the client would disconnect and immediately reconnect, but the session countdown timer would not reset. This was due to a race condition that caused the `GetCurrentGateway()` function to return a null value during the session extension thread, preventing the session from being properly prolonged.
|
||||||
|
|
||||||
|
## GPC-25828
|
||||||
|
|
||||||
|
Fixed an issue where on macOS devices running GlobalProtect Agent version 6.3.3-h6, the GlobalProtect Agent was unable to communicate with the GlobalProtect Service, resulting in the error "Could not connect to the GlobalProtect service." This occurred because when prelogon was disabled, the PanGPS LaunchDaemon would exit prematurely after boot, and the subsequent LaunchAgent failed to properly restart PanGPS as a user-session agent, leaving no service listening on port 4767 for PanGPA to connect to.
|
||||||
|
|
||||||
|
## GPC-25702
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect service (PanGPS) failed to start on macOS 26.3.1 after a system upgrade, preventing GlobalProtect client version 6.2.8-814 from connecting. This was due to a regression where `SetCurrentGateway` was set to `NULL` during `disconnectVPN` operations.
|
||||||
|
|
||||||
|
## GPC-24033
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect Client 6.3.3-676 on Windows endpoints would hang or freeze. This occurred when the client connected to a GlobalProtect portal or gateway that initiated a client certificate request, even if the certificate was not strictly required for authentication. The client's certificate selection dialog would appear briefly and then disappear, causing the GlobalProtect client application to become unresponsive.
|
||||||
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.7-h34
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-269254
|
||||||
|
|
||||||
|
Fixed an issue where high CPU utilization caused GlobalProtect VPN tunnels to flap, users to be disconnected, and the CLI to become unresponsive. This occurred when a large number of GlobalProtect users were actively processing application traffic.
|
||||||
|
|
||||||
|
## PAN-223481
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5450 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the all_pktproc process stopped responding when the firewall was on PAN-OS 10.1.9-h3 or a later release.
|
||||||
Reference in New Issue
Block a user