CVE-2026-15059: systemd-oomd · Path Traversal
Affects systemd-oomdSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 261 when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 261
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 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 8 Nov 2026.
What to do
Upgrade systemd-oomd to 261.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| systemdsystemd-oomd | Affected
| Fixed in
|
GitHubsystemd-oomdpkg:github/systemd-oomdOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict local user access and monitor for suspicious IPC activity related to systemd-oomd. Avoid running untrusted local code that could exploit this vulnerability.
Description
Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.