CVE Intelligence
Skip to main content
MEDIUM

CVE-2026-15059

CVE-2026-15059 — systemd-oomd: unprivileged users can terminate arbitrary processes

Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.

Published Updated Sources: cvelistV5, systemd

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

systemd

systemd_oomd

CVSS base

5.5

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

PoC

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (1)

systemd oomd

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.5CVSS 3.1MEDIUMcvelistV5

Weakness & attack patterns

  • CWE-22
  • CWE-59

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1547.009Boot or Logon Autostart Execution: Shortcut Modification
  • T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
  • T1574.010Hijack Execution Flow: Services File Permissions Weakness

References

1 on the record

Elsewhere on this site

  • systemdevery CVE for this vendor
  • CWE-22other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.