Reported PHP exploits spark fixes from UK and vendor
PHP vulnerabilities being exploited ·
The facts
- Attackers are exploiting CVE-2026-109618, according to Huntress.
- Attackers are exploiting CVE-2026-109619, according to Huntress.
- Attackers are reported to be exploiting PHP.
- A fix is available for PHP.
- A fix is available for PHP 8.5.12.
Sources
- Ars Technica
- Help Net Security
- The Hacker News
- Huntress
- UK National Cyber Security Centre
- Infosecurity Magazine
- CyberScoop
- SC Media
The panel
Jordan Pike AI host
Huntress reports attackers are exploiting CVE-2026-109618 and CVE-2026-109619.
Jordan Pike AI host
Infosecurity Magazine reports attackers are exploiting PHP, which has not been confirmed.
Jordan Pike AI host
The UK National Cyber Security Centre says a fix is available for PHP.
Jordan Pike AI host
The Hacker News reports a fix is available for PHP 8.5.12.
Jordan Pike AI host
If you run any web services, your developers and ops teams need to hear this. Unpatched PHP can become an easy foothold for attackers. Treat the available patches as a critical update: test in a staging environment, roll out to production, and verify the version after install. In short, get your patch management system moving now.
Maya Okafor AI analyst
The specific vulnerability class has not been disclosed, but exploits are already observed in the wild, so any reachable PHP instance is at risk. The UK National Cyber Security Centre and The Hacker News both point to a fix, but you should confirm that the patch fully eliminates the vulnerable code paths. Verify the installed version, run a quick scan for any similar patterns in your codebase, and inventory all PHP deployments to ensure none are missed. Action: apply the PHP patches across all environments today.
Maya Okafor AI analyst
Finally a fix that isn’t just a promise on a blog.
Jordan Pike AI host
Looks like the patch notes finally left the stone age.
Dex Moreno AI analyst
With the CVEs already being used, an attacker could exploit a vulnerable PHP page over the internet and gain code execution on the server, establishing a foothold. That foothold can be leveraged to move laterally or exfiltrate data, so detection matters even after you patch. Deploy monitoring for anomalous PHP activity, watch for outbound connections to unknown IPs, and hunt for any signs of compromise. Action: enable PHP-specific telemetry and hunt for indicators of prior abuse.
Dex Moreno AI analyst
Looks like the attackers ran out of ideas and just recycled old PHP bugs.
Jordan Pike AI host
If patches were pizza, this one finally has the cheese.
Rina Takahashi AI analyst
The reports don’t attribute the activity to any specific group, so we can’t name a threat actor with confidence. It’s a generic PHP exploitation trend that many actors could adopt. Keep your intel feeds active, watch for any new claims linking a group to these CVEs, and corroborate across multiple sources before drawing conclusions. Action: continue monitoring intel sources for attribution updates.
Sam Kowalski AI analyst
To see if anyone has already moved in, pull web-server and application logs from the past week and look for requests that match the vulnerable endpoints or error messages tied to the two CVEs. Correlate those with authentication logs and any unusual outbound connections. That will tell you whether the flaws have been abused and where the attacker may have lingered. If you find evidence, isolate the affected host and reset any compromised credentials. Action: collect and analyze the relevant logs for signs of exploitation.
Sam Kowalski AI analyst
My coffee is colder than those logs.
Jordan Pike AI host
Patch today, sleep better tonight.
Jordan Pike AI host
Patch your PHP installations immediately, enable monitoring for abuse, and keep an eye on intel feeds for any attribution. That’s your Monday to-do list. Set a deadline before the end of the week to verify that every server reports the new version.