Palo Alto Networks Cloud NGFW
PAN-OS: Authenticated Admin Command Injection Vulnerability via CLI or Web UI
Edge device · Firewall / VPNknown edge product: Palo Alto Networks Cloud NGFW PAN-OS: Authenticated Admin Command (high confidence)
A command injection vulnerability in Palo Alto Networks PAN-OS® software enables an authenticated administrator to bypass system restrictions and run arbitrary commands as a root user. To be able to exploit this issue, the user must have access to the PAN-OS CLI or Web UI. The security risk posed by this issue is significantly minimized when CLI access is restricted to a limited group of administrators and by restricting access to the management web interface to only trusted internal IP addresses according to our recommended best practice 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 is applicable to PAN-OS software on PA-Series and VM-Series firewalls and on Panorama (virtual and M-Series). Cloud NGFW and Prisma® Access are not affected by this vulnerability.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Fixed in All
- >= 12.1.0, < 12.1.4-h7
- >= 11.2.0, < 11.2.4-h18
- >= 11.1.0, < 11.1.4-h34
- >= 10.2.0, < 10.2.7-h35
Fixed in 12.1.4-h7, 12.1.7, 11.2.4-h18, 11.2.7-h16, 11.2.10-h9, 11.2.12, 11.1.4-h34, 11.1.6-h33, 11.1.7-h7, 11.1.10-h27, 11.1.13-h7, 11.1.15, 10.2.7-h35, 10.2.10-h37, 10.2.13-h22, 10.2.16-h8, 10.2.18-h7
Fixed in All
Mitigation
VERSION MINOR VERSION RANGE SUGGESTED SOLUTION Cloud NGFW No action needed. PAN-OS 12.1 12.1.5 through 12.1.6 Upgrade to 12.1.7 or later. 12.1.2 through 12.1.4-h* Upgrade to 12.1.4-h7 or 12.1.7 or later. PAN-OS 11.2 11.2.11 or later Upgrade to 11.2.12 or later. 11.2.8 through 11.2.10-h* Upgrade to 11.2.10-h9 or 11.2.12 or later. 11.2.5 through 11.2.7-h* Upgrade to 11.2.7-h16 or 11.2.12 or later. 11.2.0 through 11.2.4-h* Upgrade to 11.2.4-h18 or 11.2.12 or later. PAN-OS 11.1 11.1.14 or later Upgrade to 11.1.15 or later. 11.1.11 through 11.1.13-h* Upgrade to 11.1.13-h7 or 11.1.15 or later. 11.1.8 through 11.1.10-h* Upgrade to 11.1.10-h27 or 11.1.15 or later. 11.1.7 through 11.1.7-h* Upgrade to 11.1.7-h7 or 11.1.15 or later. 11.1.5 through 11.1.6-h* Upgrade to 11.1.6-h33 or 11.1.15 or later. 11.1.0 through 11.1.4-h* Upgrade to 11.1.4-h34 or 11.1.15 or later. PAN-OS 10.2 10.2.17 or later Upgrade to 10.2.18-h7 or later. 10.2.14 through 10.2.16-h* Upgrade to 10.2.16-h8 or 10.2.18-h7 or later. 10.2.11 through 10.2.13-h* Upgrade to 10.2.13-h22 or 10.2.18-h7 or later. 10.2.8 through 10.2.10-h* Upgrade to 10.2.10-h37 or 10.2.18-h7 or later. 10.2.0 through 10.2.7-h* Upgrade to 10.2.7-h35 or 10.2.18-h7 or later. All other older Upgrade to a supported fixed version. unsupported PAN-OS versions Prisma Access No action needed.
Workaround
The vast majority of firewalls already follow Palo Alto Networks' and industry best practices. However, if you have not done so already, we strongly recommend that you secure access to your management interface according to our best practice deployment guidelines (https://live.paloaltonetworks.com/t5/community-blogs/critical-recommendations-for-deployment-guides-how-to-secure-the/ba-p/464431). Specifically, you should restrict management interface access to only trusted internal IP addresses. Review information about how to secure management access to your Palo Alto Networks firewalls: Palo Alto Networks LIVEcommunity article (https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431) https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431Palo Alto Networks official and detailed technical documentation (https://docs.paloaltonetworks.com/best-practices/10-1/administrative-access-best-practices/administrative-access-best-practices/deploy-administrative-access-best-practices)
References
- Vendor advisory security.paloaltonetworks.com/CVE-2026-0273
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| HORKimhab/CVE-2026-0273 | 12 Jun 2026 +1.5 d | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.