CVE-2026-15059

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

systemd-oomd: unprivileged users can terminate arbitrary processes · Advisory · systemd/systemd · GitHub

https://github.com/systemd/systemd/security/advisories/GHSA-652q-wxr6-h5j6

Vendor Advisories for CVE-2026-15059(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuudev (259.5-0ubuntu3.4) @ resolute2026-10-06ubuntu
redhatsystemd-main-261.2-1.hum12026-07-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
systemd252.11-1 ... 262~rc3-1 (188 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 262~rc3-1 (40 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 261~rc2-1 (27 versions)
  • every version up to 261~rc3-1: fixed in 261~rc3-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 153 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 53 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-12 16:32 UTCEG score recompute
  5. 2026-10-11 20:10 UTCEG score recompute
  6. 2026-10-11 17:22 UTCEG score recompute
  7. 2026-10-11 14:55 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-06 18:22 UTCEG score recompute
  14. 2026-10-06 18:22 UTCVendor advisory
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-05 07:48 UTCEG score recompute
  18. 2026-10-05 07:48 UTCVendor advisory
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-04 04:26 UTCEG score recompute
  21. 2026-10-04 04:26 UTCVendor advisory
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-02 09:19 UTCEG score recompute
  24. 2026-10-02 09:19 UTCVendor advisory
  25. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 75 more
  1. 2026-09-30 22:36 UTCEG score recompute
  2. 2026-09-30 22:36 UTCVendor advisory
  3. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-09-28 12:49 UTCEG score recompute
  7. 2026-09-28 12:49 UTCVendor advisory
  8. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-09-27 12:46 UTCEG score recompute
  10. 2026-09-27 12:46 UTCVendor advisory
  11. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-09-25 04:01 UTCEG score recompute
  13. 2026-09-25 04:01 UTCVendor advisory
  14. 2026-09-23 21:11 UTCEG score recompute
  15. 2026-09-23 21:11 UTCVendor advisory
  16. 2026-09-22 21:24 UTCEG score recompute
  17. 2026-09-22 21:24 UTCVendor advisory
  18. 2026-09-21 22:12 UTCEG score recompute
  19. 2026-09-21 22:12 UTCVendor advisory
  20. 2026-09-20 22:43 UTCVendor advisory
  21. 2026-09-19 23:23 UTCEG score recompute
  22. 2026-09-19 23:23 UTCVendor advisory
  23. 2026-09-19 00:11 UTCEG score recompute
  24. 2026-09-19 00:11 UTCVendor advisory
  25. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-18 00:56 UTCEG score recompute
  27. 2026-09-18 00:56 UTCVendor advisory
  28. 2026-09-17 01:44 UTCEG score recompute
  29. 2026-09-17 01:44 UTCVendor advisory
  30. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-16 02:31 UTCEG score recompute
  33. 2026-09-16 02:31 UTCVendor advisory
  34. 2026-09-15 01:22 UTCVendor advisory
  35. 2026-09-14 02:10 UTCEG score recompute
  36. 2026-09-14 02:10 UTCVendor advisory
  37. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  38. 2026-09-13 02:58 UTCEG score recompute
  39. 2026-09-13 02:58 UTCVendor advisory
  40. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-09-12 03:46 UTCEG score recompute
  42. 2026-09-12 03:46 UTCVendor advisory
  43. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  45. 2026-09-11 04:33 UTCEG score recompute
  46. 2026-09-11 04:33 UTCVendor advisory
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  48. 2026-09-10 05:15 UTCVendor advisory
  49. 2026-09-09 05:51 UTCEG score recompute
  50. 2026-09-09 05:51 UTCVendor advisory
  51. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  52. 2026-09-07 17:17 UTCEG score recompute
  53. 2026-09-07 17:17 UTCVendor advisory
  54. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  55. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  56. 2026-09-06 01:27 UTCEG score recompute
  57. 2026-09-06 01:27 UTCVendor advisory
  58. 2026-09-05 01:57 UTCEG score recompute
  59. 2026-09-05 01:57 UTCVendor advisory
  60. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  61. 2026-09-04 01:58 UTCVendor advisory
  62. 2026-09-03 02:31 UTCEG score recompute
  63. 2026-09-03 02:31 UTCVendor advisory
  64. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  65. 2026-09-01 21:04 UTCVendor advisory
  66. 2026-09-01 15:17 UTCEG score recompute
  67. 2026-09-01 15:17 UTCVendor advisory
  68. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  70. 2026-08-31 09:57 UTCEG score recompute
  71. 2026-08-31 09:57 UTCVendor advisory
  72. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  73. 2026-08-30 09:12 UTCVendor advisory
  74. 2026-08-29 09:58 UTCEG score recompute
  75. 2026-08-29 09:58 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

ubuntu:USN-8626-1

Frequently asked(5)

What is CVE-2026-15059?
CVE-2026-15059 is a medium-severity vulnerability; its CVE record was published on August 10, 2026. Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.
When was CVE-2026-15059 made public?
CVE-2026-15059 was made public on August 10, 2026: that is the date its CVE record's CNA, The systemd project, gives for when the vulnerability was made public. The CVE record itself was published on August 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-15059 actively exploited?
CVE-2026-15059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15059?
CVE-2026-15059 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15059?
A fix for CVE-2026-15059 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15059 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15059

Explore →

Is Your Infrastructure Affected by CVE-2026-15059?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs