Skip to navigation

Threat reportVulnerabilityTL-2026-6372

PHP critical security release scheduled 19 Nov 2026 - CVE-2026-115560 RCE vector in session upload progress

criticalTRACKING

PHP has announced security releases for all supported versions on 19 Nov 2026 (14:00-14:30 UTC), with a highest severity of CRITICAL. CVE-2026-115560, an unpatched RCE vector in session upload progress that PHP described on 23 Oct 2026 as 'unlikely', is exposed only when session.serialize_handler is php_binary or php_serialize and code switches it to php via ini_set() before session_start() while upload progress stays enabled (the default). First disclosed .

Key facts

IdentifiersTL-2026-6372, CVE-2026-115560, CVE-2026-109619
SeverityCRITICAL
First disclosed
Exploitation statusLinked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-109619 (added )
EPSSCVE-2026-109619: 99.9% (99.9th percentile)
Affected productsPHP Group PHP
MalwarePHP, PHP2Shell
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1190 Exploit Public-Facing Application, T1588 Obtain Capabilities, T1592 Gather Victim Host Information, T1595 Active Scanning
MotivationUNKNOWN
Target sectorstechnology, government administration, finance, health, education, retail
Target regionsGlobal
Detection rules9 (1 shown free)
Sources11 cited sources

Detection coverage

As of 2026-11-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6372 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: PHP Web Worker Spawning Shell or Downloader (Post-Exploitation)

Post-exploitation detection. A PHP web worker (php-fpm, php-cgi, apache2 mod_php, httpd) spawning sh, bash, curl, wget, netcat or interpreters indicates RCE. Raises risk when the command line is a download-and-execute pattern or matches community-observed PHP2Shell/RedTail dropper infrastructure (TL_OSINT_Scan, community tier).

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1059.004, T1059, T1190, T1105
  • Data sources: sysmon_linux, mde_linux_process_events, auditd_execve
  • Severity: critical
  • Confidence: high

Splunk SPL

index=linux sourcetype="sysmon:linux" EventCode=1 earliest=-24h (ParentImage="*/php-fpm*" OR ParentImage="*/php-cgi*" OR ParentImage="*/apache2" OR ParentImage="*/httpd") (Image="*/sh" OR Image="*/bash" OR Image="*/dash" OR Image="*/curl" OR Image="*/wget" OR Image="*/nc" OR Image="*/ncat" OR Image="*/busybox" OR Image="*/python*" OR Image="*/perl")
| eval dropper=if(match(CommandLine,"(?i)(curl|wget)") AND match(CommandLine,"(?i)([|][[:space:]]*(ba)?sh|chmod[[:space:]]+[+]x|/tmp/|/dev/shm/)"),1,0)
| eval community_ioc=if(match(CommandLine,"(77[.]90[.]185[.]20|217[.]60[.]102[.]5|217[.]60[.]242[.]76|85[.]11[.]167[.]243|15[.]204[.]59[.]70|162[.]35[.]99[.]94)"),1,0)
| stats count values(CommandLine) as commands values(Image) as children max(dropper) as dropper_pattern max(community_ioc) as community_ioc_hit min(_time) as first_seen max(_time) as last_seen by host User ParentImage
| eval risk=case(community_ioc_hit=1,"critical", dropper_pattern=1,"high", true(),"medium")
| eval detection="TL-2026-6372 PHP worker spawning shell or downloader after CVE-2026-115560 / PHP2Shell RCE (T1059.004)"

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName startswith "php-fpm" or InitiatingProcessFileName in~ ("php-cgi", "apache2", "httpd")
| where FileName in~ ("sh", "bash", "dash", "curl", "wget", "nc", "ncat", "busybox", "python", "python3", "perl")
| extend DropperPattern = (ProcessCommandLine has_any ("curl", "wget")) and (ProcessCommandLine matches regex @"(?i)([|][[:space:]]*(ba)?sh|chmod[[:space:]]+[+]x|/tmp/|/dev/shm/)")
| extend CommunityIoc = ProcessCommandLine has_any ("77.90.185.20", "217.60.102.5", "217.60.242.76", "85.11.167.243", "15.204.59.70", "162.35.99.94")
| extend Risk = case(CommunityIoc, "critical", DropperPattern, "high", "medium")
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, DropperPattern, CommunityIoc, Risk

Sigma

title: PHP Web Worker Spawning Shell or Downloader
id: b4e7c210-6a93-4f1d-9c58-3d2e8a1f7b04
status: experimental
description: Detects php-fpm, php-cgi, apache2 or httpd spawning a shell, downloader or interpreter, the expected post-exploitation behaviour after successful PHP RCE (T1190 to T1059.004), including PHP2Shell-style exploitation and any future CVE-2026-115560 exploit.
references:
    - https://www.php.net/archive/2026.php#2026-10-21-5
    - https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp
author: Threadlinqs Team
date: 2026/11/18
tags:
    - attack.execution
    - attack.t1059.004
    - attack.initial-access
    - attack.t1190
    - attack.command-and-control
    - attack.t1105
logsource:
    category: process_creation
    product: linux
detection:
    selection_parent:
        ParentImage|contains:
            - 'php-fpm'
            - 'php-cgi'
            - '/apache2'
            - '/httpd'
    selection_child:
        Image|endswith:
            - '/sh'
            - '/bash'
            - '/dash'
            - '/curl'
            - '/wget'
            - '/nc'
            - '/ncat'
            - '/busybox'
            - '/perl'
    condition: selection_parent and selection_child
falsepositives:
    - Web applications that legitimately shell out (image processing, git, backups)
    - Admin scripts launched through mod_php CGI wrappers
level: high

Known false positives:

  • Web applications that intentionally shell out (ImageMagick, git, backup tooling)
  • Cron or admin wrappers run under the web user

Tuning notes: Baseline legitimate child processes per host and add exclusions on exact ParentImage plus CommandLine. Keep the dropper and community IOC branches unsuppressed. Community IPs are OSINT-tier corroboration; verify before blocking.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • PHP Version and Configuration Reconnaissance Burst · unlock with TL Creds
  • PHP Web Worker Writing PHP Files (Web Shell Staging) · unlock with TL Creds
  • PHP Web Worker Regular-Interval Beaconing · unlock with TL Creds
  • PHP Session Serialize Handler or Upload Progress Exposure Precondition Change · unlock with TL Creds
  • Cryptominer or Dropper Execution After PHP Web Compromise (RedTail-style) · unlock with TL Creds
  • Bare-IP Download Cradle Piped to Shell (PHP2Shell/RedTail Pattern) · unlock with TL Creds
  • PHP Session Upload Progress Abuse with Serialized Payload Markers (CVE-2026-115560) · unlock with TL Creds
  • PHP Web Worker Outbound to Community IOC or Unusual Port (C2/Ingress) · unlock with TL Creds

Indicators of compromise

As of 2026-11-18, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-6372.

Sample indicators (1 of 8)

  • URL: hxxps://www[.]php[.]net/archive/2026.php#2026-10-23-1

Defanged, TLP:CLEAR. Full set of 8 indicators: unlock with TL Creds.

8 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

On 23 October 2026 the PHP project published an informational advisory (relayed to oss-sec by Alan Coopersmith) for CVE-2026-115560, described as 'an unlikely RCE vector' in session upload progress. The advisory says the issue can occur only under an unusual combination of configuration and application code: the application (or its configuration) sets session.serialize_handler to php_binary or php_serialize, then switches it to php at runtime with ini_set() before calling session_start(), and session.upload_progress.enabled remains on (PHP's default). Applications that never change the serialize handler at runtime can keep upload progress enabled. PHP has not published the root cause, a CVSS score, CWE, affected version ranges or fixed versions; it said it would publish a full advisory with the next regular release. Secondary coverage (Astra) notes the advisory does not describe the bug as object injection or deserialization, and that it is unconfirmed whether it shares a root cause with CVE-2026-109619.

On 18 November 2026 PHP announced that security releases for all supported versions will ship on Thursday 19 November 2026 between 14:00 and 14:30 UTC as part of the regular four-week cycle. The announcement rates the highest severity CRITICAL, states that the CRITICAL issues require non-default configuration or uncommon setups, and says technical details and fixed version numbers will be published alongside the releases. The php.net announcement does not name CVE-2026-115560 explicitly; the link between this CVE and the upcoming release is made by Aikido Security, which reports that the 21 Oct releases do not fix it. The final CVE list and fixed versions are therefore still unconfirmed at the time of writing.

Context: the issue follows PHP2Shell (CVE-2026-109618, RCE via OOM corruption, GHSA-w8hw-w9fx-j79w; CVE-2026-109619, RCE via stale global state, GHSA-6wmf-4rv5-p3rp), two critical unauthenticated RCE flaws (CVSS v4.0 9.2 per PHP's 20 Oct notice) fixed on 21 Oct 2026 in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP2Shell saw exploitation attempts from 17 Oct (Amazon Threat Intelligence honeypots) and confirmed RCE on an Apache mod_php 8.4.26 honeypot reported by Adel Karimi on 24 Oct. For CVE-2026-115560 itself, no exploitation, public PoC, attribution or IOCs have been reported; it is not in CISA KEV and had no CVE.org/NVD record as of the most recent search coverage (about 10 Nov). Because the mitigation session.upload_progress.enabled=0 was already recommended for CVE-2026-109619, organizations that applied it in October are already protected from the described vector.

Defender guidance (per PHP and vendor sources): set session.upload_progress.enabled=0 in php.ini, the FPM pool or server configuration (not via ini_set() or .user.ini, since it must apply before request parsing); restart (not just reload) all PHP workers; verify on the serving SAPI rather than the CLI; audit code for runtime ini_set('session.serialize_handler', 'php') calls; and upgrade as soon as the 19 Nov releases are available.

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter

Initial Access

T1190 Exploit Public-Facing Application

Resource Development

T1588 Obtain Capabilities

Reconnaissance

T1592 Gather Victim Host Information; T1595 Active Scanning

Remediation

Patches

  • PHP security releases for all supported versions scheduled 19 Nov 2026 14:00-14:30 UTC; fixed version numbers not yet published
  • The 21 Oct 2026 releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) fix PHP2Shell but do not fix CVE-2026-115560

Immediate actions

  • Set session.upload_progress.enabled=0 in php.ini, the PHP-FPM pool (php_admin_flag[session.upload_progress.enabled] = off) or Apache mod_php config (php_admin_flag session.upload_progress.enabled off); do not rely on ini_set() or .user.ini
  • Restart all PHP workers (not just reload) and verify the value on the serving SAPI (php-fpm -i or phpinfo() via the web server), not the CLI
  • Audit code for runtime ini_set('session.serialize_handler', 'php') calls preceding session_start()
  • If upload_progress was already disabled for CVE-2026-109619 in October, keep it in place

Workarounds

  • session.upload_progress.enabled=0 until the next regular bugfix release
  • Applications that never change session.serialize_handler at runtime may keep upload progress enabled (per PHP)

Longer-term hardening

  • Upgrade all supported PHP branches as soon as the 19 Nov 2026 security releases are published and verify fixed version numbers against the full PHP advisory
  • Standardize session.serialize_handler in configuration and remove runtime handler switching
  • Replace server-side upload progress UIs that read $_SESSION with client-side XHR/fetch progress events

Affected and fixed versions

  • PHP Group — PHP
    Vulnerable versions: Not published; PHP states the 19 Nov 2026 release addresses all supported versions; not fixed in 8.5.12, 8.4.27, 8.3.36, 8.2.35 per Aikido and Cloudflare-attributed reporting
    Fixed in: Not yet published; to be announced with the 19 Nov 2026 releases

Timeline

  • Amazon honeypots record an attempted exploit of the related PHP2Shell flaws (CVE-2026-109618/109619), four days before disclosure.
  • PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fixing PHP2Shell; GHSA-6wmf-4rv5-p3rp lists session.upload_progress.enabled=0 as a mitigation. These releases do not fix CVE-2026-115560.
  • CISA shares a Sigma detection rule for the related PHP2Shell exploitation.
  • PHP publishes an informational advisory for CVE-2026-115560 ('unlikely RCE vector' in session upload progress), recommends session.upload_progress.enabled=0, and defers the full advisory to the next regular release; relayed to oss-sec.
  • Adel Karimi reports confirmed RCE with memory disclosure against an Apache mod_php 8.4.26 honeypot for PHP2Shell; no exploitation of CVE-2026-115560 reported.
  • PHP announces security releases for all supported versions scheduled 19 Nov 2026 14:00-14:30 UTC, highest severity CRITICAL (non-default configuration or uncommon setups); Aikido links CVE-2026-115560 to the release.
  • Scheduled PHP security releases (14:00-14:30 UTC); fixed version numbers and full CVE list to be published alongside.

Sources cited

Other reports on CVE-2026-115560

Other reports on CVE-2026-109619

Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats