CVE-2026-0280
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 · uneditedAn IPv6 packet processing vulnerability in the dataplane of Palo Alto Networks PAN-OS® software enables an unauthenticated attacker to bypass firewall security policy enforcement, allowing network traffic that should be blocked to reach protected services. Cloud NGFW and Panorama 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 · moderate confidenceA vulnerability in IPv6 packet processing within the PAN-OS dataplane allows unauthenticated attackers to bypass firewall security policies, permitting blocked network traffic to reach protected services. This is a policy enforcement bypass in the data plane specifically affecting IPv6 traffic.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
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 versionAccess the firewall management interface and go to Device > Setup > Operations or use the command 'show system info' in the CLI to retrieve the installed PAN-OS version.Affected if The installed version matches any of the following ranges: 10.2.0-10.2.6, 10.2.7, 10.2.8-10.2.9, 10.2.10, 10.2.11-10.2.12, 10.2.13, 10.2.14-10.2.15, 10.2.16, 10.2.17, 10.2.18, 11.1.0-11.1.3, 11.1.4-11.1.7, or 11.1.8-11.1.9.
-
Verify IPv6 is enabledIn the PAN-OS web interface, go to Network > Network Profiles > Interface Settings, or use the CLI command 'show system setting ipv6' to check if IPv6 is enabled on the firewall.Affected if IPv6 is enabled on the firewall dataplane interfaces.
-
Inspect IPv6 interface configurationUse the CLI command 'show interface' or access Network > Interfaces to review all configured interfaces and identify which have IPv6 addresses or IPv6 enabled.Affected if Any dataplane interfaces have IPv6 configured or enabled.
-
Review security policy rulesUse the CLI command 'show security rules' or access Policies > Security in the management interface to examine existing security policy rules and their IPv6 application settings.Affected if Security policies are configured to handle IPv6 traffic (any rules with 'ipv6' specified or default policies that apply to IPv6).
A user is affected if their PAN-OS version falls within the affected version ranges AND IPv6 is enabled on any dataplane interfaces, allowing the policy bypass to potentially occur.
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 PAN-OS patch/upgrade to the affected versions to remediate the IPv6 dataplane vulnerability. Until patched, consider disabling IPv6 if not required or implementing supplemental filtering.
Upgrade to PAN-OS 10.2.16 or later (the next stable release after the last vulnerable version 10.2.15)
- Identify your current PAN-OS version using the CLI command 'show system info' or via the web interface under Device > Summary
- Download the appropriate fixed PAN-OS release from the Palo Alto Networks Customer Support Portal
- Upload the PAN-OS upgrade bundle via Panorama (if managed) or directly to the firewall via Device > Software > Upload
- Schedule a maintenance window as upgrades require a firewall reboot
- Install the upgrade and verify the firewall comes back online successfully
- Confirm the new version matches the fixed release (10.2.16 or later) using 'show system info'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0280 — 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-0280 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