VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

tokio-postgres: vulnerability history, versions and safety

tokio-postgres is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 27 releases, from Jun 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 24 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tokio-postgres vulnerabilities

Vulert verdict on tokio-postgres 0.7.18 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

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

  • Current release 0.7.18 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 24 Aug 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Stars 4,017 i
  • Last release 4 months ago i
  • Licence Apache-2.0 OR 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 tokio-postgres, 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
0.7.18 12 Jun 2026 none Apache-2.0 OR MIT — Details →
0.7.17 30 Mar 2026 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.16 14 Jan 2026 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.15 08 Oct 2025 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.14 25 Sep 2025 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.13 02 Feb 2025 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.12 16 Sep 2024 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.11 22 Jul 2024 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.10 25 Aug 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.9 20 Aug 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.8 27 Mar 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.7 21 Aug 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.6 30 Apr 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.5 30 Oct 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.4 19 Oct 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.3 29 Sep 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.2 25 Apr 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.1 03 Apr 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.0 25 Dec 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.6.0 17 Oct 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.5 03 Jul 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.4 01 May 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.3 06 Mar 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.2 01 Feb 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.1 25 Dec 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.0 23 Dec 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.0-alpha.2 28 Nov 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.5.0-alpha.1 15 Oct 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.4.0-rc.3 30 Jun 2019 none Apache-2.0 OR MIT — Details →
0.4.0-rc.2 06 Mar 2019 none Apache-2.0 OR MIT — Details →
0.4.0-rc.1 06 Mar 2019 none Apache-2.0 OR MIT — Details →
0.3.0 30 Sep 2017 none MIT — Details →
0.2.3 11 Jun 2017 none MIT — Details →
0.2.2 02 May 2017 none MIT — Details →
0.2.1 24 Feb 2017 none MIT — Details →
0.2.0 21 Feb 2017 none MIT — Details →
0.1.1 04 Feb 2017 none MIT — Details →
0.1.0 26 Dec 2016 none MIT — 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

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for tokio-postgres

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in tokio-postgres: Panic on DataRow with Fewer Fields 6.9 medium 0.7.18 12 Jun 2026
Denial of Service Vulnerability in tokio-postgres: Panic on DataRow with Fewer Fields 6.9 medium 0.7.18 24 Aug 2026

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 tokio-postgres

Is tokio-postgres safe to use?

Vulert records 2 vulnerabilities for tokio-postgres in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 tokio-postgres's Vulert package health score?

Vulert scores tokio-postgres 81/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 tokio-postgres affected?

No. 0.7.18, 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 tokio-postgres should I use?

0.7.18 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 tokio-postgres have?

2 vulnerabilities are recorded for tokio-postgres in the crates.io ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 tokio-postgres vulnerabilities disclosed?

2 vulnerabilities were recorded for tokio-postgres in the last 12 months, and the oldest entry in this database dates to 12 Jun 2026. 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 tokio-postgres 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 tokio-postgres for upcoming vulnerabilities?

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