This page lists publicly disclosed CVE vulnerabilities affecting xcb_project xcb (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2021-26958 | An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because transmutation to the wrong type can happen after xcb::base::cast_event uses std::mem::transmute to return a reference to an arbitrary type. | [email protected] | 8.8 | 1.60% | 2021-02-09 | 2026-06-16 |
| CVE-2021-26957 | An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because there is an out-of-bounds read in xcb::xproto::change_property(), as demonstrated by a format=32 T=u8 situation where out-of-bounds bytes are sent to an X server. | [email protected] | 9.8 | 1.75% | 2021-02-09 | 2026-06-16 |
| CVE-2021-26956 | An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because bytes from an X server can be interpreted as any data type returned by xcb::xproto::GetPropertyReply::value. | [email protected] | 9.8 | 1.73% | 2021-02-09 | 2026-06-16 |
| CVE-2021-26955 | An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because xcb::xproto::GetAtomNameReply::name() calls std::str::from_utf8_unchecked() on unvalidated bytes from an X server. | [email protected] | 9.8 | 1.73% | 2021-02-09 | 2026-06-16 |
| CVE-2020-36205 | An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. | [email protected] | 5.5 | 0.40% | 2021-01-26 | 2026-06-16 |