systemd · In Nspawn
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 11:52 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.07% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 12 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
AI-suggested
Users should monitor official vendor advisories for updates or fixes addressing this vulnerability. Until a fix is available, avoid using untrusted optional configuration files with nspawn.
Description
A vulnerability exists in systemd's nspawn component versions 2.0 and 3.0, where an escape-to-host action can be triggered via a crafted optional configuration file. This issue affects versions 2.0 and 3.0 specifically. No CVSS score is provided, and no public exploit or known exploitation in the wild has been reported. No patch or remediation information is available from the provided data.