Palo Alto Networks PAN-OS Authentication Bypass Vulnerability (CVE-2025-0108)

Palo Alto Networks PAN-OS contains an authentication bypass vulnerability in its management web interface. This vulnerability allows an unauthenticated attacker with network access to the management web interface to bypass the authentication normally required and invoke certain PHP scripts.

Published Feb 12, 2025 · Updated May 17, 2026

Why patchRisk explained in plain English

Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data. Federal agencies are required to remediate by 2025-03-11 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Missing Authentication for Critical Function (CWE-306) vulnerability in Palo Alto Networks PAN-OS. An authentication bypass in the Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to bypass the authentication otherwise required by the PAN-OS management web interface and invoke certain PHP scripts. While invoking these PHP scripts does not enable remote code execution, it can negatively impact integrity and confidentiality of PAN-OS. You can greatly reduce the risk of this issue by restricting access to the management web interface to only trusted internal IP addresses according to our recommended best practices deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 . This issue does not affect Cloud NGFW or Prisma Access software. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Network Security Team

●Firewall Administrators

●IT Security

●Running pan-os: 10.1.0 ≤ v < 10.1.14, 10.2.0 ≤ v < 10.2.7, 11.1.0 ≤ v < 11.1.2, 11.2.0 ≤ v < 11.2.4, 10.1.14, 10.2.7, 10.2.8, 10.2.9, 10.2.10, 10.2.11, 10.2.12, 10.2.13, 11.1.2, 11.1.3, 11.1.4, 11.1.5, 11.1.6, 11.2.4

Real-world incidentsWhat we've seen

Active exploitation documented in the wild. Threat-research write-up: https://security.paloaltonetworks.com/CVE-2025-0108

How to patch

Manual remediation steps

Identify affected hosts: query inventory for network-security installs in scope.

Apply the vendor security update referenced in CVE-2025-0108's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.

Verify the fix per the vendor's published verification steps.

Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.

PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2025-0108 ↗ MSRC Advisory ↗ NVD ↗ Vendor Advisory