apt list --upgradable: how to check for security updates on Ubuntu and Debian
Run sudo apt update, then apt list --upgradable. A line whose source ends in -security (such as noble-security on Ubuntu 24.04 or oldstable-security on Debian 12) is a security update. To see which CVEs it fixes, read its changelog or look the package up in Ubuntu's or Debian's security tracker.
On Ubuntu, also run pro security-status. It counts security fixes that apt doesn't show at all, because they're published in Ubuntu Pro's ESM archives.
How do I list pending updates with apt list --upgradable?
Refresh the package lists, then ask apt which installed packages have a newer version. This is our Ubuntu 24.04 test server:
$ apt list --upgradable
Listing...
distro-info/noble-updates 1.7ubuntu0.1 amd64 [upgradable from: 1.7build1]
python3-distro-info/noble-updates 1.7ubuntu0.1 all [upgradable from: 1.7build1]
Each line reads: package name, then the archive the new version comes from, then the new version, the architecture, and the version you have now. The archive is the part that tells you whether it's a security fix.
- Use two dashes.
apt list upgradablelooks for a package called “upgradable” and prints onlyListing.... - Refresh first. The command reads apt's local lists and doesn't contact the archive. Run
sudo apt updatebefore it, or you're looking at old data.apt updatealso ends with a count, such as2 packages can be upgraded. - No sudo needed. Listing works as any user; we checked with an unprivileged account.
- In scripts, add
2>/dev/null. When its output goes to a pipe,aptprints a warning that its interface isn't stable. To count pending packages, useapt list --upgradable 2>/dev/null | grep -c 'upgradable from'.
The list includes updates that apt won't install yet. Both packages above were phased updates that Ubuntu was still rolling out, and held packages show up here too. Our guide to packages that have been kept back explains both.
Why the login message can show a different number
Ubuntu's login message gets its update count from apt-check, which you can run yourself:
$ /usr/lib/update-notifier/apt-check --human-readable
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
4 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm
It said 0 while apt list showed 2, because it leaves out phased updates. It also mentions 4 security updates that apt list can't see at all. Those come up again under pro security-status below.
Which pending updates are security updates?
Ubuntu and Debian publish updates in separate archives, called pockets on Ubuntu and suites on Debian. Only one of them is for security fixes:
| Archive | Ubuntu 24.04 | Debian 12 | What's in it |
|---|---|---|---|
| Release | noble | bookworm | The release itself. Ubuntu never changes it; Debian refreshes it at each point release |
| Security | noble-security | bookworm-security | Security fixes |
| Updates | noble-updates | bookworm-updates | Bug fixes (Ubuntu also copies security fixes here) |
| Backports | noble-backports | bookworm-backports | Newer software, with no security support guarantee on Ubuntu |
On Ubuntu, the security team publishes each fix to -security and copies it to -updates soon after, so a security update usually lists both. Our server's OpenSSL shows the pattern:
$ apt-cache policy openssl
openssl:
Installed: 3.0.13-0ubuntu3.16
Candidate: 3.0.13-0ubuntu3.16
Version table:
*** 3.0.13-0ubuntu3.16 500
500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages
100 /var/lib/dpkg/status
3.0.13-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
A version that appears only under -updates is a bug fix. To list only pending security updates, filter on the archive name:
apt list --upgradable 2>/dev/null | grep -- -security
On our Ubuntu server this printed nothing, because unattended-upgrades had already installed every security fix. To get real output, we downgraded OpenSSL on a Debian 12 test server to the version in the last point release. The same command then printed:
$ apt list --upgradable 2>/dev/null | grep -- -security
libssl3/oldstable-security 3.0.22-1~deb12u2 amd64 [upgradable from: 3.0.20-1~deb12u2]
openssl/oldstable-security 3.0.22-1~deb12u2 amd64 [upgradable from: 3.0.20-1~deb12u2]
On Debian, apt list shows the suite's current name. Debian 12 became oldstable when Debian 13 was released, so its security suite now shows as oldstable-security, while apt-cache policy still says bookworm-security. The grep matches both. Here's an excerpt from a fresh Debian 12 server before its first update, where security fixes sit next to point-release updates:
apt/oldstable-security 2.6.2 amd64 [upgradable from: 2.6.1]
...
curl/oldstable 7.88.1-10+deb12u15 amd64 [upgradable from: 7.88.1-10+deb12u8]
...
libexpat1/oldstable-security 2.5.0-1+deb12u5 amd64 [upgradable from: 2.5.0-1+deb12u1]
libfreetype6/oldstable,oldstable-security 2.12.1+dfsg-5+deb12u4 amd64 [upgradable from: 2.12.1+dfsg-5+deb12u3]
Don't read curl/oldstable as “no security fix inside”. Debian folds earlier security fixes into each point release, so the security pocket only shows what's newer than the last one. On a server that's far behind, install everything, not just the -security lines.
The ?security pattern in newer apt
apt 2.7.11 and newer (Ubuntu 24.04, Debian 13) add a search pattern: apt list '?upgradable ?security'. Its manual says it matches security updates and versions that “succeed a security update”, so it can list more than the grep does. Debian 12's apt 2.6 rejects it with Unrecognized pattern '?security'.
Which CVEs does a pending update fix?
On Ubuntu: apt changelog and the CVE tracker
apt changelog downloads the changelog of the version apt would install, so you can read it before upgrading. Ubuntu security entries name every CVE. This pulls the CVE IDs from the newest entry:
$ apt changelog openssl 2>/dev/null | sed -n '1,/^ -- /p' | grep -oE 'CVE-[0-9]{4}-[0-9]+' | sort -u
CVE-2026-35189
CVE-2026-54872
CVE-2026-75805
CVE-2026-75806
CVE-2026-77696
CVE-2026-84782
Look any of them up at ubuntu.com/security/ followed by the ID. The page for CVE-2026-35189 shows, per release, whether a package is fixed and in which version (3.0.13-0ubuntu3.16 for OpenSSL on 24.04), plus the Ubuntu Security Notice that announced it, here USN-8847-1. To see every CVE for a package, search the tracker by package at ubuntu.com/security/cves.
The version number doesn't change to the upstream release that fixed the bug. Ubuntu and Debian backport fixes into the version they shipped, so OpenSSL stays at 3.0.13 on Ubuntu 24.04. Scanners that compare upstream versions report these packages as vulnerable. The distribution's tracker is the authority.
With Ubuntu Pro's client you can also ask about one CVE directly: pro fix --dry-run CVE-2026-35189 reports whether the machine is affected and what would fix it, without changing anything. We took this from Ubuntu's documentation and didn't run it on our server.
On Debian: the security tracker and the installed changelog
apt changelog didn't work for a security-only version on our Debian 12 server:
$ apt changelog openssl
Err:1 https://metadata.ftp-master.debian.org openssl 3.0.22-1~deb12u2 Changelog
Changelog unavailable for openssl=3.0.22-1~deb12u2 (404 Not Found)
Use the Debian Security Tracker instead. It's organized by source package, so look up openssl, not libssl3, at security-tracker.debian.org/tracker/source-package/openssl. It shows each CVE's status per Debian release and the DSA or DLA advisory that fixed it. dpkg-query -W -f='${source:Package}\n' libssl3 tells you the source package name. After the upgrade, the changelog is on disk:
$ zcat /usr/share/doc/openssl/changelog.Debian.gz | sed -n '1,4p'
openssl (3.0.22-1~deb12u2) bookworm-security; urgency=high
* Non-maintainer upload by the LTS Team.
* CVE-2026-84782 ("DTLS Retransmits Handshake Messages From a Stale Buffer
“LTS Team” is the clue that Debian 12 is now in Long Term Support. Its fixes still arrive through bookworm-security, so you don't need to change your sources.
On Debian: debsecan
debsecan checks every installed package against the security tracker. Install it without recommended packages. On our Debian 12 server, a plain install also pulled in the exim4 mail server (a recommended package), which then listened on port 25:
sudo apt install --no-install-recommends debsecan
With the OpenSSL update still pending, it found both packages:
$ debsecan --suite bookworm --only-fixed --format packages
libssl3
openssl
$ debsecan --suite bookworm --only-fixed | head -n 3
CVE-2026-35189 libssl3 (fixed)
CVE-2026-54872 libssl3 (fixed)
CVE-2026-54874 libssl3 (fixed)
--only-fixed limits it to problems that an available update fixes, and it printed nothing once the server was up to date. By default the package also sets up a daily report emailed to root, so answer its setup question with that in mind.
What does pro security-status show?
This is Ubuntu only. Canonical's standard security support covers the Main and Restricted repositories. Most of Universe gets guaranteed fixes only through Ubuntu Pro's Expanded Security Maintenance (ESM), which is free for personal use on up to 5 physical machines. pro security-status shows where your packages stand:
$ pro security-status
...
743 packages installed:
722 packages from Ubuntu Main/Restricted repository
21 packages from Ubuntu Universe/Multiverse repository
...
This machine is receiving security patching for Ubuntu Main/Restricted
repository until 2029.
This machine is NOT attached to an Ubuntu Pro subscription.
Ubuntu Pro with 'esm-infra' enabled provides security updates for
Main/Restricted packages until 2034.
Ubuntu Pro with 'esm-apps' enabled provides security updates for
Universe/Multiverse packages until 2034. There are 4 pending security updates.
Those 4 updates are invisible to apt list --upgradable, because the ESM archives aren't enabled until Pro is attached. pro security-status --esm-apps names them:
$ pro security-status --esm-apps
...
Installed packages with an available esm-apps update:
age python3-pip python3-pip-whl python3-wheel
apt upgrade shows the same list as a hint (“Get more security updates through Ubuntu Pro”). apt-get doesn't. For scripts, pro security-status --format json marks each such package pending_attach. Whether to attach Pro is your call. Either way, know that these fixes exist and aren't installed.
How do I install only the security updates?
That's what unattended-upgrades does by default. To see what it would install right now, run sudo unattended-upgrade --dry-run --debug.
By hand, pass the packages from the grep to apt-get install --only-upgrade, after a simulation:
sudo apt-get -s install --only-upgrade libssl3 openssl
sudo apt-get install --only-upgrade libssl3 openssl
apt marks packages you name as manually installed. That rarely matters for libraries like these, but our guide to apt upgrade and full-upgrade explains the side effects.
Is the fix actually running?
An installed fix protects you only once the code using it restarts. After the OpenSSL upgrade on our Debian server, needrestart listed the services still running the old library:
Services to be restarted:
systemctl restart ssh.service
systemctl restart systemd-journald.service
/etc/needrestart/restart.d/systemd-manager
systemctl restart systemd-timesyncd.service
systemctl restart systemd-udevd.service
Restart them, or reboot. For kernel and core library updates, a reboot is the only way, and Ubuntu and Debian flag it in /var/run/reboot-required. Then check that the new kernel is the one running.
How we checked this: Ubuntu 24.04.5 LTS server (apt 2.8.4, ubuntu-pro-client 38) on 14 Nov 2026 (UTC) with read-only commands only, including apt changelog and pro security-status; Debian 12.15 test server (apt 2.6.2) on 14 Nov 2026 (UTC), where we downgraded openssl to create a real pending security update, ran apt changelog and debsecan, then upgraded and removed debsecan again. Ubuntu Pro fix and Debian 13 details come from the official documentation. Anything we didn't run ourselves comes from the official documentation listed under Sources.
Check which CVEs are really open on your server
HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.
FAQ
Why does apt list upgradable show nothing?
Check the two dashes first: apt list upgradable searches for a package named “upgradable” and prints only Listing.... If you typed --upgradable, either the server is fully patched, or the package lists are old and you need sudo apt update. On Ubuntu, fixes from the ESM archives don't appear unless Ubuntu Pro is attached.
Do I need sudo to run apt list --upgradable?
No. It only reads apt's local package lists, and it worked as an unprivileged user on our test server. You do need sudo for apt update, which refreshes those lists.
Why does Ubuntu's login message show fewer updates than apt list --upgradable?
The login message counts only what an upgrade would install now. It leaves out phased updates that Ubuntu hasn't rolled out to your machine yet. On our test server, the message said 0 updates while apt list --upgradable listed 2 phased packages.
Are Ubuntu security updates phased?
No. Ubuntu phases bug-fix updates from -updates, and its documentation says security updates are never phased. A security update is offered to every machine as soon as it's published.
Does Debian have something like pro security-status?
The closest tool is debsecan, which compares your installed packages with the Debian Security Tracker. Debian has no paid tier for security fixes. Debian 12's regular security support ended on July 11, 2026, and Debian LTS now covers it until June 30, 2028. Its fixes still arrive through bookworm-security, as our test showed. Our end-of-life dates guide has the full schedule.
Sources
- apt(8) manual, Ubuntu 24.04: list --upgradeable, update, upgrade
- apt-patterns(7) manual, Debian 13: ?security, ?upgradable, ?archive
- Ubuntu project documentation: the package archive and its pockets
- Ubuntu Security Team FAQ: security and updates pockets, backported fixes
- Ubuntu Server documentation: Package management (Universe security patches through Ubuntu Pro ESM)
- Ubuntu CVE tracker: CVE-2026-35189 (fixed in openssl 3.0.13-0ubuntu3.16 on 24.04)
- Ubuntu Security Notice USN-8847-1: OpenSSL vulnerabilities
- Ubuntu Pro Client documentation: What does security-status do?
- Ubuntu Pro Client documentation: check if a system is affected by a CVE (pro fix --dry-run)
- Debian Security FAQ: backported fixes and the security tracker
- Debian Security Tracker: openssl source package
- debsecan(1) manual, Debian 13
- Debian 12 bookworm release page: full support until July 11, 2026, LTS until June 30, 2028
- Debian Wiki: LTS (Debian 12 support dates)
- Ubuntu Pro: free for personal use on up to 5 physical machines