Is PHP2Shell fixed on Sakura Internet?

Status as of October 26, 2026: Sakura Internet reports patching PHP on its managed plans (partly confirmed in two of its own documents).

The short answer

Sakura Internet reports necessary fixes applied, including to the end-of-support PHP versions it offers: Rental server. VPS: sakura says PHP isn’t used in the VPS service itself; customers running PHP on a VPS should update. Sakura Cloud database appliance: web UI features suspended in response to the PHP vulnerability. We found two of the host’s own documents saying so. A host’s statement covers its managed platform, not a server you run yourself (source: GoDaddy). A fixed package only counts once it’s installed and PHP has restarted (source: AlmaLinux). A related flaw, CVE-2026-115560, has no fix in any PHP release as of October 23, 2026 (source: php.net advisory on CVE-2026-115560, October 23, 2026).

Fix status on Sakura Internet

How to check on Sakura Internet (read-only)

On the rental server, ask Sakura support to confirm for your account. On a VPS or cloud server, check the server itself.

If someone else runs your server, ask them in writing: the questions and a copy-ready email. If it’s your own VPS or server, nobody patches PHP for you; check it with the steps for your Linux distribution in the status table. (source (source: GoDaddy))

CVE-2026-115560

On October 23, 2026, PHP disclosed a related flaw, CVE-2026-115560, that the October 21 releases don’t fix. Until its next regular bugfix release, PHP recommends turning off session upload progress (session.upload_progress.enabled=0) in the server configuration and restarting PHP. Setting it from application code (ini_set()) or a per-directory .user.ini file doesn’t count (source: php.net advisory on CVE-2026-115560, October 23, 2026).

On Sakura Internet: Sakura’s notices don’t mention CVE-2026-115560.

Notes for Sakura Internet

• Sakura said that as of 17:00 on October 23, 2026 (no time zone stated), no damage from unauthorized access or data leakage exploiting the vulnerability had been reported.
• Your host may have patched PHP: Sakura said it did. Ask for written confirmation for your account (source: GoDaddy).

Sources (checked October 26, 2026)

• Sakura Internet: 【重要】PHPの脆弱性に関する当社の対応状況について. Page date: Oct 22, 2026; addendum Oct 23, 2026 17:30. States: Rental server: necessary fixes applied, including end-of-support PHP versions offered; VPS: PHP not used in the service itself, customers running PHP on a VPS should update; no damage reported as of Oct 23 17:00.
• Sakura Internet (Sakura Cloud): Database appliance feature suspension. Page date: Oct 21, 2026. States: Web UI features of the database appliance suspended in response to the PHP vulnerability.

Upstream facts (fixed releases, CVE-2026-115560, end-of-life dates) are footnoted to /sources. We list a build as confirmed only when two different primary documents state it. Method.

Related

Xserver · Lolipop · All platforms · How to prove your server is patched · What to ask your host or developer

Want it checked for you?

• Patch Verification & Compromise Review. Collection is read-only, and we change nothing on your server. You get a plain-English report: where each fix stands, as of a stated time, plus a compromise review from October 17, signed by the Approver of Record. Ask for it
• Check it yourself, free. The read-only steps are on our PHP2Shell page. Our open-source self-check script is publishing soon.