CVE Vulnerabilities

CVE-2026-0264

Heap-based Buffer Overflow

Published: May 13, 2026 | Modified: Jul 14, 2026
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu
root.io logo minimus.io logo echo.ai logo

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.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

NameVendorStart VersionEnd Version
Pan-osPaloaltonetworks*10.2.7 (excluding)
Pan-osPaloaltonetworks10.2.8 (including)10.2.10 (excluding)
Pan-osPaloaltonetworks10.2.11 (including)10.2.13 (excluding)
Pan-osPaloaltonetworks10.2.14 (including)10.2.16 (excluding)
Pan-osPaloaltonetworks10.2.7 (including)10.2.7 (including)
Pan-osPaloaltonetworks10.2.7-h1 (including)10.2.7-h1 (including)
Pan-osPaloaltonetworks10.2.7-h10 (including)10.2.7-h10 (including)
Pan-osPaloaltonetworks10.2.7-h11 (including)10.2.7-h11 (including)
Pan-osPaloaltonetworks10.2.7-h12 (including)10.2.7-h12 (including)
Pan-osPaloaltonetworks10.2.7-h13 (including)10.2.7-h13 (including)
Pan-osPaloaltonetworks10.2.7-h14 (including)10.2.7-h14 (including)
Pan-osPaloaltonetworks10.2.7-h15 (including)10.2.7-h15 (including)
Pan-osPaloaltonetworks10.2.7-h16 (including)10.2.7-h16 (including)
Pan-osPaloaltonetworks10.2.7-h17 (including)10.2.7-h17 (including)
Pan-osPaloaltonetworks10.2.7-h18 (including)10.2.7-h18 (including)
Pan-osPaloaltonetworks10.2.7-h19 (including)10.2.7-h19 (including)
Pan-osPaloaltonetworks10.2.7-h2 (including)10.2.7-h2 (including)
Pan-osPaloaltonetworks10.2.7-h20 (including)10.2.7-h20 (including)
Pan-osPaloaltonetworks10.2.7-h21 (including)10.2.7-h21 (including)
Pan-osPaloaltonetworks10.2.7-h22 (including)10.2.7-h22 (including)
Pan-osPaloaltonetworks10.2.7-h23 (including)10.2.7-h23 (including)
Pan-osPaloaltonetworks10.2.7-h24 (including)10.2.7-h24 (including)
Pan-osPaloaltonetworks10.2.7-h3 (including)10.2.7-h3 (including)
Pan-osPaloaltonetworks10.2.7-h32 (including)10.2.7-h32 (including)
Pan-osPaloaltonetworks10.2.7-h4 (including)10.2.7-h4 (including)
Pan-osPaloaltonetworks10.2.7-h5 (including)10.2.7-h5 (including)
Pan-osPaloaltonetworks10.2.7-h6 (including)10.2.7-h6 (including)
Pan-osPaloaltonetworks10.2.7-h7 (including)10.2.7-h7 (including)
Pan-osPaloaltonetworks10.2.7-h8 (including)10.2.7-h8 (including)
Pan-osPaloaltonetworks10.2.7-h9 (including)10.2.7-h9 (including)
Pan-osPaloaltonetworks10.2.10 (including)10.2.10 (including)
Pan-osPaloaltonetworks10.2.10-h1 (including)10.2.10-h1 (including)
Pan-osPaloaltonetworks10.2.10-h10 (including)10.2.10-h10 (including)
Pan-osPaloaltonetworks10.2.10-h11 (including)10.2.10-h11 (including)
Pan-osPaloaltonetworks10.2.10-h12 (including)10.2.10-h12 (including)
Pan-osPaloaltonetworks10.2.10-h13 (including)10.2.10-h13 (including)
Pan-osPaloaltonetworks10.2.10-h14 (including)10.2.10-h14 (including)
Pan-osPaloaltonetworks10.2.10-h17 (including)10.2.10-h17 (including)
Pan-osPaloaltonetworks10.2.10-h18 (including)10.2.10-h18 (including)
Pan-osPaloaltonetworks10.2.10-h2 (including)10.2.10-h2 (including)
Pan-osPaloaltonetworks10.2.10-h21 (including)10.2.10-h21 (including)
Pan-osPaloaltonetworks10.2.10-h27 (including)10.2.10-h27 (including)
Pan-osPaloaltonetworks10.2.10-h3 (including)10.2.10-h3 (including)
Pan-osPaloaltonetworks10.2.10-h30 (including)10.2.10-h30 (including)
Pan-osPaloaltonetworks10.2.10-h31 (including)10.2.10-h31 (including)
Pan-osPaloaltonetworks10.2.10-h36 (including)10.2.10-h36 (including)
Pan-osPaloaltonetworks10.2.10-h4 (including)10.2.10-h4 (including)
Pan-osPaloaltonetworks10.2.10-h5 (including)10.2.10-h5 (including)
Pan-osPaloaltonetworks10.2.10-h6 (including)10.2.10-h6 (including)
Pan-osPaloaltonetworks10.2.10-h7 (including)10.2.10-h7 (including)
Pan-osPaloaltonetworks10.2.10-h8 (including)10.2.10-h8 (including)
Pan-osPaloaltonetworks10.2.13 (including)10.2.13 (including)
Pan-osPaloaltonetworks10.2.13-h1 (including)10.2.13-h1 (including)
Pan-osPaloaltonetworks10.2.13-h10 (including)10.2.13-h10 (including)
Pan-osPaloaltonetworks10.2.13-h15 (including)10.2.13-h15 (including)
Pan-osPaloaltonetworks10.2.13-h16 (including)10.2.13-h16 (including)
Pan-osPaloaltonetworks10.2.13-h18 (including)10.2.13-h18 (including)
Pan-osPaloaltonetworks10.2.13-h2 (including)10.2.13-h2 (including)
Pan-osPaloaltonetworks10.2.13-h3 (including)10.2.13-h3 (including)
Pan-osPaloaltonetworks10.2.13-h4 (including)10.2.13-h4 (including)
Pan-osPaloaltonetworks10.2.13-h5 (including)10.2.13-h5 (including)
Pan-osPaloaltonetworks10.2.13-h7 (including)10.2.13-h7 (including)
Pan-osPaloaltonetworks10.2.16 (including)10.2.16 (including)
Pan-osPaloaltonetworks10.2.16-h1 (including)10.2.16-h1 (including)
Pan-osPaloaltonetworks10.2.16-h4 (including)10.2.16-h4 (including)
Pan-osPaloaltonetworks10.2.16-h6 (including)10.2.16-h6 (including)
Pan-osPaloaltonetworks10.2.17 (including)10.2.17 (including)
Pan-osPaloaltonetworks10.2.18 (including)10.2.18 (including)
Pan-osPaloaltonetworks10.2.18-h1 (including)10.2.18-h1 (including)
Pan-osPaloaltonetworks10.2.18-h5 (including)10.2.18-h5 (including)

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References