Our server runs Ubuntu 26.04 LTS, and we patch it with a command we trust. On November 17, 2026 we attached the machine to Ubuntu Pro, which is free, and ran that command's check. It listed 25 host upgrades. Twenty-one of them came from a package source that had not existed on the machine ten minutes earlier.
They were not obscure. ffmpeg, ImageMagick, rclone, restic, the GitHub CLI and a JavaScript library called lodash: the tools we use to convert media and run backups. The ffmpeg version on offer ended in +esm5 and ImageMagick's in ~esm4, which reads as five and four rounds of security fixes that had been published since April and never offered to us.
Nothing was misconfigured. This is how an Ubuntu LTS release works by default, and most people running one have not been told. The fix took a free account, three commands and a six-letter code typed into a browser.
Download the Ubuntu Pro ESM Setup Kit in Markdown. It's the whole procedure as one file: the read-only checks, the attach step, what to enable, how to prove it worked, a small script that warns you if the machine ever drops off, and a prompt you can hand to an AI coding agent along with the file so it does the typing while you do the one step that needs a person.
What "LTS" promises, and what it leaves out
Ubuntu sorts its packages into repositories. Two matter here.
Main is the core: the kernel, OpenSSH, systemd, Python, the things Canonical builds the operating system from. Canonical's documentation says main holds about 2,300 packages per release and that it committed "to security-support these packages and their dependencies in 'main' for five years, free of charge." That is the promise people mean when they say LTS.
Universe is everything else, pulled in from Debian and the Ubuntu community. Canonical's ESM page counts over 36,000 packages there as of Ubuntu 24.04. Here is the sentence from the same documentation that most LTS users have never read:
Historically those packages came with no security maintenance commitment from Canonical. Nevertheless, Canonical and the Ubuntu community provided best-effort maintenance for those packages.
Best effort means some fixes arrive and some don't, and nobody owes you either. Universe is where a working server's tools live. One command shows the split on any machine:
$ pro security-status
1568 packages installed:
1030 packages from Ubuntu Main/Restricted repository
511 packages from Ubuntu Universe/Multiverse repository
8 packages from third parties
19 packages no longer available for download
So 511 of our 1,568 packages, just under a third, sat outside the promise. On our server that third includes ffmpeg and its codec libraries, ImageMagick, rclone, restic, 7zip, exiftool, eslint, a GCC 13 toolchain and a few hundred Node.js modules.
Ubuntu Pro closes the gap with a service called Expanded Security Maintenance, ESM, delivered as two extra package sources:
Scroll to compare columns and rows when the table extends beyond the box.
| Source | Covers | When it matters |
|---|---|---|
esm-apps |
Universe and multiverse, for ten years from the LTS release | From day one |
esm-infra |
Main and restricted, for five more years after the free five end | From year six |
The commitment is to fix "critical, high and selected medium vulnerabilities across the whole Ubuntu archive." That is why a seven-month-old release already had 21 fixes waiting on our machine, all from esm-apps, and none from esm-infra, which has nothing to add until 2031.
The dates for your release
From Canonical's release cycle page, read November 17, 2026:
Scroll to compare columns and rows when the table extends beyond the box.
| Release | Free security fixes for main end | With Ubuntu Pro | With the paid Legacy add-on |
|---|---|---|---|
| 26.04 LTS | May 2031 | May 2036 | May 2041 |
| 24.04 LTS | May 2029 | May 2034 | May 2039 |
| 22.04 LTS | May 2027 | May 2032 | May 2037 |
| 20.04 LTS | ended May 2025 | May 2030 | May 2035 |
| 18.04 LTS | ended May 2023 | May 2028 | May 2033 |
Two rows deserve a second look. If you still run 20.04 and never attached it, the machine has received no security fixes of any kind for eighteen months. And 22.04, which a lot of small-business servers were built on, loses its free fixes in about six months.
Interim releases, the ones without LTS in the name, get "only 9 months of updates" and no ESM. Don't run a server on one.
What it costs
For one person and a few machines, nothing. Canonical's product page says: "Ubuntu Pro is and always will be free for personal use on up to 5 physical machines, or 50 machines for official Ubuntu Community members." The client documentation adds that the five are physical machines "with unlimited VMs on these machines."
There is one wrinkle a business owner should know about. The January 2023 launch announcement described the free tier as "for personal and small-scale commercial use in up to 5 machines." The current product page says personal use and does not repeat the commercial part. We are not lawyers and won't tell you which sentence governs your company's file server. If the machine earns money for a business, read the current terms, or pay: the list price is $25 a year for a workstation and $500 a year for a server with unlimited virtual machines. Against one afternoon of cleaning up after an unpatched image library, either price is small.
The setup, start to finish
You need an Ubuntu One account, which is free, and a shell on the machine. The client is already installed on current Ubuntu releases.
Before:
$ pro status
SERVICE AVAILABLE DESCRIPTION
esm-apps yes Expanded Security Maintenance for Applications
esm-infra yes Expanded Security Maintenance for Infrastructure
livepatch yes Canonical Livepatch service
This machine is not attached to an Ubuntu Pro subscription.
Attach. With no token on the command line, the client uses a sign-in code instead:
$ sudo pro attach --no-auto-enable
Initiating attach operation...
Please sign in to your Ubuntu Pro account at this link:
https://ubuntu.com/pro/attach
And provide the following code: ABC123
You open that page on any device, sign in, type the code and leave "Free Personal Token" selected. The first sign-in asks permission to share your Ubuntu One email, username and full name with ubuntu.com. A few seconds later the terminal carries on by itself:
Attaching the machine...
This machine is now attached to 'Ubuntu Pro - free personal subscription'
We like this route because no secret ever touches the server. The other route is a token from your dashboard, and Canonical's documentation says to treat those "as a secret (as you would with a password)." A token pasted on a command line ends up in shell history.
Then turn on the two sources:
$ sudo pro enable esm-infra esm-apps --assume-yes
Configuring APT access to Ubuntu Pro: ESM Apps
Updating Ubuntu Pro: ESM Apps package lists
Ubuntu Pro: ESM Apps enabled
Configuring APT access to Ubuntu Pro: ESM Infra
Updating Ubuntu Pro: ESM Infra package lists
Ubuntu Pro: ESM Infra enabled
Our subscription record shows it took effect at 23:50:07 UTC, and both sources were live a minute later.
Why --no-auto-enable, and whether you want it
A plain sudo pro attach turns on the recommended services for you. Canonical's documentation lists ESM as "enabled by default" and Livepatch as "one of the services we enable by default." Livepatch patches high and critical kernel flaws in the running kernel so a reboot can wait for a planned window.
For most small servers, the plain command is the right one. A machine that nobody reboots on a schedule is better off with Livepatch than without it.
We passed --no-auto-enable and enabled only ESM because our server already has a guarded reboot routine that checks what is running, saves it, reboots and verifies. We wanted one mechanism responsible for the kernel, not two. Canonical is plain that Livepatch "is not a replacement for rebooting," so the reboot routine has to exist either way.
Update, November 18, 2026. One day after publishing this we turned Livepatch on. Reboots of this server are rare and take other workloads down with them, and we first confirmed that our reboot routine ignores Livepatch and still asks for a reboot when a new kernel package lands. The reasoning and the trade-off it brings are in the follow-up.
The trap when a script or an agent runs it
We had an AI coding agent type the commands while one of us handled the browser. The first attempt printed nothing at all. Thirteen seconds in, the log file was empty and the process was sitting there.
The client is a Python program. When its output goes to a file or a pipe instead of a terminal, Python holds the text in a buffer until the program exits. This program does not exit until you enter the code, and the code is in the buffer. Each side waits for the other.
The fix is one environment variable:
sudo env PYTHONUNBUFFERED=1 pro attach --no-auto-enable > attach.log 2>&1 &
sleep 10; cat attach.log
If you attach from a terminal by hand you will never see this. If you automate it, you will see it on the first try.
What changed on the machine
Three things, all written by the client:
- Two apt source files,
/etc/apt/sources.list.d/ubuntu-esm-apps.sourcesandubuntu-esm-infra.sources, pointing atesm.ubuntu.com. - Credentials for those sources in
/etc/apt/auth.conf.d/90ubuntu-advantage, readable by root only. - A pin.
/etc/apt/preferences.d/ubuntu-pro-esm-appsgives ESM packages priority 510, a notch above apt's default of 500.
The pin is the thoughtful part. Canonical's explanation is that it "guarantees that no automatically installed updates will ever revert a previously applied security patch." You can watch it work:
$ apt-cache policy ffmpeg
ffmpeg:
Installed: 7:8.0.1-3ubuntu2
Candidate: 7:8.0.1-3ubuntu2+esm5
Version table:
7:8.0.1-3ubuntu2+esm5 510
510 https://esm.ubuntu.com/apps/ubuntu resolute-apps-security/main amd64 Packages
*** 7:8.0.1-3ubuntu2 500
500 http://nova.clouds.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
100 /var/lib/dpkg/status
Same upstream version, 8.0.1. The ESM build carries the security patches. Nothing else about your ffmpeg changes.
The client also checks in. A metering job tells Canonical which services are enabled every four hours, and a second job refreshes the login and apt messages every six. pro config show prints both timers. We mention it because a subscription that phones home should say so, and this one does.
Getting the fixes installed
Enabling ESM makes the fixes available. Something still has to install them.
If the machine uses unattended-upgrades, check that it knows about the new sources. On our 26.04 server the stock configuration already listed both, and a dry run confirmed it:
$ sudo unattended-upgrade --dry-run -d 2>&1 | grep "Allowed origins"
Allowed origins are: o=Ubuntu,a=resolute, o=Ubuntu,a=resolute-security,
o=UbuntuESMApps,a=resolute-apps-security, o=UbuntuESM,a=resolute-infra-security
If yours does not, the kit has the two lines to add. If you patch by hand, sudo apt-get update && sudo apt-get upgrade picks the ESM builds up like any other update.
We patch with one update command that saves the old package, installs the new one, checks the result and rolls back on failure. ESM builds are ordinary apt candidates, so that step needed no change at all. It still applies the rule from that post: a library a running service has loaded stays old in memory until the service restarts, so installing is not the end of the job.
The failure nobody reports
Here is what bothered us once it was working. Before today, nothing on the server said "a third of your packages have no security commitment." After today, nothing would say "you have been detached."
A fresh reinstall is not attached. Neither is a restore from an image taken last month. A paid subscription that lapses stops delivering. In every case the machine keeps running, apt keeps reporting that everything is up to date, and the fixes stop. The only signal is a line in pro status that you see if you think to look.
So we added the question to the places we already look. Our update command gained a row in its survey, a row in its health check and a report of its own:
$ update pro
Ubuntu Pro (ESM) at 2026-11-18T00:01:03Z:
OK subscription Ubuntu Pro - free personal subscription, no end date
OK esm-infra enabled
OK esm-apps enabled
21 ESM security fixes waiting; `update run apt` applies them (unattended-upgrades also does):
- ffmpeg 7:8.0.1-3ubuntu2 -> 7:8.0.1-3ubuntu2+esm5 (esm-apps)
- gh 2.46.0-4 -> 2.46.0-4ubuntu0.26.04.1~esm1 (esm-apps)
- imagemagick 8:7.1.2.18+dfsg1-1 -> 8:7.1.2.18+dfsg1-1ubuntu0.1~esm4 (esm-apps)
(18 more lines)
Three decisions in that small change are worth copying:
- It warns and never fails. The server runs fine without ESM. It only goes unpatched. A warning in the daily health check is the right weight.
- It prints no identity. The status data includes the account name, a contract id and a machine id. The report keeps the subscription name, the end date and the service states, and drops the rest, because these reports end up in logs and build summaries.
- The remote path is read-only. We can run the report from a GitHub Actions workflow whose SSH key is locked to a short list of commands. That list admits the report and refuses
pro attach,pro detachandpro enable. A workflow should be able to tell you the subscription fell off. It should not be able to change it.
You don't need our tool for this. The kit includes a short shell script, pro-esm-check, that exits 1 with a reason when the machine is detached, a source is off or the subscription ends within 30 days, plus a systemd timer to run it daily. We tested it against an attached machine, a detached one, one with a source disabled and one returning garbage.
What ESM does not cover
It is easy to read "security fixes for the whole archive" as "the server is covered." It isn't, and the gaps are specific:
- Anything inside a container. An image carries its own packages. Attaching the host does nothing for them. Rebuild images on a patched base, or attach during the build using a secret, which Canonical documents.
- Third-party apt sources. Eight of our packages come from outside Ubuntu, Docker's own repository and Tailscale among them. Their publishers patch those.
- Anything installed by pip, npm, cargo, snap or a download. Each has its own update path, and its own risks, which is what our check for poisoned releases is for.
- The running kernel until you reboot, unless Livepatch is on, and then only for high and critical flaws.
- Every vulnerability. The commitment covers critical, high and selected medium severity.
Handing the job to an AI agent
The kit is written so a person can follow it or an agent can. That second use is why it opens with a section of rules that nothing later in the file may override. The ones that matter most:
- The first two sections are read-only. The agent shows you the release, the attach state and the package counts, then stops.
- It never asks for, reads or stores a token. It uses the sign-in code and waits while you enter it.
- It enables only the services you chose. It may not turn on FIPS, which swaps out system cryptography and is very hard to take back, however helpful that might seem to it in the moment.
- It never reboots and never prints the account name or machine id.
The last section of the kit is a prompt to paste into the agent's session. The agent runs the checks, recommends a path, starts the attach, gives you the code, lists the pending fixes and waits again before installing anything. Then it installs the check script and fills in a record sheet with the date, the path you took and where the alert goes.
The division of labor is the point. The agent is fast and exact at the typing and the verifying. The decision to bind a machine to your account, and the act of signing in, stay with you.
Should you do this today?
If you run Ubuntu LTS on a server, a workstation or a home machine: yes. Run pro security-status first. It changes nothing, takes two seconds and tells you how many of your packages sit outside the promise. On ours it was 511.
Then spend the ten minutes, with the kit open beside you or handed to your agent. It is the cheapest security improvement we have made this year, and the only one that came with a list of the exact fixes we had been missing.
Fact-check notes and sources
- Our records: attach, enable and check output from our own server on November 17, 2026 (UTC), Ubuntu 26.04.1 LTS, Pro client 38. Subscription effective 23:50:07. 1,568 packages installed: 1,030 main/restricted, 511 universe/multiverse, 8 third party, 19 no longer available.
apt list --upgradableand the client's update API both counted 21 packages from the ESM apps source;pro security-statusprinted 20. The 21 are builds of nine source packages (ffmpeg, ImageMagick, gh, libass, srt, node-lodash, node-shell-quote, rclone, restic). Pin priority, source files, timers and the unattended-upgrades origins were read from the machine. - Main and universe, the "no security maintenance commitment" passage, the two ESM streams and the 510 pin: Canonical, About ESM, esm-apps and esm-infra, page dated April 24, 2026.
- Universe package count: Canonical, Expanded Security Maintenance, "over 36,000 packages per release (as of Ubuntu 24.04 LTS)". The client documentation above and the 2023 launch post still say 23,000.
- Severity commitment and the free personal tier: Canonical, Ubuntu Pro, read November 17, 2026.
- Release dates: Canonical, The Ubuntu lifecycle and release cadence, read November 17, 2026. Interim releases: "only 9 months of updates".
- Five physical machines with unlimited VMs, tokens as secrets, the 24-hour active count: Canonical, Machine counts and token usage for Ubuntu Pro.
- "Personal and small-scale commercial use": Canonical, Ubuntu Pro enters general availability, January 26, 2023.
- List prices: Canonical, Ubuntu Pro pricing, read November 17, 2026. Workstation $25 and server with unlimited VMs $500, each per machine per year.
- Attach by sign-in code, the Free Personal Token default and
--no-auto-enable: Canonical, How to attach. Token file format: How to attach with a configuration file. - Default services: Canonical, Which services are for me?.
- Livepatch scope and "not a replacement for rebooting": Canonical, Livepatch, read November 17, 2026.
- Metering every four hours, messaging every six: Canonical, Timer jobs explained.
- Containers: Canonical, How to enable Ubuntu Pro Services in a Dockerfile.
- Reinstalls, clones and deleted machines: Canonical, How to manage Ubuntu Pro attachment when moving machines, page dated July 8, 2026.
- Disable, detach and purge: Canonical, Disabling and purging services.
Related reading
- We Surveyed Our Server for 8 Hardening Gaps: what we checked next, what we changed, and why Livepatch is now on.
- Hardening a One-Admin Linux Server: the general method, with a kit to download.
- Updated on Disk, Old in Memory: the update command this check now lives in, and why installing a fix is not the same as running it.
- LiteLLM 1.107.0 Ran When Python Started: the check we run before any update, for the packages ESM does not cover.
- Hackers Now Automate Attacks on 200 Orgs: why the time between a fix and an exploit keeps shrinking.
- Node.js Fixed the Brotli Flaw on October 21: another case of a fix that existed and had not reached us.
- Build a Self-Hosted AI Server From Scratch: the server this runs on, layer by layer.
This post is informational, not security-consulting or legal advice. Read Canonical's current terms before relying on the free tier for business use, and test any change on your own systems. Mentions of Ubuntu, Canonical, Docker, Tailscale, GitHub, FFmpeg, ImageMagick and Node.js are nominative fair use. No affiliation is implied.