Palo Alto Networks Confirms Exploitation of PHP Vulnerabilities in Firewalls
Palo Alto Networks confirmed on October 28 that attackers are exploiting two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, targeting PAN-OS management interfaces that are exposed to the internet. These vulnerabilities allow unauthorized code execution on the web server.
The disclosure of these vulnerabilities was not without issues, as details leaked on October 20 prior to the coordinated release. The PHP project responded by issuing an emergency patch the following day.
Although the vulnerabilities do not require authentication, exploiting them reliably is challenging and requires specific knowledge about the target system. This is particularly concerning for appliances that often run identical and outdated software, which attackers can analyze beforehand.
As stated in the SANS course, “Everything is a web application,” web application security is often seen as a developer issue. However, it is crucial for anyone responsible for network protection to understand how web applications function to defend them effectively.
Why Appliances Are the Softer Target
Ordinary web servers utilize address space layout randomization (ASLR), which complicates exploitation by randomizing the memory addresses of code and data. However, appliances running the same software version share identical binaries, allowing attackers to determine memory offsets in advance.
The PAN-OS exploit required bypassing ASLR, which was achieved by leaking the libphp.so base address through the Set-Cookie header. Additionally, PAN-OS uses outdated PHP versions (8.0.30 and 7.4.33). A security firm, Dream, collaborating with Palo Alto Networks, discovered that the attacker had obtained and decrypted PAN-OS firmware, allowing them to create precise memory profiles for multiple software versions.
This information enabled the attacker to combine the PHP2Shell exploit with a Linux kernel flaw (CVE-2026-46300) to gain root access on 25 systems, including 24 firewalls and one management server across the U.S., Japan, Taiwan, and South Korea.
HTTP Is More Complex Than Your Defenses Assume
HTTP is a complex protocol with numerous options, allowing clients to upload files in chunks without specifying total lengths. This complexity can lead to memory-safety bugs in both web applications and the servers running them. In PHP2Shell, a crafted multipart upload can push PHP beyond its memory limits while still parsing the request.
The vulnerabilities in PHP2Shell arise from uninitialized request memory and pointers to freed memory. Even small requests can exhaust memory limits due to deeply nested file fields, complicating detection for defenders.
Understanding the protocol is essential for recognizing vulnerabilities and writing effective detection signatures. Traditional defenses may not be sufficient, especially since web application firewalls often do not provide adequate protection. Identifying critical web applications, particularly admin interfaces on firewalls, is vital for restricting access and enhancing security.
Risk Was the Hardest Call
The PHP2Shell incident highlights the challenges in accurately assessing the risk posed by vulnerabilities. Different scoring systems provide varying urgency levels, complicating prioritization for defenders.
The PHP project rated both vulnerabilities at 9.2 under CVSS 4.0, while Fortinet’s PSIRT rated them at 9.8 under CVSS v3. Palo Alto Networks initially rated the issue at 8.7 but later increased it to 9.2, recognizing the critical nature of the vulnerabilities.
Many public proofs of concept did not function, leading to confusion regarding the actual risk level for specific servers. PHP core developer Gina Peter Banyard cautioned that early workarounds were insufficient on their own.
Defending What Runs on HTTP
Dr. Johannes Ullrich, Dean of Research at SANS Technology Institute, will teach the SEC522 course on Application Security: Securing Web Applications, APIs, and Microservices at the SANS Cyber Defense Initiative 2026, scheduled for December 14-18 in Washington, D.C. The course covers HTTP protocols, file upload handling, API security, and includes hands-on labs.
Source: The Hacker News