Read the docs

Config parsing flaws in systemd-nspawn let containers escape to host

Priority MEDIUM 44Published · Updated

Key facts

Attack vector
Local
Privileges required
High
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-9mj4-rrc3-gjcx. Fix status from GitHub.

Summary

systemd-nspawn from 233 before 260 is affected. Two parsing bugs in optional .nspawn configuration files mishandle the PivotRoot=, BindUser= and Ephemeral= options, so a container starts on the host root filesystem instead of its image, with high privileges. An attacker needs high privileges and local access to place such config files in directories that systemd-nspawn reads automatically.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact systemd-nspawn optionally supports configuration files to drive the behaviour of spawned containers. These config files can be downloaded together with images, and require privileges to be stored in directories where they are picked up automatically from. Two parsing bugs affect these config files for the `PivotRoot=`, `BindUser=` and `Ephemeral=` options, resulting the container in being spawned on the host rootfs, instead of the container image, with high privileges. ### Patches v260 https://github.com/systemd/systemd/commit/61bceb1bff4b1f9c126b18dc971ca3e6d8c71c40 https://github.com/systemd/systemd/commit/7b85f5498a958e5bb660c703b8f4a71cceed3373 v259.4 https://github.com/systemd/systemd/commit/718711ed876c870a72149eea279b819cdab14e91 https://github.com/systemd/systemd/commit/6566dc1451089e07090f5a114ae2eb43ed39188d v258.6 https://github.com/systemd/systemd/commit/e4db9c12957d315c0ed22c6ca87a816d0927d6dc https://github.com/systemd/systemd/commit/1c55a0a5e26a07df828f72092ad1203e221b60db v257.12 https://github.com/systemd/systemd/commit/773fd3b6e72e6c83cbb1cfc1cb20f3793db8649a https://github.com/systemd/systemd/commit/bfa0a842822c4f79da9d47f8a773fd128d8f8a0a ### Workarounds Sanitize storage directories to ensure no `.nspawn` config files are used, or they don't use `PivotRoot=`, `BindUser=` or `Ephemeral=`. ### References Originally reported on yeswehack.com as YWH-PGM9780-116

Why it matters now

Fix Fixed systemd-nspawn (linux): 260 259.4 258.6 257.12

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—systemd-nspawn (linux)>= 233, < 260260 259.4 258.6 257.12Patch availableGHSA-9mj4-rrc3-gjcx
  • systemd-nspawn (linux) Vendor— Affected >= 233, < 260 Fixed in 260 259.4 258.6 257.12 Patch available GHSA-9mj4-rrc3-gjcx

Remediation

Upgrade to systemd-nspawn 260, 259.4, 258.6 or 257.12, which contain the fix. Until then, sanitize storage directories so no .nspawn config files are used, or do not use the PivotRoot=, BindUser= or Ephemeral= options.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-9mj4-rrc3-gjcx systemd-nspawn (linux) Fixed in 260 259.4 258.6 257.12 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-9mj4-rrc3-gjcx

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences