# CVE-2026-93516: .Org Server XInput Passive Grab Use-After-Free


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111443, AZL-111479, BELL-CVE-2026-93516, DEBIAN-CVE-2026-93516, ECHO-e34c-c597-8b7b, GHSA-hpj6-w8rm-g9h3, UBUNTU-CVE-2026-93516

## What is CVE-2026-93516?

CVE-2026-93516 is a medium-severity vulnerability in x.org xorg-x11-server, published on 28 Oct 2026. 

### Official description

A use-after-free caused by lack of lifecycle management when adding / removing XInput master devices in X.org X Server before 21.1.25 and XWayland before 24.1.14 could be used by authenticated X Clients to crash the X server or potentially execute code in X server context.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-93516?


## How do I fix CVE-2026-93516?

Upgrade to a fixed version.

## Is CVE-2026-93516 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93516 and fix it if it is affected.

What it is: CVE-2026-93516 is a medium-severity vulnerability in x.org xorg-x11-server, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93516 in the wild and no public exploit code.

Affected product: x.org xorg-x11-server. 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-2026-93516/ (Markdown: https://insights.sbomify.com/CVE-2026-93516/index.md)
```

## Sources

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

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