Ubuntu 26.04 vs 24.04 is a choice between two supported LTS stacks: 26.04 ships Linux 7.0, PHP 8.5, MySQL 8.4 and PostgreSQL 18 with free security updates until 2031, while 24.04 keeps Linux 6.8, PHP 8.3, MySQL 8.0 and PostgreSQL 16 until 2029.
Both are long-term support releases, so neither is a wrong pick in 2026. The difference is what changes under your applications. Raff runs 15,000+ VMs for 3,000+ customers and offers both images, so on 2026-11-19 we installed each one fresh on the same 2 vCPU / 4 GB server and measured boot time, memory, disk use, default services and the settings that break existing setups.
The 26.04.1 point release arrived on August 27, 2026, and Ubuntu has offered 24.04 servers the move since September 29, which is when most teams start asking whether to take it. This guide compares the two releases for servers, gives a decision framework, and shows what we measured. It is part of the VPS Setup Checklist series on preparing a new server.
Ubuntu 26.04 vs 24.04 at a Glance
The versions below come from each release's own archive, read on fresh Raff servers on 2026-11-19.
| Component | Ubuntu 24.04 LTS | Ubuntu 26.04 LTS |
|---|---|---|
| Free security updates until | 2029 | 2031 |
| Linux kernel | 6.8 | 7.0 |
| systemd | 255 | 259 |
| sudo | sudo 1.9.15 | sudo-rs 0.2 (Rust) |
Core utilities (ls, cat, sort) | GNU coreutils 9.4 | uutils (Rust); cp, mv, rm stay GNU |
| Time sync | systemd-timesyncd | chrony with NTS |
| OpenSSH | 9.6p1 | 10.2p1 |
| OpenSSL | 3.0.13 | 3.5.5 |
| Python | 3.12 | 3.14 |
| PHP | 8.3 | 8.5 |
| Nginx | 1.24 | 1.28 |
| MySQL | 8.0 | 8.4 LTS |
| PostgreSQL | 16 | 18 |
| Valkey | 7.2 | 9.0 |
| Node.js | 18 | 22 |
| MariaDB | 10.11 | 11.8 |
| Redis | 7.0 | 8.0 |
| HAProxy | 2.8 | 3.2 |
| OpenJDK (default) | 21 | 25 |
| Go | 1.22 | 1.26 |
| APT | 2.8 | 3.2 |
Nearly every component changes, several by a major version or a full replacement, so moving a server between the two is a software migration, not a routine patch.
Changes That Affect a Running Server
Most new versions are drop-in replacements. These are the ones that changed behavior on our test servers, or that Canonical's release notes flag as breaking.

sudo and the core utilities are rewritten in Rust
On 26.04, sudo is sudo-rs, and commands such as ls, cat and sort come from uutils, both rewritten in Rust. Scripts that use common options keep working, while scripts that depend on rare GNU options or exact error text can fail. The original tools stay installed: sudo.ws runs the classic sudo, and each GNU utility is available with a gnu prefix, for example gnuls. Our server upgraded from 24.04 also switched to sudo-rs and uutils, so this is not only a fresh-install change.
Time sync moves to chrony with NTS
New 26.04 installs use chrony with Network Time Security, which authenticates the time servers instead of trusting plain NTP. Our fresh 26.04 server ran chrony against Ubuntu's NTS pools out of the box. A server upgraded from 24.04 keeps systemd-timesyncd until you install chrony, so two servers on the same release can keep time differently.
/tmp lives in memory
systemd now mounts /tmp as tmpfs, so files there use RAM and disappear at reboot. On our 4 GB server the limit was 2 GB, half the memory. An application that writes large temporary files to /tmp, such as database dumps or image processing, can now run a small server out of memory instead of filling the disk.
cgroup v1 and System V scripts are on the way out
systemd 259 removed cgroup v1, so older container runtimes, Java versions and monitoring agents that only understand cgroup v1 can stop working. 26.04 is also the last Ubuntu release that runs System V init scripts, so anything still started from /etc/init.d should get a systemd unit before the next LTS.
OpenSSH 10 drops DSA and leads with post-quantum key exchange
OpenSSH 10.2 removes DSA keys entirely and puts the hybrid post-quantum key exchange mlkem768x25519-sha256 first. Our fresh 26.04 server offered it as its first choice, while 24.04 offered sntrup761x25519-sha512. RSA and Ed25519 keys work as before; very old SSH clients and DSA keys are the risk.
APT 3 removes apt-key
apt-key does not exist on 26.04. Install instructions that still pipe a key into apt-key add fail, and the current method stores the key in /etc/apt/keyrings and points to it with Signed-By. Most vendors already document the new method, and Docker lists Ubuntu 26.04 as a supported release.
PHP 8.5 and MySQL 8.4 change paths and logins
PHP 8.5 replaces PHP 8.3, so the PHP-FPM socket moves from php8.3-fpm.sock to php8.5-fpm.sock. On our upgraded test server, an Nginx site that pointed at the old socket returned 502 Bad Gateway until we changed it. MySQL 8.4 locks accounts that still use the mysql_native_password plugin, and Canonical's notes give two ways out: move those accounts to caching_sha2_password, or switch the old plugin back on in mysqld.cnf. The step-by-step upgrade tutorial with a snapshot rollback shows these fixes on a real server.
Choosing Between Ubuntu 24.04 and 26.04 for a Server
A server installed on 26.04 gets free security updates until 2031, two years longer than the same server on 24.04, whose standard support ends in 2029. That gap is the strongest reason to pick 26.04 for new work, and the release notes are the strongest reason to test before moving existing work.
Choose Ubuntu 26.04 if:
- You are building a new server and your software supports 26.04.
- You want PHP 8.5, PostgreSQL 18, MySQL 8.4 or Python 3.14 from the Ubuntu archive instead of third-party repositories.
- You want the longest free support window: until 2031.
- You want post-quantum SSH key exchange and authenticated time sync without extra setup.
Stay on Ubuntu 24.04 if:
- You need CIS or DISA-STIG hardening profiles today. Canonical lists both as achieved for 24.04 and as planned for 26.04.
- A vendor has not certified 26.04 yet, for example a control panel, a commercial agent, or a container tool that still needs cgroup v1.
- Your applications use MySQL accounts with
mysql_native_passwordor PHP code not yet tested on PHP 8.5. - The server is stable and you have no time to test this quarter, since 24.04 keeps free updates until 2029.
| Situation | Recommendation | Why |
|---|---|---|
| New server, current stack | 26.04 | Two more years of free updates and current packages |
| New server for vendor-certified software | The release the vendor certifies | Support contracts follow certification |
| Existing 24.04 server that works | Stay, and plan the move before 2029 | No security deadline until 2029 |
| Existing server with PHP or MySQL apps | Test on a copy first | Socket path and login changes break apps quietly |
| CIS or DISA-STIG compliance | 24.04 for now | 26.04 profiles are still planned |
| Container hosts and Kubernetes nodes | 26.04 if every runtime supports cgroup v2 | cgroup v1 is gone |

