
Imunify360 Rule 8.83 Blocks Public Exploit PHP CVE-2026-109618 CVE-2026-109619
📋 TL;DR — Interim update, 21 October 2026. The upstream PHP fix is not out yet. We’ll update this post as updates land.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
📋 TL;DR — Interim update, 21 October 2026. The upstream PHP fix is not out yet. We’ll update this post as updates land.
The PHP security team announced two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619 (both CVSS v4.0 9.2), ahead of a release scheduled for 21 October 2026 at 14:00 UTC.
An exploit targeting PHP’s session upload progress handling of multipart requests is already circulating publicly.
Imunify360 ModSecurity ruleset 8.83 blocks that exploit shape. It is in Stable and rolling out now. Servers with Imunify360 and its WAF enabled receive it automatically.
This is an interim mitigation, not a fix. The permanent fix is the upstream PHP release. Updating PHP is still action number one.
CloudLinux is working on alt-php packages with the fix. We will post the timeline once the upstream release is out. Follow the status page incident for updates.
On 20 October, the PHP security team announced that a security release is coming for two vulnerabilities, both rated Critical at CVSS v4.0 9.2.
The release is scheduled for Wednesday, 21 October 2026 at 14:00 UTC. The team also reserved the right to release earlier if details become public or if exploitation is seen in the wild.
Technical details from the PHP team are due with the release. Imunify’s WAF rules changelog classifies the issue as remote code execution in PHP core.
Beyond that, we can only say what public analysis and our own testing show: a public proof of concept targets the session upload-progress handling of multipart requests. That is the PHP feature that tracks file-upload progress inside a session.
Our analysts believe the underlying problem is broader than that one path, so treat the exploit shape as one door, not the whole building.
Imunify360 uses ModSecurity, the open-source web application firewall (WAF) engine, with rules maintained by Imunify’s analysts.
Ruleset 8.83 is a regular WAF release that also carries rules for other vulnerabilities. For these CVEs, it adds two rules. One blocks the publicly circulating exploit shape. The other collects additional telemetry so analysts can see how the attack evolves and adjust coverage.
This is a virtual patch: it stops the known request pattern at the server edge, while the vulnerable PHP code stays as it is. A request that differs from the public exploit may not match. That is why we call it interim. It is a stopgap mitigation.
cat /etc/apache2/conf.d/modsec_vendor_configs/imunify360-full-apache/VERSION
Paths for Plesk, DirectAdmin, standalone servers, and LiteSpeed are in the Imunify360 ruleset version article. The release notes are in the Imunify WAF rules changelog. If the version is older than 8.83, update the ruleset and check again:
imunify360-agent update --force modsec-rules
If you run CloudLinux alt-php, follow the status page incident and apply the updated packages when they ship.
We will publish the next update after the upstream release, including the timeline for CloudLinux PHP packages.
Please log in to leave a comment. Published comments are visible to everyone.
Get cybersecurity tips and news delivered straight to your inbox
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。