# CVE-2025-26599: Xorg: xwayland: use of uninitialized pointer in compredirectwindow()

> An uninitialized pointer in Xorg/Xwayland can cause a crash when memory allocation fails, leading to denial of service.

- **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-57298, AZL-57318, AZL-57446, BELL-CVE-2025-26599, DEBIAN-CVE-2025-26599, GHSA-wv34-xcj8-f3mq, UBUNTU-CVE-2025-26599

## What is CVE-2025-26599?

CVE-2025-26599 is a high-severity 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

An access to an uninitialized pointer flaw was found in X.Org and Xwayland. The function compCheckRedirect() may fail if it cannot allocate the backing pixmap. In that case, compRedirectWindow() will return a BadAlloc error without validating the window tree marked just before, which leaves the validated data partly initialized and the use of an uninitialized pointer later.

Weakness: CWE-824 (Access of Uninitialized Pointer)

## Which versions are affected by CVE-2025-26599?

It affects 4 products.


Products: Redhat Enterprise Linux, Tigervnc Tigervnc, X.org X Server, X.org Xwayland.

## How do I fix CVE-2025-26599?

Apply the vendor's patch.

## Is CVE-2025-26599 being exploited?

There is no known exploitation of CVE-2025-26599 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-26599 and fix it if it is affected.

What it is: CVE-2025-26599 is a high-severity 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-26599 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-26599/ (Markdown: https://insights.sbomify.com/CVE-2025-26599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26599
- OSV: https://osv.dev/vulnerability/CVE-2025-26599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-26599/
Summaries are generated and may contain mistakes; the official description above is the record.