dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0264

CRITICAL · 9.8 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 →
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 DNS proxy and DNS Server features of Palo Alto Networks PAN-OS® Software allows an unauthenticated attacker with network access to cause a denial of service (DoS) condition (all PAN-OS platforms except Cloud NGFW and Prisma Access) or potentially execute arbitrary code by sending specially crafted network traffic (PA-Series hardware only). 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 · moderate confidence

Buffer overflow vulnerability in PAN-OS DNS proxy and DNS Server features allows unauthenticated attackers with network access to send specially crafted DNS traffic. This can cause denial of service on all affected PAN-OS platforms and potentially enable arbitrary code execution on PA-Series hardware appliances specifically.

MitigationApply the vendor-supplied PAN-OS software update that addresses this vulnerability; for systems that cannot be immediately patched, consider restricting network access to DNS services or implementing DNS traffic filtering as a compensating control.

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
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. Identify PAN-OS version
    Run 'show system info' or check the dashboard in the PAN-OS web interface to view the installed software version
    Affected if The version falls within these ranges: < 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
  2. Confirm DNS proxy or DNS Server feature is enabled
    Navigate to Network > DNS Proxy (or DNS Server in some versions) in the PAN-OS web interface, or run 'show dns-proxy' and 'show dns-server' CLI commands
    Affected if Any DNS proxy or DNS Server object is configured and enabled on the device
  3. Verify hardware platform type
    Run 'show system info' or check the device model in the PAN-OS interface to identify if the hardware is a PA-Series model
    Affected if The device is a PA-Series hardware appliance (PA-200, PA-500, PA-2000 series, etc.) - this indicates potential for arbitrary code execution rather than just DoS
  4. Check for Siemens Ruggedcom Ape1808
    Identify if the deployment includes a Siemens Ruggedcom Ape1808 device and note its firmware version
    Affected if The device is a Siemens Ruggedcom Ape1808 with any firmware version

You are affected if you run any PAN-OS version in the affected ranges AND have DNS proxy or DNS Server feature enabled, or if you deploy Siemens Ruggedcom Ape1808 firmware at any version.

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 software update that addresses this vulnerability; for systems that cannot be immediately patched, consider restricting network access to DNS services or implementing DNS traffic filtering as a compensating control.

Recommended fix High confidence

PAN-OS 10.2.16 or later (for PA-Series hardware, Cloud NGFW, Prisma Access are not affected)

  1. 1. Identify the current PAN-OS version by navigating to Dashboard > General Information in the web interface or running 'show system info' in CLI.
  2. 2. For PAN-OS: If running any version < 10.2.7, upgrade to PAN-OS 10.2.16 or later.
  3. 3. For PAN-OS: If running 10.2.8.x through 10.2.9.x, upgrade to PAN-OS 10.2.16 or later.
  4. 4. For PAN-OS: If running 10.2.11.x through 10.2.12.x, upgrade to PAN-OS 10.2.16 or later.
  5. 5. For PAN-OS: If running 10.2.14.x through 10.2.15.x, upgrade to PAN-OS 10.2.16 or later.
  6. 6. For Ruggedcom Ape1808: Check cert-portal.siemens.com for firmware updates or contact Siemens support for patch availability.
  7. 7. After upgrade, verify the DNS proxy and DNS Server features are functioning correctly.
  8. 8. Confirm the fix by checking the PAN-OS version shows 10.2.16 or higher.
Caveat Review PAN-OS upgrade notes for compatibility with Panorama and any connected firewalls; ensure proper backups 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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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