# CVE-2026-40226: Privilege escalation in systemd

> An attacker can escape to the host system via a crafted optional config file in systemd nspawn, leading to privilege escalation.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** AZL-82646, CLSA-2026-1786542017, DEBIAN-CVE-2026-40226, ECHO-918a-fd9a-b2cd, GHSA-9mj4-rrc3-gjcx, GHSA-hc7r-6254-88w5, OESA-2026-2277, OESA-2026-2278, OESA-2026-2279, OESA-2026-2280, OESA-2026-2358, SUSE-SU-2026:22736-1, SUSE-SU-2026:22890-1, SUSE-SU-2026:2785-1, SUSE-SU-2026:2809-1, SUSE-SU-2026:3244-1, UBUNTU-CVE-2026-40226

## What is CVE-2026-40226?

CVE-2026-40226 is a medium-severity vulnerability in Systemd Project Systemd, published on 10 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.

Weakness: CWE-348 (Use of Less Trusted Source)

## Which versions are affected by CVE-2026-40226?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemd` | SUSE:Linux Enterprise Micro 5.2 | All versions | 246.16-150300.7.74.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.3 | All versions | 249.17-150400.8.64.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.4 | All versions | 249.17-150400.8.64.1 |
| `systemd` | SUSE:Linux Enterprise Micro 5.5 | All versions | 249.17-150400.8.64.1 |
| `systemd` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 254.27-150600.4.71.2 |
| `systemd` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 254.27-150600.4.71.2 |
| `systemd` | SUSE:Linux Micro 6.0 | All versions | 254.27-4.1 |
| `systemd` | SUSE:Linux Micro 6.1 | All versions | 254.27-slfo.1.1_5.1 |

Products: Systemd Project Systemd.

## How do I fix CVE-2026-40226?

Upgrade to a fixed version.

## Is CVE-2026-40226 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40226 exists.

## 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-40226 and fix it if it is affected.

What it is: CVE-2026-40226 is a medium-severity vulnerability in Systemd Project Systemd, published on 10 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40226 exists.

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-40226/ (Markdown: https://insights.sbomify.com/CVE-2026-40226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40226
- OSV: https://osv.dev/vulnerability/CVE-2026-40226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40226/
Summaries are generated and may contain mistakes; the official description above is the record.