# CVE-2025-49179: Xorg-x11-server-xwayland: xorg-x11-server: tigervnc: integer overflow in x record extension

> An integer overflow in the X Record extension allows clients to bypass length checks, potentially leading to security bypasses in Xorg-based operating systems.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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:** 17 Jun 2025
- **Updated:** 30 Jun 2026
- **Also known as:** AZL-64193, AZL-64239, AZL-64265, BELL-CVE-2025-49179, DEBIAN-CVE-2025-49179, GHSA-q547-25x8-mx66, UBUNTU-CVE-2025-49179

## What is CVE-2025-49179?

CVE-2025-49179 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 17 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the X Record extension. The RecordSanityCheckRegisterClients function does not check for an integer overflow when computing request length, which allows a client to bypass length checks.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2025-49179 being exploited?

There is no known exploitation of CVE-2025-49179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49179 and fix it if it is affected.

What it is: CVE-2025-49179 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 17 Jun 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-49179 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-49179/ (Markdown: https://insights.sbomify.com/CVE-2025-49179/index.md)
```

## Sources

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

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