CVE-2026-0269
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 memory corruption vulnerability in the processing of tunnel traffic in Palo Alto Networks PAN-OS® software allows an authenticated user to initiate system reboots using a maliciously crafted packet. Repeated attempts to initiate a reboot causes the firewall to enter maintenance mode. Panorama, 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 confidenceMemory corruption vulnerability in PAN-OS tunnel traffic processing allows authenticated users to trigger system reboots via maliciously crafted packets. Repeated exploitation forces the firewall into maintenance mode.
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>= 11.1.0, < 11.1.4>= 11.1.5, < 11.1.6>= 11.1.7, < 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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.
-
Check PAN-OS versionRun 'show system info' or 'show version' in the PAN-OS CLI, or view Device > Setup > Operations > Device Information in the web UIAffected if The installed version matches any of the affected ranges: 10.2.0 to <10.2.7, 10.2.8 to <10.2.10, 10.2.11 to <10.2.13, 10.2.14 to <10.2.16, =10.2.17, 11.1.0 to <11.1.4, 11.1.5 to <11.1.6, or 11.1.7 to <11.1.10
-
Verify tunnel interfaces are configuredRun 'show interface tunnel' or 'show tunnel info' in the CLI, or view Network > Tunnels in the web UI to list active tunnel interfacesAffected if Any tunnel interfaces (such as IPsec, SSL-VPN, or GRE tunnels) are configured and active on the firewall
-
Confirm administrative access existsRun 'show admin users' in the CLI to view currently logged-in administrators, or review Device > Administrators to list all admin accountsAffected if Multiple administrative accounts exist or administrative access is not restricted to a limited set of trusted users, since authentication is required for exploitation
-
Check for unexpected system rebootsReview system logs via 'show system logs' or the web UI under Monitor > Logs > System for entries indicating unexpected reboots or entries containing 'maintenance mode'Affected if System logs show frequent unexpected reboots or entries indicating the device entered maintenance mode
A user is affected if their PAN-OS version falls within the vulnerable ranges AND tunnel interfaces are configured AND they have administrative accounts that could be compromised.
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 when available; until then, limit authenticated access to trusted personnel only.
PAN-OS 10.2.16 or later (latest stable 10.2.x release)
- 1. Verify current PAN-OS version by navigating to Device > Support or using 'show system info' command
- 2. Review the current configuration and ensure a backup is available
- 3. Schedule a maintenance window as the upgrade will require a firewall reboot
- 4. Download the appropriate PAN-OS upgrade from the Palo Alto Networks Customer Support Portal
- 5. Upload the PAN-OS upgrade file via Dashboard > Software or via CLI: request system software upload <filename>
- 6. Install the upgrade: request system software install <filename>
- 7. After installation completes, reboot the firewall: request system restart
- 8. Verify the upgrade was successful and the firewall is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0269 — 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-0269 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