PHP2Shell exploits hit Palo Alto firewalls via PHP bugs

Critical Vulnerability 1 source

One of the early targets of PHP2Shell exploitation was the firewall. On October 28, Palo Alto Networks confirmed that attackers were exploiting the two PHP vulnerabilities, CVE-2026-109618 and CVE-202

By Yazoul AI · automated

What to do

Review the technical details in this article, check if your organization is affected, and apply the recommended security measures. Monitor official vendor advisories for patches and updates.

What Happened

Palo Alto Networks confirmed on October 28 that attackers were exploiting two PHP vulnerabilities to target its firewall products, according to reporting on the PHP2Shell exploitation campaign. The two flaws, CVE-2026-109618 and CVE-2026-109619, were chained together in attacks that treated the firewall - a network perimeter device - as just another web application to be broken into.

The confirmation marks one of the earliest observed targets of the PHP2Shell exploitation wave, and it is a notable one: Palo Alto’s firewalls are among the most widely deployed perimeter appliances in enterprise and cloud environments. The vendor’s acknowledgement that exploitation was live, not theoretical, moves these PHP issues from a general web-hosting problem into the network security stack itself.

Why It Matters

Firewalls sit at the trust boundary of nearly every enterprise network. They are the devices organizations rely on to filter, inspect, and block malicious traffic. When a firewall’s own management or web-facing components are compromised through a shared language runtime like PHP, the defender’s primary control becomes the attacker’s foothold.

The correlation is uncomfortable: the same PHP vulnerabilities affecting ordinary web servers were being used against security infrastructure. That blurs the line between “web app” and “appliance” risk. Teams that patched their web tiers but assumed their firewalls ran hardened, non-PHP code now have to re-examine that assumption. This incident also echoes the earlier PAN-OS management RCE, CVE-2026-0322, reinforcing that management planes are a recurring target.

Technical Details

The campaign hinges on two PHP flaws:

  • CVE-2026-109619 is the remote code execution primitive, actively exploited in the wild with public proof-of-concept activity.
  • CVE-2026-109618 involves the PHP out-of-memory handler and provides the second stage of the chain.

Attackers reached exposed PHP-backed interfaces on affected Palo Alto devices and chained the flaws to achieve code execution. In the firewall context, that means an attacker who lands code on the device could potentially reach management functions, configuration data, and the traffic paths the appliance was meant to protect. Any internet-exposed management or web interface should be treated as the likely entry vector until the vendor publishes definitive affected-version details.

Immediate Risk

Severity is critical. Exploitation is confirmed in the wild, and the target class - perimeter firewalls - is high-value and frequently internet-exposed. Organizations running Palo Alto devices with any PHP-backed web or management surface should assume exposure until proven otherwise.

Priority actions: inventory all Palo Alto appliances, identify those with internet-reachable management interfaces, apply vendor guidance as it lands, and restrict management access to trusted networks. Hunt logs for anomalous requests to PHP endpoints and unexpected process spawning on the appliance.

Security Insight

The deeper lesson is architectural: security appliances increasingly embed general-purpose web stacks, inheriting the full vulnerability surface of those runtimes. A firewall running PHP is not “hardened by design” - it is a web application wearing an appliance’s badge. Defenders should start classifying perimeter devices by the languages and frameworks they embed, not by the category on the datasheet. The next wave of appliance compromises will likely come from commodity runtime bugs, and the organizations that map those dependencies in advance will patch first.

Further Reading

Share

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.