Systemd vulnerabilities
Published CVEs affecting Systemd products: 7 record(s), with severity, exploitation and fixes.
CVE-2026-40228
Low · 3.3
CWE-669 Apr 10, 2026
Incorrect Resource Transfer Between Spheres in Systemd Project Systemd
In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.
CVE-2026-40227
Medium · 5.5
CWE-1025 Apr 10, 2026
In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC…
In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC API call with an array or map that has a null element.
CVE-2026-40226
Medium · 6.4
CWE-348 Apr 10, 2026
In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via…
In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.
CVE-2026-40225
Medium · 6.4
CWE-669 Apr 10, 2026
Incorrect Resource Transfer Between Spheres in Systemd Project Systemd
In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.
CVE-2026-40224
High · 7.3
CWE-863 Apr 10, 2026
Incorrect Authorization in Systemd Project Systemd
In systemd 259 before 260, there is local privilege escalation in systemd-machined because varlink can be used to reach the root namespace.
CVE-2026-40223
Medium · 5.5
CWE-696 Apr 10, 2026
In systemd 258 before 260, a local unprivileged user can trigger an assert when a…
In systemd 258 before 260, a local unprivileged user can trigger an assert when a Delegate=yes and User=<unset> unit exists and is running.
CVE-2026-29111
Medium · 5.5
CWE-269 Mar 23, 2026
systemd: Local unprivileged user can trigger an assert
systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.