Libxtst
5 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Libxtst, a product in the operating systems space. Use it to gauge the current risk picture and drill into individual advisories.
Libxtst CVEs per month
| Month | CVEs |
|---|---|
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 1 |
| 2026-10 | 1 |
| 2026-11 | 0 |
Severity
How the 5 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical1
- High2
- Medium2
Latest CVEs
The 5 most recently published vulnerabilities affecting Libxtst.
- CVE-2026-109088libXtst RECORD EnableContext Reply Endless Loop6.5
- CVE-2026-94286Out-of-bounds read in libXtst's RECORD reply parser7.1
- CVE-2016-7951Multiple integer overflows in X.org libXtst before 1.2.3 allow remote X servers to trigger out-of-bounds memory access operations by leveraging the lack of range checks.9.8
- CVE-2016-7952X.org libXtst before 1.2.3 allows remote X servers to cause a denial of service (infinite loop) via a reply in the (1) XRecordStartOfData, (2) XRecordEndOfData, or (3) XRecordClientDied category wi...7.5
- CVE-2013-2063Integer overflow in X.org libXtst 1.2.1 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the XRecordGetContext function.6.8
Product grouping is registry-driven, with AI assist and human review. How it works