dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0262

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
Multiple denial of service vulnerabilities in Palo Alto Networks PAN-OS® software allow an unauthenticated attacker with network access to cause a denial of service (DoS) condition by sending specially crafted network traffic. Panorama and Cloud NGFW 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 · moderate confidence

Multiple denial of service vulnerabilities in Palo Alto Networks PAN-OS software allow an unauthenticated attacker with network access to cause a DoS condition by sending specially crafted network traffic. The vulnerabilities are network-based and require no authentication, making them remotely exploitable. Panorama and Cloud NGFW are explicitly not affected.

MitigationApply the vendor-supplied PAN-OS update/patch to address the DoS vulnerabilities; until then, consider network segmentation and filtering to limit exposure to untrusted network paths.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installed
    Log into the PAN-OS management interface or use the CLI command 'show system info' to retrieve the installed PAN-OS version
    Affected if The installed version falls within the affected ranges: < 10.2.7, 10.2.8-10.2.9, 10.2.11-10.2.12, 10.2.14-10.2.15, 10.2.16, 10.2.17, 10.2.18, 11.1.0-11.1.3, or 11.1.5 (versions 11.1.4 and 11.1.6+ are not affected)
  2. Verify network exposure of the PAN-OS device
    Review firewall rules and network configuration to determine if the PAN-OS management interface or control plane is reachable from untrusted networks
    Affected if The device management interface or control plane is directly exposed to the internet or untrusted networks without proper access controls
  3. Check for Siemens Ruggedcom Ape1808 firmware version
    Access the Ruggedcom Ape1808 device through its management interface or use the command 'show version' via console/SSH to identify the firmware version
    Affected if Any version of Siemens Ruggedcom Ape1808 Firmware is installed, as all versions are affected
  4. Determine if device is responding to malformed packets
    Monitor device logs and responsiveness after receiving unusual network packets on interfaces; check system logs for crash or restart events
    Affected if The device becomes unresponsive, crashes, or exhibits unexpected behavior when receiving specially crafted network packets from an unauthenticated source
  5. Review system logs for DoS indicators
    Examine PAN-OS system logs, crash dumps, and management plane status for entries indicating denial of service events or unexpected restarts
    Affected if Logs show unexplained device crashes, core dumps, or service interruptions coinciding with network packet receipt from untrusted sources

A user is affected if they are running any PAN-OS version within the listed vulnerable ranges or any version of Siemens Ruggedcom Ape1808 Firmware, and the device is network-accessible to unauthenticated attackers.

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 update/patch to address the DoS vulnerabilities; until then, consider network segmentation and filtering to limit exposure to untrusted network paths.

Recommended fix Moderate confidence

PAN-OS 10.2.16 or later (for 10.2.x line); contact Siemens for Ruggedcom Ape1808

  1. 1. Identify the current PAN-OS version installed on the firewall or Panorama appliance by navigating to Device > Support
  2. 2. For PAN-OS versions below 10.2.7: Upgrade directly to PAN-OS 10.2.16 or later
  3. 3. For PAN-OS 10.2.8 - 10.2.9: Upgrade to PAN-OS 10.2.16 or later
  4. 4. For PAN-OS 10.2.10 - 10.2.12: Upgrade to PAN-OS 10.2.16 or later
  5. 5. For PAN-OS 10.2.14 - 10.2.15: Upgrade to PAN-OS 10.2.16 or later
  6. 6. For Ruggedcom Ape1808: Contact Siemens for patch/mitigation; no fixed firmware version is publicly documented
  7. 7. After upgrade, verify the fix by confirming the PAN-OS version and testing network functionality
  8. 8. Implement network segmentation or access controls to limit exposure to unauthenticated attackers until upgrade is complete
Caveat Review PAN-OS 10.2.16 release notes for any configuration or feature changes before upgrading; test in non-production environment first

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

Fix this in Pan Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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