# CVE-2026-29111: systemd: Local unprivileged user can trigger an assert > A local unprivileged user can trigger an assertion failure in systemd, causing the system to freeze and resulting in a denial of service. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Mar 2026 - **Updated:** 25 Mar 2026 - **Also known as:** ALSA-2026:13651, ALSA-2026:13677, ALSA-2026:19068, ALSA-2026:19213, AZL-80538, AZL-80937, CLSA-2026-1777482797, CLSA-2026-1779217317, CLSA-2026-1784813417, CLSA-2026-1784813597, CLSA-2026-1784813658, CLSA-2026-1787401254, DEBIAN-CVE-2026-29111, ECHO-bf64-f9b5-3e12, GHSA-gx6q-6f99-m764, OESA-2026-2122, OESA-2026-2123, RHSA-2026:13651, RHSA-2026:13677, RHSA-2026:19068, RHSA-2026:19213, RHSA-2026:25900, RHSA-2026:49910, RHSA-2026:50050, RHSA-2026:50051, RHSA-2026:50077, RHSA-2026:51134, RHSA-2026:51277, RLSA-2026:13651, RLSA-2026:13677, RLSA-2026:19068, RLSA-2026:19213 ## What is CVE-2026-29111? CVE-2026-29111 is a medium-severity denial of service vulnerability in Systemd Project Systemd, published on 23 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-269 (Improper Privilege Management) ## Which versions are affected by CVE-2026-29111? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `systemd` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-boot-unsigned` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-container` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-devel` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-journal-remote` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-libs` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-oomd` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-pam` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-resolved` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-rpm-macros` | AlmaLinux:10 | All versions | 257-13.el10_1.3.alma.1 | | `systemd-rpm-macros` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-udev` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `systemd-ukify` | AlmaLinux:10 | All versions | 257-13.el10_1.3.alma.1 | | `systemd-ukify` | AlmaLinux:10 | All versions | 257-23.el10_2.1.alma.1 | | `rhel-net-naming-sysattrs` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `rhel-net-naming-sysattrs` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-boot-unsigned` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-boot-unsigned` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-container` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-container` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-devel` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-devel` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-journal-remote` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-journal-remote` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-libs` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-libs` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-oomd` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-oomd` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-pam` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-pam` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-resolved` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-resolved` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-rpm-macros` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-rpm-macros` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-udev` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-udev` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | | `systemd-ukify` | AlmaLinux:9 | All versions | 252-55.el9_7.9.alma.1 | | `systemd-ukify` | AlmaLinux:9 | All versions | 252-67.el9_8.2.alma.1 | Products: Systemd Project Systemd. ## How do I fix CVE-2026-29111? Apply the vendor's patch. ## Is CVE-2026-29111 being exploited? There is no known exploitation of CVE-2026-29111 in the wild and no public exploit code. ## Other vulnerabilities in Systemd Project Systemd - [CVE-2015-7510](https://insights.sbomify.com/CVE-2015-7510/): Memory corruption in n/a (critical 9.8) - [CVE-2017-1000082](https://insights.sbomify.com/CVE-2017-1000082/): Privilege escalation in n/a (critical 9.8) - [CVE-2016-10156](https://insights.sbomify.com/CVE-2016-10156/): Privilege escalation in n/a (high 7.8) - [CVE-2017-9445](https://insights.sbomify.com/CVE-2017-9445/): Memory corruption in n/a (high 7.5) - [CVE-2017-9217](https://insights.sbomify.com/CVE-2017-9217/): Null dereference in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-29111 and fix it if it is affected. What it is: CVE-2026-29111 is a medium-severity denial of service vulnerability in Systemd Project Systemd, published on 23 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-29111 in the wild and no public exploit code. Affected product: Systemd Project Systemd. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-29111/ (Markdown: https://insights.sbomify.com/CVE-2026-29111/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29111 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29111 - OSV: https://osv.dev/vulnerability/CVE-2026-29111 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-29111/ Summaries are generated and may contain mistakes; the official description above is the record.