← Search results
CVE-LINKED INVENTORY79 SECURITY RECORDS
Publisher not identified
postgresql
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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-2025-1094 | 13 Feb 2025 | 17 < 17.3; 16 < 16.7; 15 < 15.11; 14 < 14.16; < 13.19 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-10979 | 14 Nov 2024 | 17 < 17.1; 16 < 16.5; 15 < 15.9; 14 < 14.14; 13 < 13.17; < 12.21 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-10978 | 14 Nov 2024 | 17 < 17.1; 16 < 16.5; 15 < 15.9; 14 < 14.14; 13 < 13.17; < 12.21 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-10977 | 14 Nov 2024 | 17 < 17.1; 16 < 16.5; 15 < 15.9; 14 < 14.14; 13 < 13.17; < 12.21 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-10976 | 14 Nov 2024 | 17 < 17.1; 16 < 16.5; 15 < 15.9; 14 < 14.14; 13 < 13.17; < 12.21 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-7348 | 8 Aug 2024 | 16 < 16.4; 15 < 15.8; 14 < 14.13; 13 < 13.16; < 12.20 | ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination. The recommended immediate actions per product are listed below: - Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later. - End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker’s ability to com-promise the system. ABB recommends that customers apply the update at the earliest convenience. | Update reference ↗ |
| CVE-2024-4317 | 9 May 2024 | 16 < 16.3; 15 < 15.7; 14 < 14.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-0985 | 8 Feb 2024 | 16 < 16.2; 15 < 15.6; 14 < 14.11; 13 < 13.14; < 12.18 | ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination. The recommended immediate actions per product are listed below: - Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later. - End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker’s ability to com-promise the system. ABB recommends that customers apply the update at the earliest convenience. | Update reference ↗ |
| CVE-2023-2455 | 9 Jun 2023 | PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is running, it will be automatically restarted after installing this update. | Update reference ↗ |
| CVE-2023-2454 | 9 Jun 2023 | PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is running, it will be automatically restarted after installing this update. | Update reference ↗ |
| CVE-2022-41862 | 3 Mar 2023 | postgresql 5.2, postgresql 14.7, postgresql 13.10, postgresql 12.14, postgresql 11.19 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-1552 | 31 Aug 2022 | Fixed in postgresql 14.3, postgresql 13.7, postgresql 12.11, postgresql 11.16, postgresql 10.21. | 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-2022-2625 | 18 Aug 2022 | postgresql 14.5, postgresql 13.8, postgresql 12.12, postgresql 11.17, postgresql 10.22 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-23214 | 4 Mar 2022 | Affects v9.6 to v14 | 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-2021-3677 | 2 Mar 2022 | Fixedin v13.4, v12.8, v11.13 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-23222 | 2 Mar 2022 | Affects v9.6 to v14 | 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-2021-32028 | 11 Oct 2021 | postgresql 13.3, postgresql 12.7, postgresql 11.12, postgresql 10.17, postgresql 9.6.22 | 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-2021-32029 | 8 Oct 2021 | postgresql 13.3, postgresql 12.7, postgresql 11.12 | 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-2021-32027 | 1 Jun 2021 | postgresql 13.3, postgresql 12.7, postgresql 11.12, postgresql 10.17, postgresql 9.6.22 | 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-2021-3393 | 1 Apr 2021 | postgresql 13.2, postgresql 12.6, postgresql 11.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-10128 | 19 Mar 2021 | 11.x prior to 11.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-10127 | 19 Mar 2021 | 11.x prior to 11.3 | 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-2021-20229 | 23 Feb 2021 | postgresql 13.2, postgresql 12.6, postgresql 11.11, postgresql 10.16, postgresql 9.6.21, postgresql 9.5.25 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-25696 | 23 Nov 2020 | All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24 | 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-2020-25695 | 16 Nov 2020 | All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-25694 | 16 Nov 2020 | All PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24 | 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-2020-10733 | 16 Sep 2020 | 9.5, 9.6, 10, 11, 12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-14350 | 24 Aug 2020 | PostgreSQL versions before 12.4, before 11.9, before 10.14, before 9.6.19, and before 9.5.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-14349 | 24 Aug 2020 | PostgreSQL versions before 12.4, before 11.9 and before 10.14 | 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.