dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0261

HIGH · 7.2 CVSS v3.1 Published 2026-05-13
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
Multiple command injection vulnerabilities in Palo Alto Networks PAN-OS® software enable 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 impacted by these vulnerabilities.

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

Multiple command injection vulnerabilities in PAN-OS software allow an authenticated administrator to bypass system restrictions and execute arbitrary commands as root user through the PAN-OS CLI or Web UI.

MitigationApply the vendor-supplied PAN-OS software update and restrict management interface access to trusted internal IP addresses while limiting CLI access to a small group of administrators.

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.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.5, < 11.1.6
Ruggedcom Ape1808 FirmwareOperating system
Affected:all versions

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. Check PAN-OS version
    Run 'show system info' in the PAN-OS CLI or navigate to Dashboard > General in the Web UI to view the installed PAN-OS version
    Affected if The version falls within any of these ranges: < 10.2.7; >= 10.2.8 and < 10.2.10; >= 10.2.11 and < 10.2.13; >= 10.2.14 and < 10.2.16; = 10.2.7; = 10.2.10; = 10.2.13; = 10.2.16; = 10.2.17; = 10.2.18; >= 11.1.0 and < 11.1.4; >= 11.1.5 and < 11.1.6
  2. Check Siemens Ruggedcom Ape1808 firmware version
    Access the Ruggedcom Ape1808 management interface or check the firmware version via CLI using 'show version' or similar firmware query command
    Affected if Any version of Siemens Ruggedcom Ape1808 Firmware is installed (all versions are affected)
  3. Verify administrator access controls
    Review management access settings in PAN-OS under Device > Management > Management Interface Settings to confirm if management interface is exposed to untrusted networks
    Affected if Management interface is accessible from untrusted networks and the PAN-OS version is in the affected list, as an authenticated administrator could exploit this vulnerability

The environment is affected if PAN-OS version is in the affected ranges listed or if any version of Siemens Ruggedcom Ape1808 Firmware is installed, combined with management interface accessibility that permits authenticated administrator access.

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

Apply the vendor-supplied PAN-OS software update and restrict management interface access to trusted internal IP addresses while limiting CLI access to a small group of administrators.

Recommended fix High confidence

PAN-OS 10.2.16 or later (latest stable 10.2.x release); for Panorama upgrade to corresponding version; for Ruggedcom Ape1808 contact Siemens for fixed firmware

  1. 1. Identify the current PAN-OS version by accessing the firewall or Panorama Web UI (Device > Setup > Operations > Unit Info) or via CLI using 'show system info'
  2. 2. Determine which upgrade path applies based on your current version from the affected version ranges: < 10.2.7, 10.2.8-10.2.9, 10.2.11-10.2.12, or 10.2.14-10.2.15
  3. 3. Download the appropriate PAN-OS upgrade image from the Palo Alto Networks Customer Support Portal
  4. 4. Review the PAN-OS Upgrade Guide for your platform (PA-Series, VM-Series, or Panorama) to ensure compatibility and proper backup procedures
  5. 5. Create a backup of the current configuration before proceeding with the upgrade
  6. 6. Schedule a maintenance window as upgrades require downtime
  7. 7. Upload the new PAN-OS version via the Web UI (Device > Software) or CLI
  8. 8. Install the software version and reboot the device
Caveat Review PAN-OS 10.2.16 release notes for any configuration or feature changes before upgrading; ensure compatibility with connected devices and plugins

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-0261 — 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-0261 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