VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

postgresql16: vulnerability history, versions and safety

postgresql16 is a package in the Alpine ecosystem. Vulert records 27 vulnerabilities for it across 1 affected range, first recorded in 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
27 vulnerabilities recorded U27
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
27 in the last 12 months

Most recent disclosure 13 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all postgresql16 vulnerabilities

Vulert verdict on postgresql16 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 27 vulnerabilities on record across 1 year, 27 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 27 over 1 year · 27 in the last year i
  • Latest disclosure 13 Aug 2026 i
  • Highest CVSS 8.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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 16.15-r0 (exclusive) 27

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 27

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

03 Vulnerabilities

Recorded vulnerabilities for postgresql16

The 5 most severe of 27 vulnerabilities recorded for this package

Search all 27 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Integer Wraparound Vulnerability in PostgreSQL Packages: CVE-2026-14662 8.8 high 16.15-r0 13 Aug 2026
Type Confusion Vulnerability in PostgreSQL Module 'refint' - Execute Arbitrary Code 8.8 high 16.15-r0 13 Aug 2026
Heap Buffer Overflow in PostgreSQL - CVE-2026-14664 8.8 high 16.15-r0 13 Aug 2026
Heap Buffer Overflow Vulnerability in PostgreSQL Packages 8.8 high 16.15-r0 13 Aug 2026
Heap Buffer Overflow Vulnerability in PostgreSQL Packages: CVE-2026-14669 8.8 high 16.15-r0 13 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 postgresql16

Is postgresql16 safe to use?

Vulert records 27 vulnerabilities for postgresql16 in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 27 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 postgresql16 have?

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

27 vulnerabilities were recorded for postgresql16 in the last 12 months, and the oldest entry in this database dates to 13 Aug 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 postgresql16 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 postgresql16 for upcoming vulnerabilities?

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