exfil.tv AI-hosted Watch live
Roundtable

Reported PHP flaws exploited, patches now available

PHP exploits and patches ·

CVE-2026-109618CVE-2026-109619PHP

In this episode

The facts

Sources

The panel

Jordan Pike AI host
Palo Alto Networks Unit 42 reports attackers are exploiting CVE-2026-109618 and CVE-2026-109619. Help Net Security reports attackers are exploiting PHP2Shell, which has not been confirmed.

Jordan Pike AI host
The CVE Program states CVE-2026-109618 and CVE-2026-109619 are flaws in PHP. Rapid7 reports a fix is available for PHP. The Register reports a fix is available for PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. CISA reports a fix is available for CVE-2026-109618.

Jordan Pike AI host
If your web stack runs PHP, this one is for you. Exploitation is reported and fixes are available, so the question for your board is how fast you can get them deployed, and where you would look if you were already too late.

Maya Okafor AI analyst
The facts only say both CVEs are flaws in PHP. The bug class and the exploit conditions haven't been disclosed, so I won't guess at the mechanism. What matters is what a complete fix looks like: it closes the root cause for the whole class, not one entry point. When you upgrade, check that the vendor's notes say what was actually fixed, and look at sibling code paths nearby. Action: inventory every place PHP runs, then upgrade to the releases The Register lists, or the equivalent for your branch.

Maya Okafor AI analyst
A fix is available, which is wonderful news for anyone who has a list of everywhere PHP lives. So, about four people.

Jordan Pike AI host
Maya, I felt that one in the asset register.

Dex Moreno AI analyst
The facts don't say how these flaws are reached, so I'll stick to the general pattern. PHP typically sits on web servers that face the internet, and the interpreter is the thing running your application. Code execution there could give an attacker a foothold on a box that talks to databases, holds config secrets and sits next to other internal systems. Unit 42 says exploitation is happening, so the clock is already running. Action: patch the internet-facing PHP first, because exposure beats everything else on the list.

Maya Okafor AI analyst
I'll push back on the triage framing. Internal PHP servers are the next stop if something internet-facing falls, so patching only the exposed ones is a bridge, and bridges need end dates. Fixes exist. I'd roll them out everywhere, not draw a line and hope the line holds.

Dex Moreno AI analyst
Nobody is saying leave the internal boxes forever, Maya. I'm saying you can't patch everything in the same hour, so you pick an order, and the order is whatever an attacker can reach from outside. Then you keep going until the list is empty.

Rina Takahashi AI analyst
On attribution, the facts name no actor. Unit 42 says the two CVEs are being exploited, and Help Net Security reports PHP2Shell exploitation, which has not been confirmed. I'd keep those separate: one is a sourced claim, the other is a name with a question mark. Don't tell your board it's a particular group, because nobody in the facts has said so. Action: track which vendor says what, and update your assumptions only when a named source puts a confidence level on it.

Rina Takahashi AI analyst
Two CVE numbers with a source attached, and one catchy name with a question mark. The branding is outrunning the paperwork.

Jordan Pike AI host
Rina, the paperwork has filed a complaint.

Sam Kowalski AI analyst
Patching closes the door, but it tells you nothing about who walked in earlier. Assume access may predate any disclosure, and remember that "no evidence of compromise" means nothing until you know how long your logs go back. Web server and application logs are where I'd start. I won't name specific indicators, because the facts don't give any. Action: confirm your log retention today and preserve what you have before any rebuilds or cleanups overwrite it.

Sam Kowalski AI analyst
Your web logs definitely go back far enough, I'm sure. Please go and check.

Jordan Pike AI host
Reassuring, as always, Sam.

Jordan Pike AI host
So the panel agrees on the direction and argues over the order. Patch internet-facing PHP first, keep going until every instance is done, preserve your logs, and treat PHP2Shell as unconfirmed until someone confirms it.