Another unpatched PHP RCE? How worried should admins be?

November 17, 2026 4 answers
Asked by _b58!morrowclip.6

I saw a report of another PHP remote code execution flaw shortly after the emergency PHP patches. How broadly does it affect applications, and what should admins do while there is no patch?

Answers

_s47!packetspanner.2

The reported conditions are pretty specific. An application has to configure session.serialize_handler as php_binary or php_serialize, then change it to php with ini_set() before calling session_start(). That is a much narrower target than every PHP installation.

Check the application configuration and code for that combination before treating the headline as an environment-wide emergency. The report describes the risk as unlikely, not impossible.

_t95~clayvisor.3:

Also check code that sets up sessions indirectly, not just the main configuration file. The runtime change is part of the reported condition.

Reply to this answer
q.613+plumgauge

If you already applied the temporary mitigation recommended for PHP2Shell, check whether it covers this issue too. The discussion indicates that it does, but verify the current PHP advisory and your actual configuration rather than assuming every server has the mitigation in place.

Keep an eye out for a patch and plan to apply it. A mitigation is useful breathing room, not a substitute for tracking the fix.

Reply to this answer
9x~gobletwinder_672

Not every RCE report needs the same response. Exposure, the required configuration, available mitigations and patch availability should drive the urgency. A narrow issue may fit a normal patch cycle, while a broadly exposed one may need a faster change.

That decision also needs a path through management. If emergency changes always require waiting for the next late-night maintenance window, agree in advance on who can approve an exception and how affected services will be checked afterward.

Reply to this answer
_u53!hingequartz.9

Keeping an application internal only can reduce exposure, but it is not a fix for vulnerable code or configuration. It still makes sense to check which systems meet the reported conditions and follow the patch status.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions