PostgreSQL

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at postgresql, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2018-1058	2 Mar 2018	9.3 - 10	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2018-1053	9 Feb 2018	9.3.x before 9.3.21; 9.4.x before 9.4.16; 9.5.x before 9.5.11; 9.6.x before 9.6.7; 10.x before 10.2	An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.	Update reference ↗
CVE-2018-1052	9 Feb 2018	10.x before 10.2	An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.	Update reference ↗
CVE-2017-7486	12 May 2017	8.4 - 9.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2017-7485	12 May 2017	9.3 - 9.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2017-7484	12 May 2017	9.2 - 9.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.