T The Triage ManualTechnical Guides for IT Emergencies
P1 · Network Infrastructure

PAN-OS GlobalProtect Authentication Bypass via Forged Override Cookies — CVE-2026-0257 (Active Exploitation)

CVE-2026-0257 is an authentication bypass in PAN-OS and Prisma Access affecting deployments where GlobalProtect portal or gateway authentication override cookies are enabled and Cloud Authentication Service (CAS) is disabled. A remote unauthenticated attacker can forge authentication override cookies to authenticate as any user — including the local admin account — and in confirmed cases obtain a full VPN session with internal network access. Rapid7 MDR confirmed active exploitation from two distinct waves beginning May 17 2026, originating from Vultr (104.207.144.154) and Dromatics Systems (146.19.216.125). The definitive fix is the vendor-supplied PAN-OS patch; interim mitigations are disabling authentication override cookies and re-enabling CAS.

Indicators

Likely causes

Diagnostic steps

  1. Collect a PAN-OS tech support file from the affected appliance before making any changes. In PAN-OS GUI: Device > Support > Generate Tech Support File. Review the extracted configuration for GlobalProtect portal/gateway settings: confirm whether 'authentication override cookie' is enabled AND whether Cloud Authentication Service (CAS) is disabled. Both conditions must be true for the vulnerable configuration to be present.
    Establish whether the vulnerable configuration exists on this appliance, and preserve forensic state before remediation alters it.
  2. Review GlobalProtect authentication logs (log type: GLOBALPROTECT, subtype: gateway-auth) for all portals and gateways. Filter for entries where auth method = 'Cookie' AND result = 'success' AND source IP is not a known corporate endpoint. Pay particular attention to logins to privileged local accounts (e.g., 'admin'). Export all matching entries with timestamps for forensic documentation.
    Determine whether exploitation has already occurred and establish the earliest date of compromise.
  3. Within the filtered Cookie-based success log entries, search specifically for source IPs 104.207.144.154 (Vultr, first exploitation wave ~May 18 2026) and 146.19.216.125 (Dromatics Systems, second exploitation wave ~May 21 2026). Also search for the consistent MAC address pattern 'aa:bb:cc:dd:ee:ff' and client OS strings 'linux-64' or 'Microsoft Windows 10 Pro, 64-bit' appearing in cookie-based logins. Note auth latency values: 78ms indicates first wave; 1019ms indicates second wave.
    Attribute exploitation to the known threat actor infrastructure documented by Rapid7 MDR and identify all affected time windows.
  4. For each suspicious cookie-based authentication event identified, check whether a VPN IP address was subsequently assigned to that session (review DHCP/IP assignment logs and GlobalProtect session tables). For any session where a VPN IP was assigned, extract the assigned IP address and the full session timeframe for use in Step 5.
    Determine whether the attacker progressed from authentication bypass to full internal network access — VPN IP assignment was confirmed in a subset of exploited customer environments.
  5. For any VPN IP addresses assigned during suspicious cookie-based sessions, review internal network logs for lateral movement activity originating from those IPs during the session window. Check: authentication events against internal systems, SMB/file access logs, DNS queries, and network connections to sensitive segments (domain controllers, file servers, databases). Scope lateral movement review to the full exploitation window (May 17 2026 onward).
    Determine if post-exploitation lateral movement occurred. Rapid7 MDR did not observe lateral movement in their customer base, but this must be independently verified per environment.
  6. Cross-reference all identified cookie-based exploitation log entries for consistent MAC address values and client hostnames (e.g., 'GP-CLIENT', 'DESKTOP-GP01') appearing across multiple time windows. Group events by MAC address to link exploitation waves from different source IPs to the same threat actor. Document all account names authenticated against via forged cookies — these accounts require credential resets regardless of whether lateral movement is confirmed.
    Complete threat actor attribution, identify all compromised accounts, and confirm the scope of the exploitation window for incident documentation and mandatory reporting.

Resolution path

Prevention

Tools

References

CVE-2026-0257PAN-OSGlobalProtectPrisma Accessauthentication-bypassVPNactive-exploitationCISA-KEVPalo Alto Networksedge-devicecookie-forgeryunauthenticated-accessnetwork-accessMDR2026P1