PostgreSQL security update fixes 52 vulnerabilities, ends support for PostgreSQL 14
PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 released with 52 security fixes.
The PostgreSQL Global Development Group has released several updates, including PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25, which collectively address 52 security vulnerabilities and over 140 other bugs. Many of the code execution flaws are memory errors or type confusion issues. Additionally, PostgreSQL 14 has reached its end-of-support, with version 14.25 being its final release.
AI summary of the linked source. Not reviewed by an editor. How this works
Run PostgreSQL?
Get an email when a new story names PostgreSQL, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonThe PostgreSQL Global Development Group released critical updates addressing 52 vulnerabilities, many of which are memory errors and type confusion issues that could allow code execution. Organizations running unpatched or end-of-life versions of PostgreSQL (particularly version 14, which has now reached end-of-support) are exposed to these risks with no future fixes available. The end-of-life status of PostgreSQL 14 means any newly discovered vulnerabilities in that branch will remain permanently unpatched, making upgrade planning a business-critical priority. Databases are high-value targets because they store sensitive data, and remote code execution flaws in database engines can lead to full system compromise and data breaches.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Cyber asset inventory
You cannot patch, monitor or protect the devices, cloud resources and accounts you do not know you have.