CVE-2025-26598HighMicrosoft CVSS 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Microsoft security update for CVE-2025-26598

Published
June 3, 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-2025-26598. This page also shows what EchelonGraph holds for CVE-2025-26598, 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 products4

  • azl3 xorg-x11-server-Xwayland 24.1.1-3 on Azure Linux 3.0
  • azl3 xorg-x11-server-Xwayland 24.1.6-1 on Azure Linux 3.0
  • cbl2 xorg-x11-server 1.20.10-15 on CBL Mariner 2.0
  • cbl2 xorg-x11-server 1.20.10-15 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 2 updates

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

KB articleUpdateFixed build
—Security Update24.1.6-1
—Security Update1.20.10-15

🧭 EchelonGraph on CVE-2025-26598

EchelonGraph score
7.8 HIGH
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

An out-of-bounds write flaw was found in X.Org and Xwayland. The function GetBarrierDevice() searches for the pointer device based on its device ID and returns the matching value, or supposedly NULL, if no match was found. However, the code will return the last element of the list if no matching device ID is found, which can lead to out-of-bounds memory access.

Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2025-26598, 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)