VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

xcb: vulnerability history, versions and safety

xcb is a package in the crates.io ecosystem. Vulert records 11 vulnerabilities for it across 35 releases, from Dec 2020 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C3 H1 M1 L1 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all xcb vulnerabilities

Vulert verdict on xcb 1.7.1 i

Updated on 23 Oct 2026

Good news: 1.7.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 11.

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 1.7.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.7.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.7.1 — unaffected i
  • Vulnerabilities on record 11 over 4 years · 0 in the last year i
  • Latest disclosure 22 Aug 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 70 packages i
  • Stars 168 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for xcb, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.7.1 09 Aug 2026 none MIT — Details →
1.7.0 03 Jan 2026 none MIT — Details →
1.6.0 15 Aug 2025 none MIT — Details →
1.5.0 10 Nov 2024 L1 U1 MIT Yes Details →
1.4.0 23 Apr 2024 L1 U1 MIT Yes Details →
1.3.0 09 Dec 2023 L1 U1 MIT Yes Details →
1.2.2 22 Jul 2023 L1 U1 MIT Yes Details →
1.2.1 23 Apr 2023 L1 U1 MIT Yes Details →
1.2.0 03 Nov 2022 L1 U1 MIT Yes Details →
1.1.1 19 Mar 2022 L1 U1 MIT Yes Details →
1.1.0 16 Mar 2022 L1 U1 MIT Yes Details →
1.0.0 06 Mar 2022 L1 U1 MIT Yes Details →
1.0.0-beta.4 30 Jan 2022 C3 H1 M1 L1 U5 MIT Yes Details →
1.0.0-beta.3 26 Dec 2021 C3 H1 M1 L1 U5 MIT Yes Details →
1.0.0-beta.2 19 Dec 2021 C3 H1 M1 L1 U5 MIT Yes Details →
1.0.0-beta.1 30 Nov 2021 C3 H1 M1 L1 U5 MIT Yes Details →
1.0.0-beta.0 11 Nov 2021 C3 H1 M1 L1 U5 MIT Yes Details →
0.10.1 21 Sep 2021 C3 H1 M1 L1 U5 MIT Yes Details →
0.10.0 18 Sep 2021 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.8 12 Nov 2019 C3 H1 M1 L1 U5 MIT Yes Details →
0.9.0 12 Nov 2019 C3 H1 M1 L1 U5 MIT Yes Details →
0.8.2 25 Feb 2018 C3 H1 M1 L1 U5 MIT Yes Details →
0.8.1 15 Aug 2017 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.7 15 Aug 2017 C3 H1 M1 L1 U5 MIT Yes Details →
0.8.0 11 Jul 2017 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.6 14 Nov 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.5 22 Aug 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.4 07 Jul 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.3 10 Apr 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.2 02 Apr 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.1 29 Mar 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.7.0 28 Mar 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.6.2 04 Mar 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.6.1 02 Mar 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.6.0 22 Feb 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.5.0 08 Feb 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.4.1 07 Feb 2016 C3 H1 M1 L1 U5 MIT Yes Details →
0.4.0 03 Feb 2016 C3 H1 M1 L1 U5 MIT Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 7
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for xcb

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-26957: Out of Bounds Read in xcb 9.8 critical 1.0.0 25 Aug 2021
CVE-2021-26956: Arbitrary return types in xcb 9.8 critical 1.0.0 25 Aug 2021
CVE-2021-26955: Unchecked Return Value in xcb 9.8 critical 1.0.0 25 Aug 2021
CVE-2021-26958: Unchecked Return Value in xcb 8.8 high 1.0.0 25 Aug 2021
CVE-2020-36205: Memory handling issues in xcb 5.5 medium 1.0.0 10 Dec 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About xcb

Is xcb safe to use?

Vulert records 11 vulnerabilities for xcb in crates.io: 3 critical, 1 high, 1 medium and 1 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is xcb's Vulert package health score?

Vulert scores xcb 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of xcb affected?

No. 1.7.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of xcb should I use?

1.7.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does xcb have?

11 vulnerabilities are recorded for xcb in the crates.io ecosystem: 3 critical, 1 high, 1 medium and 1 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new xcb vulnerabilities disclosed?

0 vulnerabilities were recorded for xcb in the last 12 months, and the oldest entry in this database dates to 10 Dec 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of xcb are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor xcb for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the xcb version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.