decrypted · 20 november 2026 · ransomware and cybercrime · vulnerabilities and patching · uk policy and law
PHP's seven critical flaws land four weeks after PHP2Shell
PHP, the scripting language behind a large share of the web, shipped fixes on Thursday for seven flaws it rates critical. Each can lead to remote code execution (RCE), which means a stranger running their own code on your server. SecurityWeek's reporting gives no sign that these seven are being exploited yet. But they arrive four weeks after PHP2Shell, a pair of flaws that attackers were probing before any patch existed, and several touch the same machinery. If you run a website, intranet or customer portal on PHP, this is a patching week, not a patching quarter.
What was fixed
PHP said the critical issues "require either non-default configuration or uncommon setups", which is reassuring but not a pass. Several concern sessions, the code that remembers who you are between page loads. In one, data is written in one format and read back in another, so a decoder can mistake part of it for instructions. Picture a post room where a parcel labelled as a letter is opened by the wrong clerk.
The one to read twice sits in PHP-FPM, the process manager many hosts use. Unread bytes of a request can be treated as a second request, slipping past front-end routing and running PHP code as the worker. SecurityWeek says an attacker needs no login.
Full fixes are in PHP 8.6.0 and 8.5.13. Most issues are also fixed in 8.4.28, 8.3.37 and 8.2.36. PHP says 8.2 reaches end of life on 31 December 2026.
Why October matters
According to SecurityWeek, Amazon saw the first PHP2Shell exploitation on 17 October, four days before the 21 October patches, while the flaws were still under embargo. Cloudflare's chief executive reported thousands of attempts in the ten hours before the announcement, rising to millions later. WatchTowr said none of the public proof-of-concept code it saw achieved code execution, so much of that was noise. The lesson is about time: the gap between disclosed and attacked is measured in hours.
The Secure by Design lesson
Opinion, not advice: three decisions limit the damage. First, do not rebuild objects from data your own code did not produce, because two of the seven turn on exactly that. Second, run each site as its own low-privilege user, so one flaw does not hand over every secret on the server. Third, keep an inventory with an owner for every PHP version in service. PHP 8.1 and older get no project updates, so a forgotten legacy site is the likeliest victim. Several of the seven also need help from the application itself, such as a suitable chain of code to abuse. The cost is a day of listing and a week of upgrades. Compare that with an incident review, a regulator's questions and customers asking what you knew.
Also this week
Transport for London. TfL said around 265,000 Oyster photocard customers may have had account details exposed, up from an earlier estimate of 250,000, according to BleepingComputer. The data includes names, contact details, dates of birth and security questions and answers. TfL says passwords, payment details and journey data were not compromised. It spotted the problem on 16 November, when customers received emails asking them to create accounts they already had, and The Register reports it took the photocard website down at once. Those affected include children as young as five, students and Londoners aged 60 and over. TfL has told the Information Commissioner's Office, the UK's data regulator, and has not said how the attackers got in, so we will not guess. The design point stands regardless: security questions are static secrets that cannot be changed after a leak. Collect less, and plan to be breached anyway. BleepingComputer does not link this to TfL's 2024 attack, which it says cost £29 million.
Cyber Security and Resilience Bill. In late October the House of Lords defeated the government twice, according to VinciWorks: 202 to 155 for a mandatory review of whether more sectors, such as cloud services and frontier AI, belong in scope, and 194 to 155 for a register of foreign powers that threaten UK cyber security. The government argued a country-based register could create false certainty. The Bill must return to the Commons, and we could not confirm its current stage from Parliament's own pages, so treat it as live but unfinished. For directors the practical point is that cloud and AI suppliers could eventually fall inside the regime you depend on, which is worth asking your own suppliers about now.
Sources
- SecurityWeek: PHP patches seven critical RCE vulnerabilities
- PHP.net: 2026 news archive and security release notices
- SecurityWeek: PHP2Shell exploitation started days before patches
- BleepingComputer: Transport for London breach exposes 265,000 Oyster card users' data
- The Register: TfL takes Oyster photocard website offline after attackers compromise customer accounts
- VinciWorks: Cyber Security and Resilience Bill, government defeated twice as Lords demand stronger protections
If PHP sits behind anything you run and you want a second pair of eyes on it, get in touch.
More like this
- The patch that broke the network: a week of outages and what officials say 18 november 2026
- The Lords beat the government on the Cyber Security Bill, and the gap is in design 3 november 2026
- The ICO's verdict on a twelve-year-old test account called Test2 20 october 2026
Get the next post by email: subscribe to Decrypted. Double opt-in, unsubscribe any time, or take the RSS feed.
Prefer to listen? Decrypted on Apple Podcasts, or paste the podcast feed into any app.