CVE-2026-109619: PHP Stale Internal Request-State Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).
Description quoted from the CVE record (assigned by php, published 2026-10-21).
Weakness: CWE-416 Use after free; CWE-755 Improper Handling of Exceptional Conditions; CWE-824 Access of uninitialized pointer; CWE-1325 Improperly controlled sequential memory allocation; CWE-1419 Incorrect Initialization of Resource
How it can be exploited
Exploitable over the network with high attack complexity only when specific conditions are present needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2026-10-26
- US federal deadline
- 2026-10-29
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2026-17192, SNYK-ALMALINUX9-PHP-21691221, SNYK-ALMALINUX9-PHP-21691232, SNYK-ORACLE10-PHP84CLI-21432983, SNYK-ORACLE10-PHP84DBA-21432998, SNYK-ORACLE10-PHP84DEVEL-21432918, SNYK-ORACLE10-PHP84EMBEDDED-21432941, SNYK-ORACLE10-PHP84FFI-21432909, SNYK-ORACLE10-PHP84GD-21432906, SNYK-ORACLE10-PHP84OPCACHE-21432969, SNYK-ORACLE10-PHP84XML-21433065, SNYK-ORACLE10-PHPCOMMON-21432914, SNYK-ORACLE10-PHPDBA-21432988, SNYK-ORACLE10-PHPDBG-21432993, SNYK-ORACLE10-PHPEMBEDDED-21432997, SNYK-ORACLE10-PHPFPM-21432972, SNYK-ORACLE10-PHPPGSQL-21432991, SNYK-ORACLE10-PHPPROCESS-21433097, SNYK-ORACLE10-PHPXML-21433012
VEDAS cluster: VEDAS:BARGEBAT
Exploit Observer links 68 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (68)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://github.com/1amrahul/php2shell-cve-2026-109618-cve-2026-109619
- Code repository: https://github.com/1nightlovel/cve-2026-109619
- Code repository: https://github.com/absholi7ly/deep-technical-report-cve-2026-109618-cve-2026-109619-php2shell
- Code repository: https://github.com/aduli198/cve-2026-109618_cve-2026-109619
- Code repository: https://github.com/ampedwastaken/php2shell-cve-2026-109618-cve-2026-109619
- Code repository: https://github.com/avaterxxx/cve-2026-109618-cve-2026-109619-
- Code repository: https://github.com/baimaobg/php-cve-2026-109619-lab
- Code repository: https://github.com/baron-stybd/cve-2026-109618-cve-2026-109619
- Code repository: https://github.com/basesixtythree/b63-poc-cve-2026-109619
- Code repository: https://github.com/certbn/php2shell-cve-2026-109618-cve-2026-109619-
- Code repository: https://github.com/cj667113/oci-ansible-fix-cve-2026-109618_cve-2026-109619
- Code repository: https://github.com/cozybear-dev/cve-2026-109619
- and 56 more
Research and write-ups (31)
- Research or write-up: https://almalinux.org/blog/2026-10-21-php2shell-cve-2026-109618-cve-2026-109619
- Research or write-up: https://app.crowdsec.net/hub/author/crowdsecurity/waf-rules/vpatch-CVE-2026-109619
- Research or write-up: https://app.cveplayground.com/labs/CVE-2026-109619
- Research or write-up: https://aws.amazon.com/blogs/security/using-aws-waf-to-apply-mitigations-for-php2shell-rce-vulnerabilities-cve-2026-109618-and-cve-2026-109619
- Research or write-up: https://bidb.metu.edu.tr/tr/haberler/php-altyapisini-etkileyen-kritik-guvenlik-aciklari-cve-2026-109618-ve-cve-2026-109619
- Research or write-up: https://blog.cloudlinux.com/php-cve-2026-109618-and-cve-2026-109619
- Research or write-up: https://cloud.google.com/blog/products/identity-security/responding-to-core-php-vulnerabilities-cve-2026-109618-cve-2026-109619
- Research or write-up: https://community.citrix.com/techzone-blogs/110_security-updates/protecting-netscaler-management-access-from-php-cve-2026-109618-cve-2026-109619-r1640
- Research or write-up: https://cveplayground.com/blog/php-rce-cve-2026-109618-and-cve-2026-109619
- Research or write-up: https://db.gcve.eu/vuln/CVE-2026-109619
- Research or write-up: https://forums.apiscp.com/t/v3-2-49-2-cve-2026-109618-cve-2026-109619/1097/2
- Research or write-up: https://git.iscsp.ulisboa.pt/trincheiras/php-cve-2026-109618-cve-2026-109619
- and 19 more
Vulnerability databases and vendor advisories (35)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://access.redhat.com/security/cve/cve-2026-109619
- Vulnerability database or vendor advisory: https://forum.multiportal.io/topic/110/security-advisory-critical-php-vulnerabilities-cve-2026-109618-and-cve-2026-109619
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-109619
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/ROOT-OS-ALPINE-315-CVE-2026-109619
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/ROOT-OS-ALPINE-318-CVE-2026-109619
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/ROOT-OS-UBUNTU-2004-CVE-2026-109619
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/ROOT-OS-UBUNTU-2504-CVE-2026-109619
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/ROOT-OS-UBUNTU-2510-CVE-2026-109619
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/UBUNTU-CVE-2026-109619
- Vulnerability database or vendor advisory: https://security.paloaltonetworks.com/CVE-2026-109619
- Vulnerability database or vendor advisory: https://security.snyk.io/vuln/SNYK-ALMALINUX9-PHP-21691221
- Vulnerability database or vendor advisory: https://security.snyk.io/vuln/SNYK-ALMALINUX9-PHP-21691232
- and 23 more
News (1)
1755 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 1.000
very likely to be attacked soon - VEDAS
- 0.982
strong exploit evidence - On CISA KEV
- Yes, since 2026-10-26
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
VEDAS flagged this bug about 2 days before CISA confirmed attacks.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| PHP Group PHP (php-src) | from 8.2.* before 8.2.35 from 8.3.* before 8.3.36 from 8.4.* before 8.4.27 from 8.5.* before 8.5.12 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: php php, php_group php, ооо_«а-реал_консалтинг» программный_межсетевой_экран_интернет_контроль_сервер_(фстэк).
How to fix it
Fixed versions stated in the CVE record: 8.2.35, 8.3.36, 8.4.27, 8.5.12.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset’s internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Vendor guidance:
- https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp (vendor-advisory)
How to detect it
Nuclei template (active check)
PHP - session.upload_progress Use-After-Free RCE (Attack-Surface Probe)
CVE-2026-109619 is a use-after-free in the PHP rfc1867 session.upload_progress handler: a zval cached from an early multipart part is dereferenced after its backing progress/session tree has been freed and reclaimed by attacker-controlled heap data, yielding a forged zend_fcall_info call-frame primitive that an unauthenticated attacker turns into remote code execution. Two public exploit families exist: a leak-dependent one requiring a pre-supplied libphp pointer and build-specific offsets, and a self-leaking ASLR-bypass chain that first leaks the Zend MM chunk base and libphp base through the Set-Cookie PHPSESSID value before forging the call frame. Both require a large heap spray and are memory-corruption, so exploitation cannot be confirmed with a single safe request. This template is a non-destructive attack-surface probe: it sends two benign upload-progress multipart requests and flags either precondition the chains depend on - (1) the handler’s session-ID validation warning for an illegal-character identifier (display_errors path), or (2) reflection of an attacker-chosen session identifier in Set-Cookie (session.use_strict_mode=0, the fixation/heap-leak primitive). It does not attempt or confirm memory corruption; on-wire exploit attempts are covered by the paired Suricata rule.
Name and description quoted from the template, written by VEDAS.
The template sends 2 requests (POST /, POST /?PHPSESSID={{marker}}); it decides using dsl matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-109619.yamlShow the template (91 lines)
id: CVE-2026-109619
info:
name: "PHP - session.upload_progress Use-After-Free RCE (Attack-Surface Probe)"
author: vedas-arpsyndicate
severity: high
description: |
CVE-2026-109619 is a use-after-free in the PHP rfc1867 session.upload_progress handler: a zval cached from an
early multipart part is dereferenced after its backing progress/session tree has been freed and reclaimed by
attacker-controlled heap data, yielding a forged zend_fcall_info call-frame primitive that an unauthenticated
attacker turns into remote code execution. Two public exploit families exist: a leak-dependent one requiring
a pre-supplied libphp pointer and build-specific offsets, and a self-leaking ASLR-bypass chain that first
leaks the Zend MM chunk base and libphp base through the Set-Cookie PHPSESSID value before forging the call
frame. Both require a large heap spray and are memory-corruption, so exploitation cannot be confirmed with a
single safe request. This template is a non-destructive attack-surface probe: it sends two benign
upload-progress multipart requests and flags either precondition the chains depend on - (1) the handler's
session-ID validation warning for an illegal-character identifier (display_errors path), or (2) reflection
of an attacker-chosen session identifier in Set-Cookie (session.use_strict_mode=0, the fixation/heap-leak
primitive). It does not attempt or confirm memory corruption; on-wire exploit attempts are covered by the
paired Suricata rule.
reference:
- https://www.exploit.observer/?keyword=CVE-2026-109619&match=exact
- https://subdomain.center/?engine=ammonites&keyword=php&match=exact
classification:
cvss-metrics: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
cvss-score: 8.6
cve-id: CVE-2026-109619
cwe-id: CWE-416
metadata:
verified: false
max-request: 2
tags: cve,cve2026,php,uaf,rce,upload-progress,intrusive
variables:
marker: "{{rand_base(12)}}"
sid_invalid: "{{randstr}}/{{rand_base(20)}}"
http:
- raw:
- |
POST / HTTP/1.1
Host: {{Hostname}}
Content-Type: multipart/form-data; boundary=----{{randstr}}
------{{randstr}}
Content-Disposition: form-data; name="PHPSESSID"
{{sid_invalid}}
------{{randstr}}
Content-Disposition: form-data; name="PHP_SESSION_UPLOAD_PROGRESS"
{{marker}}
------{{randstr}}
Content-Disposition: form-data; name="f"; filename="{{marker}}.txt"
Content-Type: text/plain
Z
------{{randstr}}--
- |
POST /?PHPSESSID={{marker}} HTTP/1.1
Host: {{Hostname}}
Content-Type: multipart/form-data; boundary=----{{randstr}}
------{{randstr}}
Content-Disposition: form-data; name="PHPSESSID"
{{marker}}
------{{randstr}}
Content-Disposition: form-data; name="PHP_SESSION_UPLOAD_PROGRESS"
{{marker}}
------{{randstr}}
Content-Disposition: form-data; name="f"; filename="{{marker}}.txt"
Content-Type: text/plain
Z
------{{randstr}}--
disable-cookie: true
stop-at-first-match: true
matchers-condition: or
matchers:
- type: dsl
name: session-id-validation-warning
dsl:
- 'contains(body, "Session ID is too long or contains illegal characters")'
- type: dsl
name: attacker-session-id-reflected
dsl:
- 'contains(all_headers, "PHPSESSID={{marker}}")'
CVE-2026-109619.yaml on GitHub
Suricata rules (network detection)
2 rules that alert on traffic matching this exploit: VEDAS CVE-2026-109619 PHP - session.upload_progress Use-After-Free RCE (Attack-Surface Probe) Attempt. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-109619 PHP - session.upload_progress Use-After-Free RCE (Attack-Surface Probe) Attempt"; flow:established,to_server; http.method; content:"POST"; http.request_body; content:"PHP_SESSION_UPLOAD_PROGRESS"; nocase; fast_pattern; content:"PHPSESSID"; nocase; classtype:attempted-admin; reference:cve,CVE-2026-109619; reference:url,https://www.exploit.observer/?keyword=CVE-2026-109619&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=php&match=exact; sid:1043401; rev:3;)
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-109619 PHP session.upload_progress UAF RCE Forged system Call-Frame"; flow:established,to_server; http.method; content:"POST"; http.request_body; content:"PHP_SESSION_UPLOAD_PROGRESS"; nocase; fast_pattern; content:"name=|22|t[]|22|"; nocase; content:"system|00|"; classtype:attempted-admin; reference:cve,CVE-2026-109619; reference:url,https://www.exploit.observer/?keyword=CVE-2026-109619&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=php&match=exact; sid:1049800; rev:1;)
CVE-2026-109619.rules on GitHub
Advisories on this CVE
- PHP2Shell (CVE-2026-109618, CVE-2026-109619): patch the PHP engine, not just your app (full advisory)
References
Vendor advisories and patches
- https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp (vendor-advisory)
Exploits and technical analysis
- https://www.wiz.io/blog/php2shell-php-rce (third-party-advisory)
- https://php2shell.delftintellab.com/ (third-party-advisory)
- https://arcticwolf.com/resources/blog/php2shell-critical-php-vulnerabilities-enable-unauthenticated-remote-code-execution/ (third-party-advisory)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-109619 (government-resource)
Other references
- http://www.openwall.com/lists/oss-security/2026/10/21/7
- http://www.openwall.com/lists/oss-security/2026/10/21/16
- http://www.openwall.com/lists/oss-security/2026/10/21/17
- http://www.openwall.com/lists/oss-security/2026/10/21/23
- http://www.openwall.com/lists/oss-security/2026/10/22/2
- http://www.openwall.com/lists/oss-security/2026/10/22/14
- http://www.openwall.com/lists/oss-security/2026/10/22/15
- http://www.openwall.com/lists/oss-security/2026/10/22/16
- http://www.openwall.com/lists/oss-security/2026/10/22/19
- http://www.openwall.com/lists/oss-security/2026/10/22/20
- http://www.openwall.com/lists/oss-security/2026/10/23/4
- https://cert-portal.siemens.com/productcert/html/ssa-566512.html
2 more
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.