Quick answers
- Is CVE-2026-4105 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-4105 being exploited in the wild.
- How severe is CVE-2026-4105?
- Medium severity, with a CVSS score of 6.7, published 13 March 2026.
- Which products and versions are affected?
- systemd systemd.
- Is there a fix for CVE-2026-4105?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-4105 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-4105?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper access control flaw in the systemd-machined service's RegisterMachine D-Bus method, caused by insufficient validation of the class parameter. A local unprivileged user can exploit this by providing a crafted class value when registering a machine, resulting in a usable attacker-controlled machine object being left in place. By invoking methods on this privileged object, the attacker can execute arbitrary commands with root privileges. The attack requires local access and does not require authentication beyond standard D-Bus access, allowing privilege escalation from unprivileged to root.
Affected products
- systemd systemd
Timeline
- 2026-03-13: disclosed