VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

postgresql-17: vulnerability history, versions and safety

postgresql-17 is a package in the Debian ecosystem. Vulert records 3 vulnerabilities for it across 6 releases, from Feb 2026 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
3 vulnerabilities recorded U3
i
2 with no fix published

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

See the unfixed vulnerabilities →
i
3 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-17 vulnerabilities

Vulert verdict on postgresql-17 i

Updated on 23 Oct 2026

Careful: 2 of the 3 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 3 vulnerabilities on record across 1 year, 3 in the last year.

What to do: Plan around the 2 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 3 over 1 year · 3 in the last year i
  • Latest disclosure 14 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 2 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-17, 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
17.9-0+deb13u1 U2 No Details →
17.8-0+deb13u1 U2 No Details →
17.7-0+deb13u1 U3 No Details →
17.6-1 U3 No Details →
17.6-0+deb13u1 U3 No Details →
17.5-1 U3 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for postgresql-17

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Security Update for PostgreSQL-17: Addressing Multiple Vulnerabilities N/A unrated 17.8-0+deb13u1 12 Feb 2026
Critical Vulnerability in PostgreSQL Packages: CVE-2026-6476 N/A unrated No fix published 14 May 2026
Critical Vulnerability in PostgreSQL Packages: CVE-2026-6638 N/A unrated No fix published 14 May 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 postgresql-17

Is postgresql-17 safe to use?

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

How many vulnerabilities does postgresql-17 have?

3 vulnerabilities are recorded for postgresql-17 in the Debian ecosystem: 0 critical, 0 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 postgresql-17 vulnerabilities disclosed?

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

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