CVE-2026-0286
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 · uneditedA command injection vulnerability in the management plane of Palo Alto Networks PAN-OS® software enables an authenticated administrator to execute arbitrary OS commands as root. The security risk posed by this issue is significantly minimized when CLI access is restricted to a limited group of administrators. 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 confidenceA command injection vulnerability exists in the PAN-OS management plane where improper input validation allows an authenticated administrator to inject and execute arbitrary OS commands with root privileges. The vulnerability resides in the management interface accessible via CLI or web interface.
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>= 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.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check PAN-OS version via CLILog into the device CLI and run the command: `show system info` or `show system details`. Look for the 'sw_version' or 'PanOS' field.Affected if The version displayed 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.
-
Check PAN-OS version via web interfaceLog into the PAN-OS web management console. Navigate to Device > Support. The software version is displayed on this page.Affected if The version displayed falls within any of the affected ranges listed above.
-
Verify management plane accessibilityConfirm that the device management interface (HTTPS for web UI or SSH for CLI) is reachable from your network. Use `show management-services` or check the interface configurations.Affected if The management interface is accessible from network segments beyond the trusted admin workstation.
-
Confirm administrator accounts existIn the web UI, go to Device > Administrators. Verify that administrator accounts are configured. In CLI, use `show admin` to list accounts.Affected if Any administrator accounts exist on the system (the vulnerability requires authenticated administrator access to exploit).
If the PAN-OS version falls within the affected ranges AND the management interface is accessible to untrusted networks, the environment is vulnerable to command injection via authenticated administrator sessions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.2.710.2.1010.2.13
Apply the vendor-supplied patch for PAN-OS. Additionally, strictly limit CLI and management plane access to a small, trusted group of administrators to reduce exposure.
PAN-OS 10.2.16 or later (or migrate to the latest 10.2.x stable release)
- 1. Identify your current PAN-OS version from the device dashboard or via 'show system info' in the CLI
- 2. Schedule a maintenance window for the upgrade, ensuring you have backups of the configuration
- 3. Download the appropriate PAN-OS upgrade file from the Palo Alto Networks Customer Support Portal
- 4. Upload the upgrade file via the web interface (Device > Software) or via CLI using 'request system software upload'
- 5. Install the upgrade using 'request system software install <filename>' in CLI
- 6. After installation, reboot the system using 'request system restart'
- 7. Verify the new version is running with 'show system info' and confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0286 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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