PHP security response21 October 2026 · Two critical RCE advisoriesRead the guidance

YOUR RMM. YOUR FLEET. CLEARER EVIDENCE.

Know which PHP runtimes still need attention.

Build an inspectable script. Run it through your RMM. See patch evidence, worker activation, and discovery gaps in one private dashboard.

Assess first. Configuration changes are always explicit.

A PRACTICAL RESPONSE LOOP

From script to fleet visibility.

01

Configure & inspect

Choose Windows or Linux, set discovery boundaries, and review the exact script before downloading.

02

Deploy with your RMM

Use your existing execution workflow and secret field. No persistent agent or remote command channel.

03

Review the evidence

Private reports show separate patch, activation, mitigation, and coverage states. Follow up where evidence is missing.

PATCHING IS THE COMPLETE SOLUTION

Partial mitigations do not make PHP safe.

Target PHP 8.2.35, 8.3.36, 8.4.27, or 8.5.12, or your vendor’s confirmed backport. Restart every affected worker.

Read patch and mitigation guidance