Vulnerability Database · Alpine · Package report

postgresql: vulnerability history, versions and safety

postgresql is a package in the Alpine ecosystem. Vulert records 60 vulnerabilities for it across 112 releases, from May 2017 to Oct 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
60 vulnerabilities recorded U60
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.

Vulert verdict on postgresql i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 11 Oct 2021. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 60 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 60 over 4 years · 0 in the last year i
  • Latest disclosure 11 Oct 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

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 holds for postgresql, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
11.11-r0 U6 Yes Details →
11.10-r0 U8 Yes Details →
11.9-r0 U14 Yes Details →
11.7-r0 U18 Yes Details →
11.6-r0 U20 Yes Details →
11.5-r1 U20 Yes Details →
11.5-r0 U20 Yes Details →
11.4-r0 U24 Yes Details →
11.3-r2 U26 Yes Details →
11.3-r1 U26 Yes Details →
11.3-r0 U26 Yes Details →
11.2-r1 U30 Yes Details →
11.2-r0 U30 Yes Details →
11.1-r0 U30 Yes Details →
11.0-r1 U32 Yes Details →
10.5-r1 U32 Yes Details →
10.4-r1 U36 Yes Details →
10.3-r1 U38 Yes Details →
10.3-r0 U38 Yes Details →
10.2-r0 U40 Yes Details →
10.1-r2 U44 Yes Details →
10.1-r1 U44 Yes Details →
10.1-r0 U44 Yes Details →
10.0-r1 U48 Yes Details →
10.0-r0 U48 Yes Details →
9.6.5-r1 U48 Yes Details →
9.6.5-r0 U48 Yes Details →
9.6.4-r1 U48 Yes Details →
9.6.4-r0 U48 Yes Details →
9.6.3-r0 U54 Yes Details →
9.6.2-r4 U60 Yes Details →
9.6.2-r3 U60 Yes Details →
9.6.2-r2 U60 Yes Details →
9.6.2-r1 U60 Yes Details →
9.6.2-r0 U60 Yes Details →
9.6.1-r1 U60 Yes Details →
9.6.1-r0 U60 Yes Details →
9.6.0-r1 U60 Yes Details →
9.6.0-r0 U60 Yes Details →
9.5.4-r0 U60 Yes Details →
9.5.3-r1 U60 Yes Details →
9.5.3-r0 U60 Yes Details →
9.5.2-r4 U60 Yes Details →
9.5.2-r3 U60 Yes Details →
9.5.2-r2 U60 Yes Details →
9.5.2-r1 U60 Yes Details →
9.5.2-r0 U60 Yes Details →
9.5.1-r0 U60 Yes Details →
9.5.0-r0 U60 Yes Details →
9.4.5-r1 U60 Yes Details →
9.4.5-r0 U60 Yes Details →
9.4.4-r0 U60 Yes Details →
9.4.3-r0 U60 Yes Details →
9.4.2-r0 U60 Yes Details →
9.4.1-r3 U60 Yes Details →
9.4.1-r2 U60 Yes Details →
9.4.1-r1 U60 Yes Details →
9.4.1-r0 U60 Yes Details →
9.4.0-r0 U60 Yes Details →
9.3.5-r1 U60 Yes Details →
9.3.5-r0 U60 Yes Details →
9.3.4-r1 U60 Yes Details →
9.3.4-r0 U60 Yes Details →
9.3.3-r2 U60 Yes Details →
9.3.3-r1 U60 Yes Details →
9.3.3-r0 U60 Yes Details →
9.3.2-r0 U60 Yes Details →
9.3.1-r0 U60 Yes Details →
9.3.0-r2 U60 Yes Details →
9.3.0-r1 U60 Yes Details →
9.3.0-r0 U60 Yes Details →
9.2.4-r0 U60 Yes Details →
9.2.3-r0 U60 Yes Details →
9.2.2-r0 U60 Yes Details →
9.2.1-r2 U60 Yes Details →
9.2.1-r1 U60 Yes Details →
9.2.1-r0 U60 Yes Details →
9.2.0-r1 U60 Yes Details →
9.2.0-r0 U60 Yes Details →
9.1.5-r0 U60 Yes Details →
9.1.4-r0 U60 Yes Details →
9.1.3-r0 U60 Yes Details →
9.1.2-r2 U60 Yes Details →
9.1.2-r1 U60 Yes Details →
9.1.2-r0 U60 Yes Details →
9.1.1-r2 U60 Yes Details →
9.1.1-r1 U60 Yes Details →
9.1.1-r0 U60 Yes Details →
9.1.0-r1 U60 Yes Details →
9.1.0-r0 U60 Yes Details →
9.0.4-r0 U60 Yes Details →
9.0.3-r1 U60 Yes Details →
9.0.3-r0 U60 Yes Details →
9.0.2-r0 U60 Yes Details →
9.0.1-r0 U60 Yes Details →
8.4.4-r0 U60 Yes Details →
8.4.3-r3 U60 Yes Details →
8.4.3-r2 U60 Yes Details →
8.4.3-r1 U60 Yes Details →
8.4.3-r0 U60 Yes Details →
8.4.2-r1 U60 Yes Details →
8.4.2-r0 U60 Yes Details →
8.4.1-r1 U60 Yes Details →
8.4.1-r0 U60 Yes Details →
8.4.0-r2 U60 Yes Details →
8.4.0-r1 U60 Yes Details →
8.4.0-r0 U60 Yes Details →
8.3.7-r3 U60 Yes Details →
8.3.7-r2 U60 Yes Details →
8.3.7-r1 U60 Yes Details →
8.3.7-r0 U60 Yes Details →
8.3.5-r0 U60 Yes Details →

Newest 112 of 112 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 16
  • 2018 14
  • 2019 10
  • 2020 12
  • 2021 8

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

03 Vulnerabilities

Recorded vulnerabilities for postgresql

The 5 most severe of 60 vulnerabilities recorded for this package

Search all 60 in the database →

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 postgresql

Is postgresql safe to use?

Vulert records 60 vulnerabilities for postgresql in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 60 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.

How many vulnerabilities does postgresql have?

60 vulnerabilities are recorded for postgresql in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 60 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 postgresql vulnerabilities disclosed?

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

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