# CVE-2025-26597: Xorg: xwayland: buffer overflow in xkbchangetypesofkey() > A buffer overflow in X.Org and Xwayland allows attackers to execute arbitrary code or cause a denial of service via crafted key symbol changes. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Feb 2025 - **Updated:** 29 Jun 2026 - **Also known as:** AZL-57283, AZL-57383, AZL-57479, BELL-CVE-2025-26597, DEBIAN-CVE-2025-26597, GHSA-7qjx-378m-p8hm, OESA-2026-1587, OESA-2026-1588, OESA-2026-1589, OESA-2026-1590, OESA-2026-1591, SUSE-SU-2025:0739-1, SUSE-SU-2025:0740-1, SUSE-SU-2025:0757-1, SUSE-SU-2025:20161-1, SUSE-SU-2025:20299-1, UBUNTU-CVE-2025-26597, openSUSE-SU-2025:14837-1 ## What is CVE-2025-26597? CVE-2025-26597 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 25 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A buffer overflow flaw was found in X.Org and Xwayland. If XkbChangeTypesOfKey() is called with a 0 group, it will resize the key symbols table to 0 but leave the key actions unchanged. If the same function is later called with a non-zero value of groups, this will cause a buffer overflow because the key actions are of the wrong size. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2025-26597? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libX11` | SUSE:Enterprise Storage 7.1 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.8.7-150600.3.3.1 | | `libX11` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.6.2-12.36.1 | | `libX11` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.6.2-12.36.1 | | `libX11` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Linux Micro 6.0 | All versions | 1.8.7-3.1 | | `libX11` | SUSE:Linux Micro 6.1 | All versions | 1.8.7-slfo.1.1_2.1 | | `libX11` | SUSE:Manager Proxy 4.3 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | SUSE:Manager Server 4.3 | All versions | 1.6.5-150000.3.36.1 | | `libX11` | openSUSE:Leap 15.6 | All versions | 1.8.7-150600.3.3.1 | | `libX11` | openSUSE:Tumbleweed | All versions | 1.8.11-2.1 | Products: Redhat Enterprise Linux, Tigervnc Tigervnc, X.org X Server, X.org Xwayland. ## How do I fix CVE-2025-26597? Apply the vendor's patch. ## Is CVE-2025-26597 being exploited? There is no known exploitation of CVE-2025-26597 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild) - [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8) - [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8) - [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8) - [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-26597 and fix it if it is affected. What it is: CVE-2025-26597 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 25 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-26597 in the wild and no public exploit code. Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-26597/ (Markdown: https://insights.sbomify.com/CVE-2025-26597/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26597 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26597 - OSV: https://osv.dev/vulnerability/CVE-2025-26597 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-26597/ Summaries are generated and may contain mistakes; the official description above is the record.