Cloud NGFW: Incorrect Authorization
CVE-2026-0272 is a high-severity incorrect authorization vulnerability in Cloud NGFW from Palo Alto Networks, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update PAN-OS to 12.1.4-h7 or 11.2.4-h18 or 11.1.4-h34 or 10.2.7-h35, whichever matches your release line, or a later version.
- Read the advisory on security.paloaltonetworks.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Palo Alto Networks | Cloud NGFW | Not specified in the record | Not stated |
| Palo Alto Networks | PAN-OS | 12.1.0 up to, but not including, 12.1.4-h7; 11.2.0 up to, but not including, 11.2.4-h18; 11.1.0 up to, but not including, 11.1.4-h34; 10.2.0 up to, but not including, 10.2.7-h35 | 12.1.4-h7, 11.2.4-h18, 11.1.4-h34, 10.2.7-h35 |
| Palo Alto Networks | Prisma Access | Not specified in the record | Not stated |
| Siemens | RUGGEDCOM APE1808 | all versions | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.0 | Medium | CNA (paloaltonetworks.com) |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
A privilege escalation vulnerability in Palo Alto Networks PAN-OS® software allows an authenticated administrator with access to the Command Line Interface (CLI) to perform actions on the device with root privileges. 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 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 impacted by this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Cloud NGFW
- 7.2 High severity
Palo Alto Networks PAN-OS Code Injection Exploited
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
- 7.2 High severity
- 9.9 Critical severity
Recent Incorrect Authorization vulnerabilities
- 8.1 High severity
- 8.1 High severity
- 10.0 Critical severity
- 8.4 High severity
- 7.1 High severity
- 7.8 High severity
Spotted an error? Tell us.