Keeping server software patched: web, database, mail and more

Updated November 2026

Most break-ins do not start with the operating system but with the software on top of it: the web server, PHP, a database left open to the internet, an old control panel or plugin. Each page shows how to check your version, which versions are still supported, and how to update safely.

Where to start

  1. Make a list of what runs on your server. sudo ss -tulpn shows every program that listens on the network; those are the ones attackers can reach first.
  2. Check each one against its supported versions. Each page below has a table. A version that no longer receives fixes is the biggest risk, whatever else you do.
  3. Prefer your distribution's packages. They receive security fixes through the normal system update, often as backported fixes with the same version number. Use the project's own repository only when you need a newer version, and then keep that repository updated too.
  4. Restart after updating. A library or service update is not active until the program restarts. See what to restart.
  5. Keep databases, panels and admin tools off the internet. Most mass attacks find them with simple scans.

Also see Updating PHP, Updating Node.js, Patching nginx, Apache and OpenSSL and the live list of vulnerabilities that need patching now.

All software guides