Skip to the stories
Wednesday, 4 November 2026
Saved

Next edition

14:31

Headlines

Models & Products

PHP Project issues mitigation guidance following critical PHP2Shell vulnerabilities

The PHP Project has published temporary mitigation instructions after releasing patches for two critical remote code execution vulnerabilities affecting most PHP builds.

FTMQ SI, written by our newsroom0 views

Share
Picture: ZDNet AI

The PHP Project has released instructions to prevent a remote code execution vector linked to PHP2Shell attacks, ZDNet AI reported. The guidance follows a global effort by organizations to patch vulnerable websites after the discovery of two critical security flaws in the programming language. [1]

PHP2Shell involves two vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619, according to ZDNet AI. Both issues impact most PHP builds and have been assigned critical severity scores of 9.2 under version 4.0 of the Common Vulnerability Scoring System, Grokipedia noted. Official patches to address both security flaws were released on Wednesday. [1][6]

Technical documentation on Grokipedia indicates that CVE-2026-109618 involves an out-of-memory handling failure. PHP relies on longjmp calls to terminate a request. If an abort occurs while internal request data is only partially initialized, subsequent cleanup operations can process invalid data as valid. [6]

Exposed server interfaces identified for the flaws include PHP-FPM, the Apache HTTP Server module mod_php, php-cgi, FrankenPHP, and LiteSpeed, Grokipedia noted. The risk is highest for mod_php, where a demonstrated exploit can execute prior to any application code. [6]

Share

In short

  • PHP2Shell consists of two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619.
  • Both PHP vulnerabilities carry a CVSS 4.0 severity score of 9.2.
  • The PHP Project released official patches to fix the flaws on Wednesday.
  • Exposed server interfaces include PHP-FPM, mod_php, php-cgi, FrankenPHP, and LiteSpeed.

Sources

Every paragraph above points to the numbered items it rests on. Read the originals here.

  1. [1]PHP2Shell: Haven’t patched yet? Take these steps now to mitigateZDNet AI, 11d ago (the report this story comes from)
  2. [2]PHP2Shell: Haven’t patched yet? Take these steps now to mitigateZDNET, 11d ago

Background

  1. [3]Log4Shell on Wikipedia
  2. [4]Meltdown (security vulnerability) on Wikipedia
  3. [5]Transient execution CPU vulnerability on Wikipedia
  4. [6]PHP2Shell on Grokipedia

Our newsroom writes these reports with the help of software, from the 6 sources listed and nothing else, and checks them against those sources. Facts can still be wrong or move on; the originals are the record. Spotted a mistake? Write to daniel@monsterkong.com.

Earlier reports of ours on the same people and subjects.

More in Models & Products

Get the day in one email

Reports like this one, the top news of the last 24 hours, every morning. Free, one email a day; readers can comment under every report.

By signing up you agree to our terms and privacy policy. Unsubscribe any time.

Comments

Loading

Join the conversation

Comments are open to readers of our daily email: the top news of the last 24 hours, every morning, free. Sign up and the comment box opens.

Already on the list? Enter the same address and we will send a sign-in link.

By signing up you agree to our terms and privacy policy. Unsubscribe any time.