VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

pgsync: vulnerability history, versions and safety

pgsync is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 34 releases, first recorded in Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 pgsync vulnerabilities

Vulert verdict on pgsync 0.8.1 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 0.8.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 27 Apr 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Last release 13 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, 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 pgsync, 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.8.1 12 Sep 2025 none MIT — Details →
0.8.0 11 Jul 2024 none MIT — Details →
0.7.4 07 Mar 2023 none MIT — Details →
0.7.3 10 Nov 2022 none MIT — Details →
0.7.2 19 Sep 2022 none MIT — Details →
0.7.1 06 Jul 2022 none MIT — Details →
0.7.0 11 Mar 2022 none MIT — Details →
0.6.8 21 Sep 2021 none MIT — Details →
0.6.7 26 Apr 2021 none MIT — Details →
0.6.6 30 Oct 2020 H1 MIT Yes Details →
0.6.5 10 Jul 2020 H1 MIT Yes Details →
0.6.4 11 Jun 2020 H1 MIT Yes Details →
0.6.3 10 Jun 2020 H1 MIT Yes Details →
0.6.2 10 Jun 2020 H1 MIT Yes Details →
0.6.1 08 Jun 2020 H1 MIT Yes Details →
0.6.0 07 Jun 2020 H1 MIT Yes Details →
0.5.5 14 May 2020 H1 MIT Yes Details →
0.5.4 10 May 2020 H1 MIT Yes Details →
0.5.3 04 Apr 2020 H1 MIT Yes Details →
0.5.2 28 Mar 2020 H1 MIT Yes Details →
0.5.1 27 Mar 2020 H1 MIT Yes Details →
0.5.0 27 Mar 2020 H1 MIT Yes Details →
0.4.3 28 Oct 2019 H1 MIT Yes Details →
0.4.2 28 Oct 2019 H1 MIT Yes Details →
0.4.1 15 Dec 2018 H1 MIT Yes Details →
0.4.0 01 Mar 2018 H1 MIT Yes Details →
0.3.9 27 Feb 2018 H1 MIT Yes Details →
0.3.8 01 Oct 2017 H1 MIT Yes Details →
0.3.7 30 Aug 2017 H1 MIT Yes Details →
0.3.6 03 Oct 2016 H1 MIT Yes Details →
0.3.5 23 Jul 2016 H1 MIT Yes Details →
0.3.4 29 Apr 2016 H1 MIT Yes Details →
0.3.3 26 Apr 2016 H1 MIT Yes Details →
0.3.2 19 Apr 2016 H1 MIT Yes Details →
0.3.1 07 Apr 2016 H1 MIT Yes Details →
0.3.0 07 Apr 2016 H1 MIT Yes Details →
0.2.4 05 Apr 2016 H1 MIT Yes Details →
0.2.3 31 Mar 2016 H1 MIT Yes Details →
0.2.2 28 Mar 2016 H1 MIT Yes Details →
0.2.1 27 Mar 2016 H1 MIT Yes Details →
0.2.0 26 Mar 2016 H1 MIT Yes Details →
0.1.1 24 Mar 2016 H1 MIT Yes Details →
0.1.0 08 Dec 2015 H1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for pgsync

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-31671: Cleartext Transmission of Sensitive Information in pgsync 7.5 high 0.6.7 27 Apr 2021

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 pgsync

Is pgsync safe to use?

Vulert records 1 vulnerabilities for pgsync in RubyGems: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is pgsync's Vulert package health score?

Vulert scores pgsync 87/100, which reads as healthy. 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 pgsync affected?

No. 0.8.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 pgsync should I use?

0.8.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 pgsync have?

1 vulnerability is recorded for pgsync in the RubyGems ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pgsync vulnerabilities disclosed?

0 vulnerabilities were recorded for pgsync in the last 12 months, and the oldest entry in this database dates to 27 Apr 2021. 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 pgsync 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 pgsync for upcoming vulnerabilities?

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