- SMB/SME
- Enterprise
· ASC Editorial Team
Is Your Firewall's Management Interface on the Internet? What PHP2Shell Shows
On 21 October 2026, two critical flaws in PHP, CVE-2026-109618 and CVE-2026-109619, became public. Known as PHP2Shell, they allow an unauthenticated attacker to run code remotely. Palo Alto Networks has since confirmed active exploitation against PAN-OS management interfaces exposed to the internet.
PAN-OS bundles its own PHP, so firewalls and Panorama running affected versions need Palo Alto's hotfixes. The advisory says no special configuration is needed to be affected, and rates the flaw 9.2 out of 10. The risk is highest where the management interface can be reached from the internet. The score falls to 5.2 where access is restricted to a jump box. Unit 42, Palo Alto's threat research team, says about 0.02% of the company's installed base had internet-facing management interfaces and was affected, and that those customers were contacted individually. Researchers also reported attackers chaining PHP2Shell with a Linux kernel flaw to gain root access.
The effects went beyond firewalls. In the House of Lords on 22 October, a government minister said 32 government services were unavailable and four partly unavailable, because of precautionary measures taken while updates were applied. The minister said the government wasn't aware of any confirmed compromise of central government systems. Even a precaution can take a service offline.
Check three things now. First, take management interfaces off the internet and restrict access to a jump box or trusted internal addresses. Palo Alto advises this, and it's good practice for any vendor's firewall, whether or not this flaw affects it.
Second, patch to the fixed version for your branch, using the versions listed in the advisory. If you run unsupported PAN-OS, you'll need to move to a supported fixed version.
Third, look for signs of compromise. A patch closes the hole, but it doesn't tell you whether someone has already been through it. The Register reported AWS as saying attackers were exploiting the flaws four days before they were disclosed. Unit 42 suggests reviewing firewall threat logs for inbound events from public addresses matching Threat ID 543004 or the related threat names. If an exposed device shows signs of compromise, treat it as an incident.
If you run other vendors' products, check their current advisories rather than assuming. Fortinet lists FortiOS, FortiManager and FortiWeb as unaffected, but it and other vendors have been updating their product lists as investigations continue.
There's a wider lesson for anyone buying security appliances. Few owners would have listed PHP as something they run on their firewalls, yet it's part of what they have to patch. Ask your vendors how they track and tell you about third-party components, and how quickly they issue fixes when one of them fails.
Can you say today, without logging in to check, which of your management interfaces can be reached from the internet?
Source: Palo Alto Networks: CVE-2026-109618 security advisory
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.