VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

postgresql-15: vulnerability history, versions and safety

postgresql-15 is a package in the Debian ecosystem. Vulert records 17 vulnerabilities for it across 20 releases, from Aug 2023 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded U17
i
8 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
9 in the last 12 months

Most recent disclosure 14 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all postgresql-15 vulnerabilities

Vulert verdict on postgresql-15 i

Updated on 23 Oct 2026

Careful: 8 of the 17 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 17 vulnerabilities on record across 2 years, 9 in the last year.

What to do: Plan around the 8 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 17 over 2 years · 9 in the last year i
  • Latest disclosure 14 May 2026 i
  • Highest CVSS 4.3 i
  • With no published fix 8 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-15, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2024 6
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for postgresql-15

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unauthorized Data Exposure in PostgreSQL 15 and 16: CVE-2024-4317 4.3 medium 15.7-0+deb12u1 14 May 2024
DSA-5553-1: PostgreSQL-15 Security Update N/A unrated 15.5-0+deb12u1 13 Nov 2023
DSA-5623-1: Security Update for postgresql-15 N/A unrated 15.6-0+deb12u1 14 Feb 2024
Critical Vulnerability in PostgreSQL Packages: CVE-2026-6637 N/A unrated No fix published 14 May 2026
PostgreSQL 15 Authorization Bypass Vulnerability in pg_stats_ext and pg_stats_ext_exprs N/A unrated 15.7-0+deb12u1 14 May 2024

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-15

Is postgresql-15 safe to use?

Vulert records 17 vulnerabilities for postgresql-15 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does postgresql-15 have?

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

9 vulnerabilities were recorded for postgresql-15 in the last 12 months, and the oldest entry in this database dates to 11 Aug 2023. 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-15 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-15 for upcoming vulnerabilities?

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