CVE-2026-0287
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 · uneditedMultiple 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 to or through a dataplane interface. Repeated attempts to trigger this condition result in the firewall entering maintenance mode. Panorama is 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 confidencePalo Alto Networks PAN-OS contains multiple DoS vulnerabilities allowing unauthenticated attackers with network access to send specially crafted packets to dataplane interfaces, causing a denial of service condition. Repeated exploitation forces the firewall into maintenance mode, disrupting network protection. Panorama appliances are not affected by these vulnerabilities.
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 dataall versions>= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm product is PAN-OS and not PanoramaAccess the firewall web interface and check System > About > Device > Model, or run 'show system info' in CLI. Panorama appliances are not affected by this vulnerability.Affected if The device is a Panorama appliance - these are explicitly not affected per the CVE description
-
Identify installed PAN-OS versionIn the web interface go to Device > Setup > Operations > Device Information, or in CLI run 'show system info' and note the 'PAN-OS' or 'Software Version' field.Affected if The installed version falls within: 10.2.0 through 10.2.6, 10.2.7, 10.2.8 through 10.2.9, 10.2.10, 10.2.11 through 10.2.12, 10.2.13, 10.2.14 through 10.2.15, 10.2.16, 10.2.17, 10.2.18, 11.1.0 through 11.1.3, or 11.1.8 through 11.1.9 - OR if running Paloaltonetworks Cloud NGFW (all versions are affec
-
Check network exposure of dataplane interfacesReview firewall network configuration to determine if dataplane interfaces (such as ethernet1/1 or aggregate interfaces) are reachable from untrusted networks. Examine interface zones and security policies controlling access to these interfaces.Affected if Dataplane interfaces have exposure to untrusted or external networks - the CVE requires network access to these interfaces for exploitation
You are affected if you are running PAN-OS (not Panorama) with a version matching the affected ranges above AND your dataplane interfaces are accessible from network paths an attacker could reach.
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 relevant PAN-OS security update when available; restrict network access to dataplane interfaces to minimize attack surface until patching is feasible.
PAN-OS 10.2.16 or later (10.2 branch); Cloud NGFW - contact Palo Alto Networks for latest fixed release
- 1. Identify the current PAN-OS version installed on the firewall by navigating to Device > Summary in the web interface or running 'show system info' in the CLI.
- 2. Determine which version branch (10.2.x) is currently running and cross-reference with the affected version ranges provided (>= 10.2.0,<10.2.7; >=10.2.8,<10.2.10; >=10.2.11,<10.2.13; >=10.2.14,<10.2.16).
- 3. For PAN-OS 10.2.x: upgrade to the fixed release (10.2.16 or later for the 10.2 branch) by downloading the upgrade image from the Palo Alto Networks Customer Support Portal.
- 4. For Cloud NGFW: contact Palo Alto Networks support or documentation for the latest fixed release, as all versions are affected.
- 5. Before upgrading, review the PAN-OS Upgrade Guide and take a configuration backup (Device > Setup > Operations > Save config).
- 6. Schedule a maintenance window as the upgrade will require a firewall restart.
- 7. Upload and install the new PAN-OS version, then verify the firewall returns to a operational state after reboot.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0287 — 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-0287 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