On this page (7 sections)

On November 18, 2026, the Debian Security Team published DSA-6637-1, a security update for needrestart. The flaw, tracked as CVE-2026-124757, allows a local user to escalate privileges to root.

If you run Debian 13 (trixie) servers, especially shared hosts or machines where several people or applications have shell access, you should update. So far this story rests on a single source, the Debian advisory itself, so some details below are marked as not yet confirmed.

What happened

Debian reports that needrestart, a utility that checks which daemons need a restart after library upgrades, does not properly validate process names and cgroup paths. According to the advisory, a local user can abuse this to gain root privileges. Debian credits Armaan Sandh with the discovery.

The advisory states the fix for the stable distribution (trixie) is version 3.11-1.1~deb13u1 and recommends upgrading the needrestart package.

What the weakness means in plain terms

needrestart typically runs with high privileges, often automatically after package upgrades, and it inspects other processes on the system. Inspecting processes means reading data that other users can influence, such as a process name or the cgroup path a process belongs to. When a privileged tool trusts that data without validating it, an unprivileged user may be able to craft input that makes the tool do something it should not. That is the general class of problem Debian describes here.

The Debian advisory does not give a CVSS score, a technical root cause beyond the missing validation, or any statement about exploitation. We do not know from this source whether the flaw is being exploited, and no public proof of concept is described. Treat severity as unrated until NVD or another scorer publishes one.

Who is realistically exposed

This is a local flaw. An attacker needs to already run code or have a shell account on the machine. It is not described as remotely exploitable. That still matters for many website environments:

  • Shared servers and VPS hosts where several customers or staff have shell or SSH access.
  • Servers running web applications where a separate flaw (for example a vulnerable plugin or upload form) gives an attacker code execution as a low-privilege user. A local root flaw can then turn a limited foothold into full control.
  • CI runners, build hosts and containers-on-host setups where untrusted code runs as a normal user.
  • Single-admin servers with no other users and no untrusted code are lower risk, but patching is still cheap and sensible.

The advisory only names the stable distribution, trixie. It does not list fixed versions for other Debian releases, so check the Debian security tracker for needrestart for the status of the release you run.

How to check if you are affected

This read-only command shows whether needrestart is installed and which version. Run it on each Debian host. If the version is older than 3.11-1.1~deb13u1 on trixie, you need the update.

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

If you manage many hosts, this lists the package version in a compact form. An error or empty output means the package is not installed.

Compact version query (Debian)Shell
dpkg-query -W -f='${Package} ${Version}\n' needrestart

What to do now

Updating is a normal package upgrade. Debian recommends upgrading needrestart; the standard way is through apt.

Caution. Upgrading packages on a production server can trigger service restarts, and needrestart itself exists to prompt for them. Apply updates in a maintenance window where possible and confirm which services will restart.

This command refreshes the package index and upgrades only the needrestart package. Run it as root or with sudo, then re-check the version.

Update only the needrestart package (Debian)Shell
sudo apt update
sudo apt install --only-upgrade needrestart

Afterwards, run the version query again and confirm it reports 3.11-1.1~deb13u1 or newer on trixie.

  1. List your Debian hosts and note which release each one runs.
  2. Run the version check for needrestart on each host.
  3. Update needrestart with apt on trixie systems, preferably in a maintenance window.
  4. Re-run the version check and confirm 3.11-1.1~deb13u1 or newer.
  5. Check the Debian security tracker for the status on other releases you run.
  6. Review who has shell or SSH access and remove accounts that are no longer needed.
  7. Review recent logins and sudo activity on shared hosts for anything unexpected.

Detection and monitoring afterwards

Debian's advisory does not describe indicators of compromise or any exploitation, so there is no specific signature to hunt for. General practice applies: watch authentication logs for unfamiliar local accounts or logins, review changes to privileged files and cron jobs, and keep an eye on unexpected processes running as root. If you suspect an attacker already had local access before you patched, follow a website hacked response plan and consider rotating credentials stored on the host.

To reduce the chance that a small web-app flaw becomes a root compromise, keep applications patched and limit what the web server user can do. The WordPress security checklist covers hardening for WordPress sites, and Webforta Scan can run read-only scans of sites you have verified to help spot outdated or exposed components from the outside. It cannot see local package versions on your server, so the checks above are still required.

Timeline

Known date from the Debian advisory
DateEvent
November 18, 2026Debian publishes DSA-6637-1 with the fix in 3.11-1.1~deb13u1 for trixie

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-1] needrestart security updatelists.debian.org ·
  • Debian
  • needrestart
  • privilege escalation
  • Linux servers
  • patching