How do we make sure the urgent PHP RCE fixes are actually running?

November 17, 2026 5 answers
Asked by 2y~gimbalbadge_814

CISA has flagged two PHP runtime vulnerabilities as exploited and set an October 29 remediation deadline for federal civilian agencies. What needs patching, and how can we verify the fix is active?

Answers

Nuvrali+5q

Patch PHP itself, not just WordPress, Drupal, or whatever application runs on it. The stated fixed releases are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. A vendor package with a backported fix can also address the issue.

Check the runtime serving web requests. The shell's php -v output may be from a different build than PHP-FPM or Apache uses. After updating, restart the relevant workers or web server and verify the loaded build again. Don't assume installing the package replaced code already running in memory.

r.247~socketladle:

Some package updates restart PHP-FPM automatically, but checking the service afterward is still worthwhile. Tools such as needrestart can help find processes using replaced files.

Reply to this answer
Jorvi

Don't reject a patched distro package just because the PHP version string looks old. Vendors including Red Hat and CloudLinux backport security fixes without necessarily changing the upstream version number.

Use the vendor's advisory or package changelog to map the installed package to both CVEs. For scanner disagreements, distro security data is more useful than a simple upstream version comparison.

Reply to this answer
2f!sproing_719

Containers need a little extra care. Rebuild and redeploy the image, but make sure the rebuild actually picks up a fixed base image. A pinned digest or cached base layer can leave you deploying the same vulnerable PHP again.

Update the pin if needed, pull the base during the build, and check the running container rather than trusting the pipeline result alone.

Reply to this answer
8j~plumratchet_461

PHP 8.1 and older don't have the listed upstream fixes. If an application is stuck there, look for a vendor backport or plan an upgrade to a fixed branch. CISA directs systems that cannot be updated to be taken offline until they can be remediated.

Reply to this answer
_r7+claspnori.5

There are two other checks worth keeping separate from the package update. Disable session.upload_progress.enabled as the advised mitigation for the separate CVE-2026-115560, and review logs back to October 17, when attempts were reported. Looking only after the patch date misses the earlier exposure window.

5n+quibblefin_284:

That setting addresses the separate issue. It isn't a substitute for patching the two CISA-listed runtime flaws.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions