← IBM QRadar detections
IBM QRadar · CVE exploitation
PHP2Shell (CVE-2026-109618 / CVE-2026-109619): PHP worker crashes (possible heap exploitation)
- severity
- medium
- confidence
- 50/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2026-109618 · CVE-2026-109619
php-fpm workers dying on SIGSEGV / SIGBUS / SIGABRT, or a kernel "segfault" line for a PHP process. A memory-corruption exploit such as the reported PHP2Shell use-after-free usually crashes workers while it grooms the heap, so a burst of crashes on an internet-facing server this week deserves a look even when no shell followed.
False-positive notes
Reads the raw syslog payload, so it needs php-fpm's error log or the kernel log forwarded (Linux OS log source). One crash means little; the AQL groups by server and keeps only hosts with 5 or more crashes in the window.
References
- skopnix.com/cve/CVE-2026-109618 ↗
- skopnix.com/cve/CVE-2026-109619 ↗
- www.php.net/archive/2026.php#2026-10-20-1 ↗
- cert.europa.eu/publications/security-advisories/2026-018/ ↗
- watchtowr.com/intelligence/php-cve-2026-109618-faq/ ↗
- nvd.nist.gov/vuln/detail/CVE-2026-109618 ↗
- nvd.nist.gov/vuln/detail/CVE-2026-109619 ↗
SELECT sourceip, LOGSOURCENAME(logsourceid) AS log_source, COUNT(*) AS 'Hits', MIN(starttime) AS first_ms, MAX(starttime) AS last_msFROM eventsWHERE ((UTF8(payload) ILIKE '%php-fpm%' OR UTF8(payload) ILIKE '%php-cgi%' OR UTF8(payload) ILIKE '%lsphp%') AND (UTF8(payload) ILIKE '%exited on signal 11%' OR UTF8(payload) ILIKE '%exited on signal 7%' OR UTF8(payload) ILIKE '%exited on signal 6%' OR UTF8(payload) ILIKE '%SIGSEGV%' OR UTF8(payload) ILIKE '%SIGBUS%' OR UTF8(payload) ILIKE '% segfault at %'))AND LOGSOURCETYPENAME(devicetype) IN ('Linux OS')GROUP BY sourceip, logsourceidHAVING "Hits" >= 5ORDER BY "Hits" DESCLAST 7 DAYSskopnix-qradar-cve-cve-2026-109618-fpm-crash-3041dead.aql
How to deploy on IBM QRadar
- Step 1
- Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
- Step 2
- Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
- Step 3
- For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.
- Check
- Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.