Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityopen-source-dependency-vulnerabilitydetection-content-updatewidely-deployed-product-advisory

Critical PHP RCE Flaws Prompt Patching as Scanner Fixes Expose False-Safe Results

Vulnerability Disclosure · 13 sources · Updated 2h ago · First seen Nov 19, 2026

Critical PHP RCE Flaws Prompt Patching as Scanner Fixes Expose False-Safe Results

Two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, can enable unauthenticated remote code execution in web-serving installations, according to Red Sift. Both carry reported CVSS v4.0 scores of 9.2 and involve out-of-memory corruption and stale per-request state. Apache mod_php is identified as the highest-risk deployment because a demonstrated exploit runs during request parsing, before application code executes. The PHP security team reportedly released fixes in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Organizations should inventory standalone and embedded PHP installations, apply fixed releases or vendor backports, restart all workers, and investigate potentially compromised systems; configuration mitigations do not replace patching.

Subsequent php2shell testing reported vulnerable behavior across tested end-of-life PHP 5.6–8.1 releases and uncovered false SAFE verdicts, incompatible warning matchers, and a broken upstream Nuclei template. Repository updates corrected detection and defensive-rule logic and distinguished inconclusive results from patched systems. Remote checks on PHP 7.4 and earlier depend on exposed startup warnings, so missing signatures do not establish safety. The repository also added prerequisite checks for CVE-2026-115560, a session serializer mismatch it says remains unfixed in the releases above. Exploitation requires an application-level runtime handler switch that the checker cannot confirm; the maintainers recommend disabling session upload progress to close the described poisoning path. The supplied references do not document a victim incident or observed exploitation campaign.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

14 events · Oct 20, 2026 – Nov 19, 2026
  1. Nov 19, 202616h ago

    UpGuard reports sharp PHP2Shell remediation gap for end-of-life PHP

    UpGuard reported tracking nearly 14,000 companies exposed to PHP2Shell, finding that starting PHP version was the strongest predictor of remediation. Around 90% of sites running supported PHP versions showed a fix within two weeks, compared with rates as low as 3% for end-of-life versions; industry, region, and company size made little difference.

    PHP2Shell Shows the Real Cost of Outdated Software | Labs by UpGuard | SecuritySenses
  2. Oct 28, 202623d ago

    Palo Alto Networks confirms PHP2Shell exploitation against PAN-OS

    Palo Alto Networks confirmed attackers were exploiting both PHP2Shell vulnerabilities against internet-exposed PAN-OS management interfaces. The reported campaign bypassed ASLR and chained PHP2Shell with Fragnesia (CVE-2026-46300) to obtain root access on 24 firewalls and one management server across four countries.

    Everything Is a Web Application, Including Your Firewall
  3. Oct 28, 202623d ago

    php2shell adds prerequisite checker for CVE-2026-115560

    Commit d6a4f3b added a checker for server-side prerequisites of a session serializer mismatch that the repository describes as a potential remote code execution path not fixed by the October 21 PHP releases. The checker cannot confirm the required application-side handler switch, so positive results indicate prerequisites rather than confirmed exploitability.

    P0 fixes: bulk verdict semantics, nuclei version regex, ModSec phases… · cyberok-org/php2shell@d6a4f3b · GitHub
  4. Oct 28, 202623d ago

    php2shell corrects scan verdicts, version matching, and defensive rules

    Commit d6a4f3b revised bulk scan outcomes to distinguish inconclusive results from patched systems and corrected Nuclei version matching that could confuse PHP 8.2.3 with 8.2.35. It also repaired ModSecurity inspection logic and Suricata multipart detection rules.

    P0 fixes: bulk verdict semantics, nuclei version regex, ModSec phases… · cyberok-org/php2shell@d6a4f3b · GitHub
  5. Reported Oct 22, 202629d ago

    php2shell updates detection for older PHP and repairs Nuclei templates

    Commit f6f2fcb revised local callback-marker detection and remote warning matching to recognize vulnerable behavior across tested PHP 5.6–8.1 releases, and repaired incompatible Nuclei template syntax. The changes distinguish inconclusive responses from evidence of safety, particularly where older PHP installations suppress startup warnings.

    Extend coverage to EOL PHP (5.6-8.1): fix false SAFE in 109619 local,… · cyberok-org/php2shell@f6f2fcb · GitHub
  6. Oct 22, 202629d ago

    Compatibility tests expose false SAFE verdicts on end-of-life PHP releases

    Testing found that older PHP releases exhibited CVE-2026-109619 vulnerable behavior despite detection gaps, including a false SAFE local verdict on PHP 7.4.33; PHP 8.2.35 produced the expected patched remote signature. During separate CVE-2026-109618 testing, PHP 7.0.33 crashed with SIGSEGV on a multipart-header input.

    Extend coverage to EOL PHP (5.6-8.1): fix false SAFE in 109619 local,… · cyberok-org/php2shell@f6f2fcb · GitHub
  7. Oct 22, 202629d ago

    php2shell expands CVE-2026-109619 scanning and adds session-anomaly rules

    Commit 6dd5a90 adds remote and concurrent bulk scanning with JSON output to the CVE-2026-109619 checker, plus ModSecurity and Suricata rules for upload-progress parameters and malformed PHP session cookies. Warning-based checks can return inconclusive results, but the bulk summary misleadingly counts those as not vulnerable; the changes do not demonstrate exploitation.

    Add 2 new rules (Ziv00s3 suggestions) + upgrade 109619 to bulk+remote · cyberok-org/php2shell@6dd5a90 · GitHub
  8. Reported Oct 22, 202629d ago

    php2shell adds bulk scanning, Nuclei template, and phpMyAdmin retesting

    CyberOK's commit 2ea3f3a expands php2shell with threaded bulk scanning, custom paths, JSON output, a Nuclei template, and phpMyAdmin-specific retesting through show_config_errors.php. Remote verdicts depend on warning signatures or advertised PHP versions; edge rejection responses do not establish that the underlying PHP installation is patched.

    Bulk scan, custom paths, nuclei template, phpMyAdmin retest, FPM cras… · cyberok-org/php2shell@2ea3f3a · GitHub
  9. Reported Oct 21, 202630d ago

    php2shell adds invalid-session-ID remote probe and ModSecurity response rule

    Commit ad34012 replaces remote reachability checks with a single-request probe, credited to PortSwigger and Tom SL, that detects session-write attempts after session startup fails. It also adds a ModSecurity response-signature rule for CVE-2026-109618 and CVE-2026-109619; remote responses lacking the expected warnings remain inconclusive.

    Remote mode: PortSwigger invalid-SID technique + ModSec response rule · cyberok-org/php2shell@ad34012 · GitHub
  10. Reported Oct 21, 202630d ago

    php2shell adds post-patch session-poisoning surface checker

    CyberOK added a local checker for configuration-dependent session-poisoning paths that may remain after patching CVE-2026-109618 and CVE-2026-109619, and expanded Suricata signatures. The checker supplies its own PHP settings and does not establish production exposure or code execution, which requires an additional application-level inclusion or deserialization sink.

    Add post-patch surface safecheck (session poisoning exposure) · cyberok-org/php2shell@d84d854 · GitHub
  11. Reported Oct 21, 202630d ago

    php2shell fixes Suricata detection of oversized PHPSESSID response cookies

    Commit 87a27d6 changes Suricata signature 1000006111, targeting a CVE-2026-109618 session-cookie leak, to inspect HTTP response headers and removes the HTTP 200 status requirement. It retains matching for PHPSESSID cookie values of at least 200 characters; the excerpt does not establish exploitation in the wild.

    Fix SID 6111 (http.set_cookie → http.response_header); FPM validation · cyberok-org/php2shell@87a27d6 · GitHub
  12. Oct 21, 202630d ago

    php2shell adds six rules for handler mismatch, oversized cookies, and giant filenames

    Commit a84fdb0 added three Suricata signatures and three ModSecurity rules targeting PHP upload-progress exploitation patterns; the commit reports all three Suricata signatures triggered in testing while clean controls remained silent. The implementations differ in coverage: ModSecurity retains a lowercase-only handler-mismatch expression and a higher filename-length threshold.

    Add 3 new signatures from xue-poc audit + fix validation bugs · cyberok-org/php2shell@a84fdb0 · GitHub
  13. Oct 21, 202630d ago

    PHP releases fixes for CVE-2026-109618 and CVE-2026-109619

    The PHP security team released PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 to address both vulnerabilities. Older branches require vendor backports, available source patches, or upgrades, and all PHP workers must be restarted after patching.

    Critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 | Red Sift
  14. Oct 20, 20261mo ago

    PHP security team announces two critical remote code execution vulnerabilities

    The PHP security team announced CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2, involving memory corruption and stale request state. The flaws can enable unauthenticated remote code execution, with Apache mod_php identified as the highest-risk deployment.

    Critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 | Red Sift
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.