> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# needrestart root flaw (CVE-2026-124757) hits Debian and Ubuntu; no fixed packages yet
- URL: https://ping2prompt.com/needrestart-root-flaw-cve-2026-124757-debian-ubuntu/
- Published: 2026-11-17T22:26:19.000Z
- Updated: 2026-11-18T17:21:28.000Z
- Description: A local user can gain root through needrestart flaw CVE-2026-124757, using a forged cgroup path and the notify hook. Debian bookworm and Ubuntu 24.04 are confirmed affected. No fixed package version is named yet; check distribution security advisories.
- Author: Ping2Prompt Newsroom
- Tags: Debian, Ubuntu, Vulnerabilities, High, #auto, #short-ping

## needrestart flaw lets a local user reach root

A local user can escalate to root through needrestart, tracked as CVE-2026-124757\. The weak points are the code that works out which user session a process belongs to and the notify hook `400-notify-send`. The researcher tested in a lab, with root as the only target.

No severity score is published, and the exploitation status is unknown (the sources do not say).

## A forged cgroup path makes root run attacker text

needrestart decides which user session a process belongs to by looking for a pattern in the process's cgroup path, and it does not tie that pattern to the start of the path. That lets a local user create a directory with a matching name under their own `user@UID.service` cgroup, so one of their processes is treated as part of root's session.

The notify hook then uses the process name, which the process chooses for itself. On Debian bookworm and Ubuntu 24.04 the hook places that name in a shell command launched through `su`, so a root shell interprets it and runs the attacker's commands. On Debian trixie the hook runs `notify-send` as root with an attacker-chosen `DISPLAY` and message text, but command execution was not reproduced there.

## Debian bookworm, Ubuntu 24.04 and trixie packages in scope

- **Confirmed affected**: Debian bookworm needrestart `3.6-4+deb12u3` and Ubuntu 24.04 needrestart `3.6-7ubuntu4.5`.
- **Partly affected**: Debian trixie needrestart `3.11-1`, where the attacker can pass as root's session and abuse `notify-send`.

Any `apt` or `dpkg` run as root with the stock apt hook starts needrestart afterwards, which fires the vulnerable path. The tests used `apt-get`; `unattended-upgrades` was not tested. Upstream notes the hook runs whenever needrestart runs, so systems that call it from automation or monitoring can be affected too. The author did not check other distributions' packages.

## No fixed packages yet: watch Debian and Ubuntu advisories

No fixed package version has been named for any distribution, so the table below is empty. Check your distribution's security advisories for updated packages; no other workaround is given. Upstream has a three-patch series, which it will add to its git repository at disclosure:

- It passes the notification text to the hook through environment variables.
- It anchors the systemd cgroup matches.
- It replaces non-printable characters in the notification text.

The series applies with offsets on needrestart 3.11, but on 3.6 the second patch needs a backport.

## How the disclosure unfolded

Armaan Sandhu found and reported the issue, Red Hat assigned the CVE, and upstream maintainer Thomas Liske reviewed the fix. It went to upstream on 2026-10-23, to the Debian and Ubuntu security teams on 2026-11-05, and to linux-distros on 2026-11-08\. Public disclosure was agreed for 2026-11-17, and the write-up went out that day.

## Sources

- [seclists.org/oss-sec/2026/q4/753](https://seclists.org/oss-sec/2026/q4/753?ref=ping2prompt.com)

Image: [Image by joffi from Pixabay](https://pixabay.com/photos/hacking-hacker-computer-internet-1685092/?ref=ping2prompt.com)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).