VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

postgrex: vulnerability history, versions and safety

postgrex is a package in the Hex ecosystem. Vulert records 4 vulnerabilities for it across 24 releases, from May 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
4 vulnerabilities recorded H1 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 07 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all postgrex vulnerabilities

Vulert verdict on postgrex 1.0.0-rc.1 i

Updated on 23 Oct 2026

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

Package health score 70/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 1.0.0-rc.1 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 07 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 142,411,596 packages i
  • Last release 119 months ago i

Version list, release dates, licence and dependants published by hex.pm, refreshed 22 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 postgrex, 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.0.0-rc.1 16 Nov 2016 none — — Details →
1.0.0-rc.0 16 Nov 2016 none — — Details →
0.22.4 07 Aug 2026 none — — Details →
0.22.3 09 Jul 2026 U1 — Yes Details →
0.22.2 12 May 2026 U2 — Yes Details →
0.22.1 05 May 2026 H1 U3 — Yes Details →
0.22.0 10 Jan 2026 H1 U3 — Yes Details →
0.21.1 03 Aug 2025 H1 U3 — Yes Details →
0.21.0 31 Jul 2025 H1 U3 — Yes Details →
0.20.0 05 Feb 2025 H1 U3 — Yes Details →
0.19.3 12 Nov 2024 H1 U3 — Yes Details →
0.19.2 23 Oct 2024 H1 U2 — Yes Details →
0.19.1 13 Aug 2024 H1 U2 — Yes Details →
0.19.0 03 Aug 2024 H1 U2 — Yes Details →
0.18.0 18 May 2024 H1 U2 — Yes Details →
0.17.5 01 Mar 2024 H1 U2 — Yes Details →
0.17.4 04 Dec 2023 H1 U2 — Yes Details →
0.17.3 29 Aug 2023 H1 U2 — Yes Details →
0.17.2 12 Jul 2023 H1 U2 — Yes Details →
0.17.1 13 Apr 2023 H1 U2 — Yes Details →
0.17.0 10 Apr 2023 H1 U2 — Yes Details →
0.16.5 20 Sep 2022 H1 U2 — Yes Details →
0.16.4 29 Jul 2022 H1 U2 — Yes Details →
0.16.3 27 Apr 2022 H1 U2 — Yes Details →
0.16.2 21 Feb 2022 H1 U2 — Yes Details →
0.16.1 24 Jan 2022 H1 U2 — Yes Details →
0.16.0 23 Jan 2022 H1 U2 — Yes Details →
0.15.13 25 Oct 2021 none — — Details →
0.15.12 17 Oct 2021 none — — Details →
0.15.11 26 Sep 2021 none — — Details →
0.15.10 27 Jul 2021 none — — Details →
0.15.9 24 Apr 2021 none — — Details →
0.15.8 19 Jan 2021 none — — Details →
0.15.7 17 Oct 2020 none — — Details →
0.15.6 21 Sep 2020 none — — Details →
0.15.5 03 Jun 2020 none — — Details →
0.15.4 09 May 2020 none — — Details →
0.15.3 11 Dec 2019 none — — Details →
0.15.2 04 Dec 2019 none — — Details →
0.15.1 16 Sep 2019 none — — Details →
0.15.0 18 Jul 2019 none — — Details →
0.14.3 08 May 2019 none — — Details →
0.14.2 12 Apr 2019 none — — Details →
0.14.1 24 Nov 2018 none — — Details →
0.14.0 29 Oct 2018 none — — Details →
0.14.0-rc.1 15 Oct 2018 none — — Details →
0.14.0-rc.0 07 Oct 2018 none — — Details →
0.13.5 09 Feb 2018 none — — Details →
0.13.4 25 Jan 2018 none — — Details →
0.13.3 31 May 2017 none — — Details →
0.13.2 05 Mar 2017 none — — Details →
0.13.1 20 Feb 2017 none — — Details →
0.13.0 17 Dec 2016 none — — Details →
0.13.0-rc.0 09 Dec 2016 none — — Details →
0.12.2 02 Aug 2017 none — — Details →
0.12.1 29 Sep 2016 none — — Details →
0.12.0 05 Sep 2016 none — — Details →
0.11.2 16 Jun 2016 none — — Details →
0.11.1 15 Feb 2016 none — — Details →
0.11.0 21 Jan 2016 none — — Details →
0.10.0 17 Nov 2015 none — — Details →
0.9.1 14 Jul 2015 none — — Details →
0.9.0 12 Jul 2015 none — — Details →
0.8.4 23 Jun 2015 none — — Details →
0.8.3 22 Jun 2015 none — — Details →
0.8.2 01 Jun 2015 none — — Details →
0.8.1 10 Apr 2015 none — — Details →
0.8.0 26 Feb 2015 none — — Details →
0.7.0 20 Jan 2015 none — — Details →
0.6.0 07 Sep 2014 none — — Details →
0.5.5 20 Aug 2014 none — — Details →
0.5.4 03 Aug 2014 none — — Details →
0.5.3 13 Jul 2014 none — — Details →
0.5.2 18 Jun 2014 none — — Details →
0.5.1 24 May 2014 none — — Details →
0.5.0 01 May 2014 none — — Details →
0.4.2 22 Apr 2014 none — — Details →

All 77 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 4

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

03 Vulnerabilities

Recorded vulnerabilities for postgrex

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-32687: Postgrex SQL Injection Vulnerability via Channel Name 7.5 high 0.22.2 12 May 2026
CVE-2026-32687: Postgrex SQL Injection Vulnerability in Notifications Module 7.5 high 0.22.2 18 May 2026
CVE-2026-66838: Postgrex SQL Injection via Comment Option in Streaming 5.9 medium 0.22.4 07 Aug 2026
CVE-2026-58225: Postgrex SQL Injection Vulnerability Leading to Notification Denial of Service 2.1 low 0.22.3 10 Jul 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 postgrex

Is postgrex safe to use?

Vulert records 4 vulnerabilities for postgrex in Hex: 0 critical, 1 high, 0 medium and 0 low, plus 3 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 postgrex's Vulert package health score?

Vulert scores postgrex 70/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 postgrex affected?

No. 1.0.0-rc.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.

How many vulnerabilities does postgrex have?

4 vulnerabilities are recorded for postgrex in the Hex ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 3 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 postgrex vulnerabilities disclosed?

4 vulnerabilities were recorded for postgrex in the last 12 months, and the oldest entry in this database dates to 12 May 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 postgrex 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 postgrex for upcoming vulnerabilities?

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