{
  "id": 20414366,
  "title": "PostgreSQL patches 52 security holes, sends version 14 into retirement",
  "url": "https://urgent.news/2026/11/17/postgresql-patches-52-security-holes-sends-version-14-into-retirement-20414366",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T09:30:00.000Z",
  "source": {
    "name": "The Register",
    "slug": "the-register",
    "url": "https://www.theregister.com/databases/2026/11/17/postgresql-patches-52-security-holes-sends-version-14-into-retirement/5310108"
  },
  "original_language": "en",
  "account": "PostgreSQL developers have addressed 52 security vulnerabilities and over 140 bugs in updates from versions 14 to 18, along with a second release candidate for version 19. The update includes PostgreSQL 14.25, the final release for the unsupported version 14. Users are urged to upgrade to a newer major version. Following the patch, certain fixes may necessitate additional tasks, such as rebuilding affected indexes or creating a fresh full backup. Administrators are advised to refer to the release's post-update instructions. Alastair Turner, community technologist at Percona, emphasized the seriousness of high-severity code execution flaws, although exploiting them would require database access. He clarified that brute-force scanning of the correct port wouldn't suffice to discover these flaws, but SQL injection or credential theft could be more detrimental, as they open the door to remote, anonymous code execution. Among the fixes is CVE-2026-6460, a type confusion flaw that could enable a database user with object-creating permissions to execute arbitrary code. This flaw has a CVSS severity score of 8.8 out of 10. Turner attributed the surge in security discoveries to AI-assisted scanning and heightened scrutiny as PostgreSQL gains traction in enterprise computing. He highlighted this as a record number of CVEs fixed in a quarterly release, with no indication that this trend will cease. Turning to the list of CVE sources, it became evident that AI or brute force played a role, as providers like Anthropic and OpenAI open-source scanners were involved. Turner noted that the fixes encompassed various parts of the software, stating there isn't a single broken piece of code, but rather a broad base that required patching. It's also worth mentioning that this is the third consecutive quarterly release with a record number of CVEs patched. PostgreSQL 14 users must now face a major-version upgrade or operate without further security and bug fixes. Their chosen path might hinge on internal upgrade policies. Those requiring the preceding major release, known as N-1, should currently target PostgreSQL 17, as pointed out by Turner. Version 18 remains the latest generally available release until 19 makes its debut. PostgreSQL 19 is slated for general availability on Thursday, November 19, barring unexpected issues. It is anticipated to introduce a new REPACK command, featuring a CONCURRENTLY option that enables reads and writes to continue while reclaiming disk space. VACUUM FULL, on the other hand, necessitates an exclusive table lock, blocking reads and writes while it operates.",
  "summary": "Some fixes need more than installation, while the next major release is due November 19",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}