CVE-2026-15059 is a path traversal in systemd-oomd's D-Bus interface allowing unprivileged local users to kill arbitrary processes. The fix is simple validation, but the real issue is systemd's pattern of treating local socket callers as implicitly trusted — an assumption that ignores unprivileged users as adversarial actors with full /proc visibility. This vulnerability genotype has reproduced across systemd components and other privileged daemons, each time receiving a patch but no institutional memory of the flaw class. systemd-oomd's lifecycle (2019-2024, now deprecated) created an entropy window where initial trust assumptions never got revisited. Defenders should audit all systemd IPC handlers treating local socket callers as untrusted input; socket permissions control reachability, not trustworthiness. The architectural pressure to expose privileged operations via unprivileged IPC for usability outpaces security review capacity, creating accumulated permission surface that drives this recurring class.
CVE-2026-15059
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLocal unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA file path is built from user input without being confined, so sequences like “../” let an attacker step outside the intended directory. That can expose configuration, credentials, or source code, and in the worst case lets an attacker write files where they shouldn't. A durable fix resolves and canonicalises the path, then rejects anything that escapes a known-safe base directory.
General guidance for the path traversal class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-15059 is a path traversal in systemd-oomd's D-Bus interface allowing unprivileged local users to kill arbitrary processes. The fix is simple validation, but the real issue is systemd's pattern of treating local socket callers as implicitly trusted — an assumption that ignores unprivileged users as adversarial actors with full /proc visibility. This vulnerability genotype has reproduced across systemd components and other privileged daemons, each time receiving a patch but no institutional memory of the flaw class. systemd-oomd's lifecycle (2019-2024, now deprecated) created an entropy window where initial trust assumptions never got revisited. Defenders should audit all systemd IPC handlers treating local socket callers as untrusted input; socket permissions control reachability, not trustworthiness. The architectural pressure to expose privileged operations via unprivileged IPC for usability outpaces security review capacity, creating accumulated permission surface that drives this recurring class.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data