dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0273

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 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.

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 · moderate confidence

Command injection vulnerability in Palo Alto Networks PAN-OS software enables authenticated administrators to bypass system restrictions and execute arbitrary commands as root user through the PAN-OS CLI or Web UI interface.

MitigationRestrict CLI access to a limited group of administrators and limit management web interface access to trusted internal IP addresses per best practice deployment guidelines; apply vendor patches when available.

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. Identify if the device runs PAN-OS
    Access the CLI and run `show system info` or log into the Web UI and navigate to Device > Setup > Operations to view system information. Look for 'PAN-OS' as the operating system.
    Affected if The device is not running PAN-OS, then it is not affected by this vulnerability.
  2. Check the installed PAN-OS version
    From CLI run `show system info` or `show version`; from Web UI go to Device > Setup > Operations. Locate the version number (for example 10.2.5, 11.1.3).
    Affected if The installed version falls within any of these ranges: 10.2.0 to <10.2.7, 10.2.8 to <10.2.10, 10.2.11 to <10.2.13, 10.2.14 to <10.2.16, 10.2.17 to 10.2.18, 11.1.0 to <11.1.4, or 11.1.8 to <11.1.10.
  3. Determine if CLI access is enabled
    From the Web UI, navigate to Device > Administrators > [admin name] and check the 'CLI' column for the admin account, or from CLI run `show admin-list` to see admin profiles.
    Affected if CLI access is granted to administrator accounts and the version is in the affected list.
  4. Determine if Web UI access is enabled
    From the Web UI, navigate to Device > Administrators > [admin name] and check the 'Web UI' column, or from CLI run `show admin-list` and verify management profiles allow HTTPS/HTTP access.
    Affected if Web UI access is enabled for any administrator and the version is in the affected list.
  5. Review management interface exposure
    Check network access settings via Device > Setup > Management > Management Interface Settings, or from CLI run `show interface management`. Verify which IP addresses can reach the management services.
    Affected if The management interface (CLI or Web UI) is exposed to untrusted networks and the version is in the affected list.

The environment is affected if the device runs a PAN-OS version within the listed ranges AND has CLI or Web UI access enabled for authenticated administrators.

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 administrators and limit management web interface access to trusted internal IP addresses per best practice deployment guidelines; apply vendor patches when available.

Recommended fix High confidence

PAN-OS 10.2.16 or later (or the next version in the current minor branch that exceeds the last vulnerable version)

  1. 1. Identify the current PAN-OS version on affected devices (PA-Series, VM-Series firewalls, or Panorama virtual/M-Series).
  2. 2. Determine the appropriate target version based on current installation: if running 10.2.0-10.2.6, upgrade to 10.2.7 or later; if running 10.2.8-10.2.9, upgrade to 10.2.10 or later; if running 10.2.11-10.2.12, upgrade to 10.2.13 or later; if running 10.2.14-10.2.15, upgrade to 10.2.16 or later.
  3. 3. Download the PAN-OS upgrade image from the Palo Alto Networks support portal.
  4. 4. Before upgrading, back up the current configuration.
  5. 5. Schedule a maintenance window as upgrades may cause brief service interruption.
  6. 6. Upload and install the upgrade via PAN-OS Web UI (Device > Software) or CLI.
  7. 7. After upgrade, verify the system is functioning correctly and the new version is running.
  8. 8. As a complementary mitigation (defense-in-depth), restrict CLI access to a limited group of administrators and limit management web interface access to trusted internal IP addresses only.
Caveat Standard PAN-OS upgrade considerations apply - review release notes for any configuration changes, feature modifications, or known issues before upgrading. Test in a non-production environment first if possible.

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0273 — 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-0273 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