Vulnerability Database · Debian · postgresql-common · Version

postgresql-common 134wheezy4

134wheezy4 is affected by 2 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 0 Medium 0 Low 0 Unrated 2

Database updated 23/Oct/2026

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 Vulnerabilities affecting this version

postgresql-common 134wheezy4 vulnerabilities

2 vulnerabilities cover postgresql-common 134wheezy4. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Security Vulnerability in postgresql-common N/A unrated 134wheezy6 11 Nov 2017
Security Vulnerability in postgresql-common N/A unrated 134wheezy5 01 Jan 2017

Looking for another version, or everything Vulert holds for postgresql-common?

All versions → Full vulnerability list →

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-common 134wheezy4

Is postgresql-common 134wheezy4 vulnerable?

Yes. 2 vulnerabilities in the Vulert database cover postgresql-common 134wheezy4: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. Each entry above names the fixed version to move to.

How do I monitor postgresql-common for upcoming vulnerabilities?

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