dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0263

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 11.1.4 / 11.1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 buffer overflow vulnerability in the IKEv2 processing of Palo Alto Networks PAN-OS® software allows an unauthenticated network-based attacker to execute arbitrary code with elevated privileges on the firewall, or cause a denial of service (DoS) condition. Panorama, 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

A buffer overflow vulnerability exists in the IKEv2 processing component of Palo Alto Networks PAN-OS software. This allows an unauthenticated network-based attacker to overflow a buffer during IKEv2 handshake processing, enabling arbitrary code execution with elevated privileges on the firewall or causing a denial of service.

MitigationApply vendor-supplied PAN-OS patches for CVE-2026-0263 immediately; as an interim measure, consider disabling IKEv2 if not required, and restrict IKEv2 traffic at external interfaces using ACLs to limit attack surface until patching is complete.

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:>= 11.1.0, < 11.1.4>= 11.1.5, < 11.1.6>= 11.1.8, < 11.1.10>= 11.1.11, < 11.1.13= 11.1.4= 11.1.6= 11.1.7= 11.1.10= 11.1.13= 11.1.14>= 11.2.0, < 11.2.4>= 11.2.5, < 11.2.7

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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
    Access the firewall management interface or use 'show system info' command in the CLI to retrieve the installed PAN-OS version number
    Affected if The installed version falls within any of these ranges: 11.1.0-11.1.3, 11.1.5, 11.1.8-11.1.9, 11.1.11-11.1.12, 11.1.4, 11.1.6, 11.1.7, 11.1.10, 11.1.13, 11.1.14, 11.2.0-11.2.3, or 11.2.5-11.2.6
  2. Verify IKEv2 VPN gateway is configured
    Use 'show vpn gateway' or 'show vpn ike gateway' CLI command to list configured VPN gateways and check if IKEv2 protocol is enabled on any gateway
    Affected if An IKEv2 VPN gateway is active and the PAN-OS version is in the affected ranges above
  3. Confirm VPN interface is network accessible
    Review VPN configuration to identify the interface(s) handling IKEv2 traffic (typically external or untrusted interfaces) using 'show interface' and check firewall security policy rules for VPN-related zones
    Affected if The IKEv2 VPN interface has network accessibility from untrusted networks (not behind restricted ACLs or internal-only)
  4. Check for recent IKEv2-related system logs
    Review PAN-OS logs in Monitor > System > Logs or use 'show log system' CLI command filtering for IKEv2 events to identify potential exploitation attempts
    Affected if IKEv2 processing logs exist and the PAN-OS version is in the affected version ranges

A user is affected if the PAN-OS version is any of 11.1.0 through 11.1.14 (excluding unaffected point releases), or 11.2.0 through 11.2.6, AND the device has an IKEv2 VPN gateway configured and accessible from the network.

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 11.1.4 / 11.1.6 / 11.1.10 or later
Fixed in 11.1.411.1.611.1.10
Interim mitigation

Apply vendor-supplied PAN-OS patches for CVE-2026-0263 immediately; as an interim measure, consider disabling IKEv2 if not required, and restrict IKEv2 traffic at external interfaces using ACLs to limit attack surface until patching is complete.

Recommended fix High confidence

PAN-OS 11.1.13 or later

  1. 1. Identify the current PAN-OS version by navigating to Dashboard > General Information or using 'show system info' in CLI.
  2. 2. If running a version in the affected range (>= 11.1.0, < 11.1.4; >= 11.1.5, < 11.1.6; >= 11.1.8, < 11.1.10; >= 11.1.11, < 11.1.13), plan for upgrade to a fixed release.
  3. 3. Review Palo Alto Networks Upgrade Guide for pre-upgrade checks: https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-upgrade.html
  4. 4. Perform a backup of the firewall configuration via 'request system backup' or Device > Setup > Operations > Save config.
  5. 5. Download the recommended fixed PAN-OS release (11.1.13 or later) from the Palo Alto Networks Customer Support Portal.
  6. 6. Upload the software file via Device > Software > Upload, or via 'request system software upload <filename>' in CLI.
  7. 7. Install the upgrade: select the downloaded release and click 'Install' in the web UI, or use 'request system software install <filename>' in CLI.
  8. 8. After installation completes, reboot the firewall via 'request system restart' or through the web UI.
Caveat Review PAN-OS 11.1.13 Release Notes for any compatibility changes, feature behavior modifications, or deprecated functionality before upgrading

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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