Skip to main content
Operations8 min read

Who patches the server behind your business tools? Three critical flaws in a month

PHP, Apache and nginx each fixed a critical flaw in four weeks. If your business runs its own tools on a server, here is who patches it and what to ask.

Between 21 October and 18 November 2026, three widely used pieces of server software each shipped a fix for a critical flaw: PHP, the Apache web server and the nginx web server. If your business runs a website, a web application or its own tools for files, email or chat on a server, one of them may be involved somewhere. This post sets out what was fixed, why a fix existing is not the same as a server being protected, and how to find out who patches yours.

In short: the fixes are public, but they protect a server only once someone installs them and makes sure the fixed software is the version actually running, so any business that runs its own server or tools needs a named person responsible for that.

What was fixed between 21 October and 18 November

Not every site is affected. A flaw matters only where the software, the version and, sometimes, a particular setting are present. These are the three, in date order.

  • —PHP, 21 October 2026. PHP released 8.2.35, 8.3.36, 8.4.27 and 8.5.12. The US Cybersecurity and Infrastructure Security Agency (CISA) added two PHP flaws, CVE-2026-109618 and CVE-2026-109619, to its Known Exploited Vulnerabilities catalogue on 26 October, describing both as allowing remote code execution without logging in. CISA describes the catalogue as its authoritative list of vulnerabilities that attackers have been seen exploiting. PHP's own changelog lists the fix as "Avoid state corruption via bailout". PHP is a programming language that many websites and web applications run on.
  • —Apache httpd, 11 November 2026. Apache released version 2.4.71 to fix CVE-2026-119618, rated critical, a flaw in its HTTP/2 module that can lead to remote code execution. Apache lists versions 2.4.55 through 2.4.70 as affected. The same release fixed two lesser issues.
  • —nginx, 18 November 2026. nginx released 1.31.9 and 1.30.7, and the 1.31.9 changelog lists ten security fixes. The most discussed, CVE-2026-123007, is in how nginx handles HTTP/2 and affects every release from 1.9.5 to 1.31.8. In its CVE record, F5, which publishes nginx, says the flaw affects configurations that use HTTP/2 and that an attacker could crash a worker process, corrupt its memory or potentially run code remotely, where a memory-protection feature is switched off or can be bypassed. F5 scores it 9.2 out of 10 (critical) on the newer CVSS 4.0 scale and 8.1 (high) on the older 3.1 scale, so the label depends on which scale you read.

These are not only website problems. Several of the open-source tools that small teams run for file sharing, email and chat are web applications written in PHP and served by Apache or nginx, so the same fixes reach them.

On the day we checked (20 November 2026, against the catalogue's update of 18 November), the PHP flaws were in CISA's catalogue and the Apache and nginx flaws were not. That can change quickly, so treat it as a snapshot, not a verdict.

Why a fix existing does not mean your server is protected

A fix passes through three stages: it is released, it is installed, and the fixed software is the one actually running. A server can sit at stage one for a long time without anyone noticing. Three things make stage three harder than it sounds.

  • —Installing is not the same as running. nginx's own documentation treats reloading its configuration and upgrading the running executable as separate operations, and press coverage of the nginx flaw says a reload alone is not enough. How a fixed version gets running depends on how the software was installed, which is something only the person who set the server up is likely to know.
  • —Version numbers can mislead. Linux distributions often apply a fix to the version they shipped without changing the version number the software reports, as Debian's security FAQ explains. A server that reports an older number may already be fixed, and a current-looking number does not show that the fixed software is the one running. Someone who knows the machine has to read it correctly.
  • —PHP is part of the server, not of your website software. The WordPress project explains that your hosting provider determines which PHP versions are available to a site, and that keeping PHP up to date matters as much as updating the site's own software and plugins. Those are separate jobs, and the second is often the one nobody is doing.

There is also a calendar. PHP 8.2 receives security fixes only until 31 December 2026, according to PHP's supported versions page. A server still on 8.2 after that date gets no further fixes from the PHP project, and only keeps getting them if a distribution or host chooses to patch its own packaged version, so "it works" is not the same as "it is looked after".

Who patches the server depends on how it is set up

The honest answer differs by setup, and many small businesses are in one of these four without having chosen it.

  • —A software service you subscribe to (hosted email, a hosted shop, a website builder). The provider patches the platform. Your responsibility is your own accounts and passwords.
  • —Managed hosting. The host usually patches the platform, but terms differ, so ask what exactly is covered. Your own plugins, themes and application code are normally still yours.
  • —A server or cloud machine you rent. The provider supplies the machine, not the updates. Updating the operating system and the software on it is the job of you or whoever you hired. This is also where open-source tools for files, email or chat usually run when a business hosts them itself.
  • —A server a freelancer or employee built. Often nobody, once that person has moved on. This is the most common way a server ends up unmanaged, and we describe how to get a grip on it in Taking over a server nobody documented and The handoff problem.

Three questions to ask whoever runs your server

You do not need to understand the flaws to ask these. A clear answer matters more than a technical one.

  1. —What software handles our website, and was it updated after these releases? Ask for the names and versions of the web server (Apache or nginx) and of PHP, if used, and for the date each was last updated.
  2. —Who installs security updates, how do we know they were applied, and was the fixed software restarted? The answer should name a person or a provider, not "it updates itself" unless they can show how.
  3. —If that person is unavailable, who can step in? Ask where the admin logins and the backups are, and who can reach them.

If nobody can answer the first question, that is useful information, not a failure. It tells you the server has no clear owner.

What ongoing care covers, and what we do

Ongoing care for a server is not a promise that nothing will go wrong. It is a named person doing a short list of things regularly and telling you in plain words what changed:

  • —watching for security releases for the software your server uses, including the web server and PHP;
  • —installing them at a time agreed with you, and confirming the fixed version is the one running;
  • —keeping backups and testing that one can be restored;
  • —reviewing who has access and removing logins that are no longer needed;
  • —keeping simple written notes, so that the knowledge does not live in one head.

This is the work we do. We deploy and maintain open-source tools for small teams, such as file sharing, email, chat and password management, on servers the business owns, and we can look after a server someone else built. If it is not ours yet, we start with a review and a one-page written summary before anything is changed. Care is optional, monthly and quoted separately, so you can see what it covers before agreeing to anything. You keep the server, the accounts and the data, and either of us can end care with 30 days' written notice.

When you probably do not need this

If your site is a few brochure pages on managed hosting, or the tools you use are software services, someone else is already doing most of this and the useful step is the question about what your host covers. If you have an IT person or a provider who answers the three questions clearly, you are in good shape.

What this post does not cover

This is general information, not a security audit. It does not tell you whether your server was affected, and patching does not show whether a server was accessed while it was exposed. CISA's entries for the PHP flaws also reference its forensic triage requirements, so a server that was reachable and unpatched in late October deserves a closer look than an update alone. Facts here are dated 20 November 2026 and will change; we update the post when they do.

If you are not sure who looks after your server, a Free 30-minute review is a place to start: we go through what runs where and who has access, then send a one-page written summary within two business days.

New posts are also available by RSS. Add the address to any feed reader.

We set up and look after open-source tools for small teams, and move you off paid tools gradually and carefully. A free 30-minute review is a good place to start.

See our services

Everything we set up is open-source software. TrySelfHost is independent and not affiliated with or endorsed by any of these projects. We sell setup, migration and care, not the software. Product names belong to their owners.