<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sooatek blog (English)</title><description>Technical posts by Sooatek: migrations, security, maintenance, AI. Primary sources cited.</description><link>https://sooatek.com/en/blog/</link><language>en-US</language><copyright>Sooatek</copyright><item><title>PHP2Shell: check your PHP version, mitigate, then patch</title><link>https://sooatek.com/en/blog/php2shell-check-mitigate-patch/</link><guid isPermaLink="true">https://sooatek.com/en/blog/php2shell-check-mitigate-patch/</guid><description>PHP2Shell (CVE-2026-109618 and CVE-2026-109619) affects PHP since version 5.4. How to check the version served, mitigate in an emergency, then patch.</description><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;PHP2Shell (CVE-2026-109618 and CVE-2026-109619) affects PHP since version 5.4. How to check the version served, mitigate in an emergency, then patch.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;PHP2Shell names two flaws in the PHP engine (CVE-2026-109618 and CVE-2026-109619), rated 9.2 out of 10 in CVSS v4.0 and made public on 21 October 2026: remote code execution, without an account.&lt;/li&gt;&lt;li&gt;Fix: PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12. Branches 5.x, 7.x, 8.0 and 8.1 have no fixed version: you need to migrate.&lt;/li&gt;&lt;li&gt;The version that matters is the one the web server runs, not the one reported by php -v: the two often differ on the same server.&lt;/li&gt;&lt;li&gt;Until you patch or migrate, rejecting multipart/form-data requests before they reach PHP limits exposure, at the cost of file uploads.&lt;/li&gt;&lt;/ul&gt;</content:encoded><category>Security</category><author>contact@sooatek.com (Florent Didelot)</author></item><item><title>PHP 8.2 security support ends on 31 December 2026: what to do</title><link>https://sooatek.com/en/blog/php-8-2-end-of-security-support/</link><guid isPermaLink="true">https://sooatek.com/en/blog/php-8-2-end-of-security-support/</guid><description>PHP 8.2 will receive no security fix after 31 December 2026. Official schedule, which version to target, changes to expect and a migration plan.</description><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;PHP 8.2 will receive no security fix after 31 December 2026. Official schedule, which version to target, changes to expect and a migration plan.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;On 31 December 2026, PHP 8.2 leaves security support: after that date, the PHP team publishes no fix at all for this branch, not even for a critical flaw.&lt;/li&gt;&lt;li&gt;In October 2026, two targets make sense: PHP 8.4, maintained until 31 December 2028, or PHP 8.5, maintained until 31 December 2029, depending on what your framework and dependencies accept.&lt;/li&gt;&lt;li&gt;Drupal 11 (versions 11.1 to 11.4) already requires at least PHP 8.3; Symfony 7.4 still runs on PHP 8.2, but Symfony 8 requires PHP 8.4.&lt;/li&gt;&lt;li&gt;A migration needs preparing: inventory of servers and dependencies, automated tests, reading the 8.3, 8.4 and 8.5 migration guides, a full trial in pre-production.&lt;/li&gt;&lt;/ul&gt;</content:encoded><category>Migration</category><author>contact@sooatek.com (Florent Didelot)</author></item></channel></rss>