CVE-2026-4105 | Systemd: systemd: privilege escalation via improper access control in registermachine d-bus method

A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.

Published: 2026-03-13 Last update: 2026-04-30 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-4105 is rated Low Risk (27.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-4105

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-13 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4105

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 5.9 [email protected]

Weakness enumeration for CVE-2026-4105

OS Trackers for CVE-2026-4105

vendor priority summary link
debian not yet assigned CVE-2026-4105 not yet assigned priority: Debian including 1 source packages (systemd), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-4105
redhat medium — https://access.redhat.com/security/cve/CVE-2026-4105
suse high CVE-2026-4105 severity important: SUSE including 405 source package names (13.2-9.82:aaa_base-84.87+git20240906.742565b-1.1, 13.2-9.82:libsystemd0-254.27-slfo.1.1_4.1, …), 812 product×package rows across 86 product lines (Container suse/ltss/sle12.5/sles12sp5, Container suse/manager/4.3/proxy-httpd, … (86 product lines)): Fixed 568, Known Affected 231, First Fixed 13. https://www.suse.com/security/cve/CVE-2026-4105/
ubuntu medium CVE-2026-4105 medium priority: Ubuntu including 1 source packages (systemd), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): not-affected 7, released 1. https://ubuntu.com/security/CVE-2026-4105

Affected software / configurations for CVE-2026-4105

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-4105

cvelogic Threat Intelligence