Attackers exploiting PHP flaws, patches available
PHP flaws exploited, patches out ·
In this episode
The facts
- Attackers are exploiting CVE-2026-109618, according to CISA.
- Attackers are exploiting CVE-2026-109619, according to CISA.
- Attackers are reported to be exploiting PHP2Shell.
- A fix is available for PHP.
- A fix is available for PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.
- A fix is available for CVE-2026-109618.
- CVE-2026-109619 is a flaw in PHP.
- CVE-2026-109618 is a flaw in PHP.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-109618 and CVE-2026-109619.
Jordan Pike AI host
Help Net Security reports attackers are exploiting PHP2Shell, which has not been confirmed.
Jordan Pike AI host
Both CVE-2026-109618 and CVE-2026-109619 are flaws in PHP.
Jordan Pike AI host
CISA says a fix is available for PHP, and The Register reports patches for PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, while CISA also notes a fix for CVE-2026-109618.
Jordan Pike AI host
Your web servers running vulnerable PHP versions need attention. Let’s hear the angles.
Dex Moreno AI analyst
If an internet-facing PHP service runs an affected version, CISA says the CVE-2026-109618 and CVE-2026-109619 flaws are being exploited. That could give attackers a foothold on the host and the ability to move laterally. Exposure beats severity: exploitation is happening, so a PHP server exposed to the internet is an emergency, not a ticket for the next cycle. My action: deploy the PHP patches across all servers today.
Dex Moreno AI analyst
Looks like the attackers left a thank-you note on the backdoor.
Jordan Pike AI host
One sentence.
Maya Okafor AI analyst
The flaws are in PHP and CISA reports they are being exploited. A fix is available, but you should verify that the patches cover the exact vulnerable versions you run. I’d hold off on a blanket rollout until you confirm coverage; otherwise you risk breaking applications. My action: validate patch coverage on every PHP instance and scan for any PHP2Shell artifacts.
Dex Moreno AI analyst
Maya, CISA says exploitation is happening now, so waiting to confirm coverage is a bet that attackers are slow. Patch the exposed servers first, test in parallel, and hunt for a foothold afterward. Patching isn't the end of the job, but it is the part that cuts the path off.
Maya Okafor AI analyst
Patching first is fine; my objection is to patching blind. A rushed rollout that skips testing leaves you unsure the fix landed on the versions The Register reports. Do the exposed servers today, and if you use a temporary workaround anywhere, give it an end date, because a bridge is not a fix.
Sam Kowalski AI analyst
On the evidence side, look for anomalous PHP request patterns in your web server logs and any newly created files in web directories. Search for PHP2Shell files that may have been dropped. Contain any host that shows signs of compromise and preserve logs for deeper analysis. "No evidence of compromise" means nothing until you know how long your logs were kept, so check retention first. My action: start a log review for suspicious PHP activity and isolate any compromised hosts immediately.
Rina Takahashi AI analyst
The reports come from CISA and Help Net Security, but there’s no attribution to any threat group yet. Without a claim, we can only treat this as opportunistic exploitation of widely used software. Keep the PHP2Shell piece labelled as reported, not confirmed, and ask who says so every time it gets repeated. Keep an eye on intel feeds for any emerging attribution or new tooling that leverages these CVEs. My action: monitor threat-intel sources for any claims of groups using the PHP2Shell or these PHP flaws.
Jordan Pike AI host
So, the Monday list: patch the exposed PHP servers first, test alongside rather than instead, and review your logs for signs someone got there before you did. The panel disagrees on ordering, not on urgency.