CVE-2026-29111MediumMicrosoft CVSS 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U

Microsoft security update for CVE-2026-29111

Published
May 31, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-29111. This page also shows what EchelonGraph holds for CVE-2026-29111, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products8

  • azl3 systemd 255-26 on Azure Linux 3.0
  • azl3 systemd-bootstrap 250.3-18 on Azure Linux 3.0
  • azl3 systemd-bootstrap 250.3-19 on Azure Linux 3.0
  • cbl2 systemd 250.3-23 on CBL Mariner 2.0
  • cbl2 systemd 250.3-24 on CBL Mariner 2.0
  • cbl2 systemd-bootstrap 250.3-13 on CBL Mariner 2.0
  • cbl2 systemd-bootstrap 250.3-14 on CBL Mariner 2.0
  • cbl2 systemd-bootstrap 250.3-14 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 3 updates

3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update250.3-14
—Security Update250.3-19
—Security Update—

🧭 EchelonGraph on CVE-2026-29111

EchelonGraph score
5.5 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-29111, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)