dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0272

HIGH · 7.2 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 10.2.7 / 10.2.10 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a privilege escalation vulnerability in Palo Alto Networks PAN-OS software affecting PA-Series, VM-Series firewalls, and Panorama appliances. An authenticated administrator with Command Line Interface (CLI) access can elevate their privileges to execute commands with root-level permissions on the affected device.

MitigationRestrict CLI access to a limited group of trusted administrators and limit management interface access to only trusted internal IP addresses per Palo Alto best practices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pan OsOperating system
Affected:>= 10.2.0, < 10.2.7>= 10.2.8, < 10.2.10>= 10.2.11, < 10.2.13>= 10.2.14, < 10.2.16= 10.2.7= 10.2.10= 10.2.13= 10.2.16= 10.2.17= 10.2.18>= 11.1.0, < 11.1.4>= 11.1.8, < 11.1.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the PAN-OS version
    Log into the CLI and run 'show system info' or use the web interface under Device > Support or Dashboard > System Information to view the PAN-OS version
    Affected if The installed version falls within any of these ranges: 10.2.0-10.2.6, 10.2.8-10.2.9, 10.2.11-10.2.12, 10.2.14-10.2.15, 10.2.16-10.2.18, 11.1.0-11.1.3, or 11.1.8-11.1.9
  2. Confirm the product type
    Check the device model via 'show system info' in CLI or under Device > Setup > Management in the web interface. For Panorama, verify it is a virtual or M-Series appliance
    Affected if The device is a PA-Series firewall, VM-Series firewall, or Panorama (virtual or M-Series). Not affected are Cloud NGFW or Prisma Access
  3. Verify CLI access is enabled
    Check if the management interface allows CLI access. In the web interface, go to Device > Access Domain or use 'show admin-access' in CLI to see which interfaces permit administrative access
    Affected if CLI access is permitted on any management interface (HTTP, HTTPS, or SSH)
  4. Identify administrators with CLI privileges
    In the web interface, go to Device > Administrators or use 'show admins' in CLI to list admin accounts and their privilege levels
    Affected if Any administrator account exists with CLI access (typically 'Superuser' or 'Superuser read-only' roles)
  5. Check for external or untrusted CLI access exposure
    Review management interface bindings: go to Device > Setup > Management and verify the 'Management Interface' settings. Check if CLI services (SSH/HTTPS) are bound to untrusted zones or IP addresses accessible from outside
    Affected if CLI services (SSH or HTTPS) are accessible from untrusted zones or the internet

You are affected if you run a vulnerable PAN-OS version (10.2.x or 11.1.x within the specified ranges) on PA-Series, VM-Series, or Panorama, and you have any administrator accounts with CLI access configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.2.7 / 10.2.10 / 10.2.13 or later
Fixed in 10.2.710.2.1010.2.13
Interim mitigation

Restrict CLI access to a limited group of trusted administrators and limit management interface access to only trusted internal IP addresses per Palo Alto best practices.

Recommended fix High confidence

PAN-OS 10.2.16 (or later 10.2.x release)

  1. 1. Identify the current PAN-OS version on affected devices (PA-Series, VM-Series firewalls, or Panorama).
  2. 2. Plan for upgrade during a maintenance window as upgrading will require a reboot.
  3. 3. Download the fixed PAN-OS version (10.2.16 or later) from the Palo Alto Networks support portal.
  4. 4. For HA (High Availability) configurations, follow the recommended upgrade procedure: upgrade the secondary device first, perform a failover, then upgrade the now-secondary device.
  5. 5. Upload and install the upgrade via the web interface or CLI.
  6. 6. After upgrade, verify the system is functioning correctly and the vulnerability is remediated.
  7. 7. As a defense-in-depth measure, ensure CLI access is restricted to a limited group of trusted administrators and the management interface is only accessible from trusted internal IP addresses.
Caveat Upgrade requires a reboot and should be performed during a maintenance window; for HA pairs, proper failover procedure must be followed.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pan Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0272 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data