PHP: Two critical vulnerabilities ahead of scheduled security release
PHP has announced two critical vulnerabilities rated CVSS v4.0 9.2 and a security release scheduled for 21 October at 14:00 UTC. Exploit details and affected versions are not yet confirmed by PHP.
CVE search metadata
CVE search record: CVE-2026-109618. KEV: no. Product: PHP (affected versions not yet confirmed). Brief: PHP: Two critical vulnerabilities ahead of scheduled security release. Brief link: https://feed.craftedsignal.io/briefs/2026-10-php-critical-security-release/
CVE search record: CVE-2026-109619. KEV: no. Product: PHP (affected versions not yet confirmed). Brief: PHP: Two critical vulnerabilities ahead of scheduled security release. Brief link: https://feed.craftedsignal.io/briefs/2026-10-php-critical-security-release/
Triage facts
Revision 2- Applicability
- PHP (affected versions not yet confirmed)
- Evidence
- Unknown
- Severity
- Critical
- Action
- Immediate escalation
- Sources
- 4 public sources
- Freshness
- Revision 2Oct 21, 08:26 UTC
- Vulnerabilities
- 2 CVEs
- Source quality
- A2
Revision history 1 entry · Revision 2
- Revision 2
Added a source-backed PHP worker child-process hunt lead with scope and telemetry limits.
Changed: references, action_plan, body
Sources: 1
The PHP security team announced an upcoming release addressing two critical vulnerabilities, each rated CVSS v4.0 9.2. It scheduled the release for 21 October 2026 at 14:00 UTC and said it will disclose technical details, affected versions, and fixed versions with that release. CERT-EU identifies the issues as CVE-2026-109618 and CVE-2026-109619. CERT-EU describes potential remote code execution based on other reporting; PHP has not yet confirmed that attack path. No active exploitation is established in the cited notices.
Detection opportunity
Hunt for PHP or web-server workers spawning shells, scripting runtimes, discovery commands, or network utilities. The community Sigma rule for suspicious PHP child processes offers a starting point across Linux, macOS, and Windows. It requires process creation telemetry with both parent and child executable paths; use command lines and nearby HTTP requests to investigate matches. Tune known application jobs that intentionally start command-line tools.
This is generic post-execution behavior. A match does not establish exploitation of CVE-2026-109618 or CVE-2026-109619, and execution that stays inside the PHP worker will not match this rule.
Recommendation
- Identify deployed PHP runtimes and the public applications that depend on them so owners can patch promptly.
- Watch the PHP security release for confirmed affected and fixed versions; test and roll out the relevant updates.
- Treat claims that all PHP versions are affected or that unauthenticated remote code execution is confirmed as provisional until the vendor publishes technical details.
Immediate actions
Inventory PHP runtimes and identify internet-facing applications before the scheduled release
Threat Hunt
Review process creation events where a PHP or web-server worker starts a shell, scripting runtime, discovery command, or network utility
Data: Process creation telemetry with parent and child executable paths, Child command line and adjacent web request logs for triage
Mitigations
Review the vendor release at 14:00 UTC and deploy fixed PHP versions when announced
PHP