CVE-2026-29111

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

March 23, 2026

Last Modified

June 17, 2026

Advisory Details (10)

Auto-updated Aug 4, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit efa6ba2ab625 (systemd/systemd)

Fix landed in systemd/systemd commit efa6ba2ab625 — awaiting tagged release

https://github.com/systemd/systemd/commit/efa6ba2ab625aaa160ac435a09e6482fc63bdbe8
github_commit

commit b5fd14693057 (systemd/systemd)

Fix landed in systemd/systemd commit b5fd14693057 — awaiting tagged release

https://github.com/systemd/systemd/commit/b5fd14693057e5f2c9b4a49603be64ec3608ff6c
github_commit

commit 80acea4ef80a (systemd/systemd)

Fix landed in systemd/systemd commit 80acea4ef80a — awaiting tagged release

https://github.com/systemd/systemd/commit/80acea4ef80a4bb78560ed970c34952299b890d6
github_commit

commit 7ac322021369 (systemd/systemd)

Fix landed in systemd/systemd commit 7ac322021369 — awaiting tagged release

https://github.com/systemd/systemd/commit/7ac3220213690e8a8d6d2a6e81e43bd1dce01d69
github_commit

commit 54588d2dedff (systemd/systemd)

Fix landed in systemd/systemd commit 54588d2dedff — awaiting tagged release

https://github.com/systemd/systemd/commit/54588d2dedff54bfb6036670820650e4ea74628f
github_commit

commit 42aee39107fb (systemd/systemd)

Fix landed in systemd/systemd commit 42aee39107fb — awaiting tagged release

https://github.com/systemd/systemd/commit/42aee39107fbdd7db1ccd402a2151822b2805e9f
github_commit

commit 3cee294fe8cf (systemd/systemd)

Fix landed in systemd/systemd commit 3cee294fe8cf — awaiting tagged release

https://github.com/systemd/systemd/commit/3cee294fe8cf4fa0eff933ab21416d099942cabd
github_commit

commit 21167006574d (systemd/systemd)

Fix landed in systemd/systemd commit 21167006574d — awaiting tagged release

https://github.com/systemd/systemd/commit/21167006574d6b83813c7596759b474f56562412
github_commit

commit 20021e768642 (systemd/systemd)

Fix landed in systemd/systemd commit 20021e768642 — awaiting tagged release

https://github.com/systemd/systemd/commit/20021e7686426052e3a7505425d7e12085feb2a6
github_commit

commit 1d22f706bd04 (systemd/systemd)

Fix landed in systemd/systemd commit 1d22f706bd04 — awaiting tagged release

https://github.com/systemd/systemd/commit/1d22f706bd04f45f8422e17fbde3f56ece17758a

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsystemd-0:252-14.el9_2.112026-08-06redhat
redhatsystemd-0:252-32.el9_4.112026-08-06redhat
redhatsystemd-0:239-58.el8_6.162026-08-04redhat
redhatsystemd-0:239-74.el8_8.72026-08-04redhat
redhatsystemd-0:239-45.el8_4.172026-08-04redhat
redhatsystemd-0:252-51.el9_6.62026-08-04redhat
redhatsystemd-0:257-9.el10_0.22026-06-15redhat
ubuntuudev (257.9-0ubuntu2.3) @ questing2026-06-11ubuntu
ubuntuudev (245.4-4ubuntu3.24+esm3) @ focal2026-06-11ubuntu
redhatinsights-proxy/insights-proxy-container-rhel9:17804204282026-06-02redhat
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatsystemd-0:252-67.el9_8.22026-05-19redhat
redhatsystemd-0:257-23.el10_2.12026-05-19redhat
redhatrhosdt/opentelemetry-target-allocator-rhel9:17780562452026-05-06redhat
redhatsystemd-0:257-13.el10_1.32026-05-05redhat
redhatsystemd-0:252-55.el9_7.92026-05-05redhat
redhatsystemd-main-260.1-2.1.hum12026-04-09redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
systemd247.3-6 ... 247.3-7+deb11u7 (9 versions)247.3-7+deb11u8
Debian:12(1)
PackageVulnerable rangeFixed inDependents
systemd252.11-1 ... 252.6-1+loong64 (31 versions)252.39-1~deb12u2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
systemd257.7-1, 257.8-1~deb13u1, 257.8-1~deb13u2, 257.9-1~deb13u1257.13-1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
systemd257.13-1~deb13u1 ... 260~rc1-2 (20 versions)260~rc2-1

Weakness Classification(1)

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 7× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-29111?
CVE-2026-29111 is a medium vulnerability published on March 23, 2026. systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this…
When was CVE-2026-29111 disclosed?
CVE-2026-29111 was first published in the National Vulnerability Database on March 23, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-29111 actively exploited?
CVE-2026-29111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-29111?
CVE-2026-29111 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-29111?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-29111, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-29111?

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