CVE-2026-0286: PAN-OS Management Plane Command Injection (CVSS 7.2)

Technical summary

CVE-2026-0286 is a command injection vulnerability (CWE-78) in the PAN-OS management plane affecting PA-Series, VM-Series firewalls, and Panorama appliances. An authenticated administrator can craft input that breaks out of intended command boundaries and execute arbitrary OS commands as root. The CVSS 3.1 score of 7.2 (HIGH) reflects the high-privilege requirement (PR:H) but acknowledges the severity of code execution and the network attack vector. Cloud NGFW and Prisma Access deployments are out of scope.

Business impact

Root-level command execution on firewalls or Panorama management servers poses a critical integrity and confidentiality risk. An attacker with administrative credentials—whether through insider threat, credential compromise, or account takeover—could alter firewall rules, exfiltrate configuration and traffic logs, disable security controls, or pivot to protected networks. For organizations using Panorama to manage multiple firewalls, a single compromised admin account could affect your entire security posture.

Affected systems

PAN-OS software running on PA-Series physical firewalls, VM-Series virtual firewalls, and Panorama (both virtual and M-Series appliances) are vulnerable. Cloud NGFW and Prisma Access are not affected. Check your inventory to identify all instances where PAN-OS is deployed in management or perimeter roles.

Exploitability

Exploitation requires a valid authenticated administrator account with CLI access. There is no unauthenticated or low-privilege attack path. The vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities catalog. The actual attack surface in your environment depends on how many administrators have CLI credentials and whether those credentials are subject to compromise through phishing, credential stuffing, or internal compromise.

Remediation

Consult the Palo Alto Networks security advisory for the specific patched PAN-OS versions applicable to your hardware model and version series. Patch deployment should be prioritized for internet-facing management interfaces and Panorama servers. While patches are prepared, implement compensating controls: restrict CLI access to a minimal set of trusted administrators, enforce multi-factor authentication on management accounts, isolate management networks with dedicated VLANs or jump hosts, and monitor administrative session logs for suspicious activity.

Patch guidance

Verify the patched PAN-OS versions directly from the Palo Alto Networks advisory. Patch priority should be highest for Panorama servers and any firewalls with external management access. Consider phased patching by testing in a non-production environment first, as PAN-OS updates may require brief outages. After patching, review and re-validate any CLI scripts or automation that interact with affected systems to ensure they remain compatible.

Detection guidance

Monitor for unusual CLI commands executed by administrator accounts, particularly those involving shell metacharacters or attempts to spawn subprocesses. Review audit logs for commands containing pipes, semicolons, backticks, or other shell injection indicators. Network-level detection should focus on anomalous outbound connections initiated from firewall or Panorama management sessions. Correlation of failed login attempts followed by successful CLI session activity may indicate credential compromise.

Why prioritize this

Although the CVSS score is 7.2, this vulnerability warrants urgent attention because it delivers root-level code execution on critical security infrastructure. Administrators control the perimeter defenses; compromise of their credentials or access channels would allow an adversary to disable or alter security controls wholesale. The patch should be scheduled immediately even though it requires authentication, because admin account compromise—while less common than user compromise—carries outsized impact. Organizations with restrictive CLI access policies may deprioritize slightly, but should not defer indefinitely.

Risk score, explained

The CVSS 3.1 score of 7.2 reflects: network-reachable attack vector (AV:N), low complexity (AC:L), high privilege requirement (PR:H), no user interaction (UI:N), confidentiality, integrity, and availability all fully compromised (C:H/I:H/A:H), and scope unchanged (S:U). The score is not low because root-level code execution on a firewall is severe; it is not critical (9.0+) because authentication is required. Real-world risk in your environment scales with the number of administrators with CLI credentials and the security of those credentials.

Frequently asked questions