On this page (6 sections)

On November 19, 2026, the Debian Security Team published DSA-6637-2, a follow-up to an earlier needrestart update. According to the Debian security announcement, the update announced as DSA 6637-1 introduced a regression, and a corrected package is now available for Debian stable (trixie).

If you run Debian 13 servers or workstations with needrestart installed, Debian recommends upgrading to the corrected package. The advisory is brief, so this article sticks to what it states and marks anything else as an assumption.

What happened

Debian's advisory is short. It says the update announced as DSA 6637-1 introduced a regression due to an incorrect backport when using notify-send to notify a user session via dbus. Debian then published updated packages to correct the issue and recommends upgrading needrestart.

The advisory does not list a CVE identifier, a severity rating or any exploitation information, and it does not describe the regression beyond that one sentence. It also does not say what DSA-6637-1 originally fixed. Only the Debian announcement covers this story so far, so treat anything beyond it as unconfirmed.

What the regression is, in plain terms

needrestart is a tool that checks which running services and sessions are using outdated libraries after an upgrade and can prompt for or trigger restarts. When it needs to tell a logged-in desktop user something, it can send a desktop notification using notify-send over dbus.

Debian says the backported change for that notification path was done incorrectly in DSA-6637-1. In general terms, a regression means something that worked before an update behaves differently afterwards. The advisory does not say whether the problem shows up as errors, missing notifications or something else, so we cannot say what you would observe on your own machines.

This is a correction to a previous update, not a newly described vulnerability. The advisory gives no CVE or severity for it. Its purpose is to deliver a corrected package.

Who is affected

The advisory names only the stable distribution, Debian 13 (trixie), with fixed version 3.11-1.1~deb13u2. It does not say which installed versions are affected or how systems received the faulty package. The practical reading is simple:

  • Debian 13 (trixie) hosts with needrestart installed should be upgraded to 3.11-1.1~deb13u2 or newer.
  • Assumption, not stated by Debian: because the regression concerns notify-send over dbus, systems where needrestart notifies a logged-in user session, such as desktops or shared workstations, are the most likely to notice it.
  • For other Debian releases or other distributions, check the Debian security tracker for needrestart rather than assuming a status.

How to check your exposure

This read-only command prints the installed needrestart version. You are looking for 3.11-1.1~deb13u2 or newer on trixie.

Show the installed needrestart version (Debian 13)Shell
dpkg -s needrestart | grep -E '^(Package|Version|Status)'

This command shows the installed version and the candidate version apt would install from your configured repositories, so you can confirm the fixed package is visible to your system.

Show installed and candidate versions (Debian 13)Shell
apt-cache policy needrestart

What to do now

  1. Run the version check above on every Debian 13 host that has needrestart installed.
  2. Refresh package lists and upgrade needrestart to 3.11-1.1~deb13u2 or newer.
  3. Confirm the new version with dpkg after the upgrade.
  4. If you manage many servers, push the update through your normal patch tooling and verify the result on a sample first.
  5. Review the Debian security tracker page for needrestart for the latest status on your release.

These commands refresh the package index and upgrade only the needrestart package. Run them as root or with sudo.

Update only needrestart (Debian 13)Shell
sudo apt update
sudo apt install --only-upgrade needrestart
Tip. On production servers, apply the update during your usual maintenance window and test it on a staging host first, as you would any package update. Since this release exists to fix a faulty backport, a quick check after installing is worthwhile.

Monitoring afterwards

Subscribe to the debian-security-announce mailing list or your distribution's equivalent so follow-up advisories reach you directly. For a fleet, keep an inventory of package versions so you can answer quickly which hosts still run an older needrestart build.

For the websites and services running on those servers, outside-in checks complement patching. Certificate, DNS and uptime changes are the kind of thing Webforta Monitor watches, and our website security for small business guide covers broader basics. Neither replaces keeping operating system packages current.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6637-2] needrestart regression updatelists.debian.org ·
  • Debian
  • needrestart
  • DSA
  • Linux
  • patching