Understand
Read what the PHP weaknesses mean and which installations need attention.
Read the advisory →BYTOVA / SECURITY RESPONSE 2026
Critical PHP advisory · Official fixes available
Understand the risk.
Take the next step.
Clear guidance for website owners. Careful tools for administrators. Start with the facts, then make a safe update plan.
Free to use. No account. No website scanning.
Published · Sources checked · Next review due 29 October 2026
A USEFUL PLACE TO START
Choose your next action.
Check
Compare a locally supplied version or a verified vendor package.
Open the version checker →Get the fix
Find the official download or vendor update, then follow a careful remediation plan.
Get official patches →EVIDENCE BEFORE ASSURANCE
A PHP number is
only part of the picture.
A hosting provider or Linux distribution may backport a fix while keeping an older version number. The checker treats unknown packages cautiously and links you to the vendor records.
It never asks for a password or sends a request to your website.
Get the response resources| PHP branch | Fixed release | PHP-project security support ends |
|---|---|---|
| 8.2 | 8.2.35 | 2026-12-31 |
| 8.3 | 8.3.36 | 2027-12-31 |
| 8.4 | 8.4.27 | 2028-12-31 |
| 8.5 | 8.5.12 | 2029-12-31 |
Sources: PHP official security announcement · Ubuntu package status: CVE-2026-109618.
HELP FIRST
Useful without a signup.
Read, check and download freely. If you want help, describe your situation before booking. Server remediation and incident response need an agreed scope and may require a specialist.
Ask about suitable help