Skip to content
Oday Bakkour
Back to Knowledge Hub

PostgreSQL Patches 52 CVEs, Node.js Fixes 16: Dev Stack Release Audit, Week of November 9, 2026

Part of Dev Stack Release & Security Audit, a recurring series.

Oday Bakkour profile photo
Oday Bakkour
9 min read
Share

Executive Summary

This is the first weekly edition of the series. It covers releases from Monday, November 9 to Sunday, November 15, 2026, and it starts with what you need to patch.

  • Patch PostgreSQL now. PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 shipped on November 12. They fix 52 CVEs, many rated CVSS 8.8 for arbitrary code execution, and more than 140 bugs. Several index-corruption fixes require a manual REINDEX after the upgrade. PostgreSQL 14 is now end-of-life.
  • Patch Node.js now. The November 11 security release fixed 16 CVEs, seven rated High, mostly in HTTP/2 and TLS. The fixed versions are v26.13.1, v24.22.3 and v22.23.5.
  • Hono 4.13.18 fixes four GHSA advisories in validator(), bodyLimit(), mount() and serveStatic().
  • MongoDB Node driver 7.9.0 fixes CVE-2026-126835: OIDC bearer tokens could be sent to hosts outside your allowlist. Versions 6.7.0 up to 7.9.0 are affected.
  • Laravel 12.72.0 fixes a temporary signed URL expiration bypass, and Laravel 13.41.0 and 13.42.0 shipped the same day.
  • Better Auth 1.7.19 to 1.7.25 shipped seven patch releases with OAuth, DPoP and SAML hardening and several required schema migrations.
  • Breaking defaults: NestJS 12.5.0 lowers the WebSocket max payload from 100 MB to 1 MB and binds TCP microservices to localhost by default. FastAPI 0.162.6 drops Python 3.10.
  • Coming up: PostgreSQL 19 GA is planned for November 19, 2026.

1. Act now: runtime and database security

PostgreSQL: 52 CVEs and a mandatory reindex check

The November 12 release is the largest PostgreSQL security update I have tracked in this series. Most of the 52 CVEs need an authenticated SQL user, but many of them lead to arbitrary code execution as the server process. Examples:

  • CVE-2026-6460 (CVSS 8.8): type confusion after ALTER ... SET DATA TYPE executes arbitrary code.
  • CVE-2026-14661 (CVSS 8.1): dblink and subscriptions can append to arbitrary files.
  • CVE-2026-116318 (CVSS 8.8): a crafted not-null constraint name allows SQL injection through pg_dump.
  • CVE-2026-116314 (CVSS 8.8): pg_restore executes arbitrary code because it does not validate non-plain archives.
  • CVE-2026-120145 (CVSS 8.8): logical replication can write to subscriber system catalogs.
  • CVE-2026-120154 (CVSS 4.3): INSERT ... ON CONFLICT can read rows despite row security policies. This matters if you rely on RLS, for example with Supabase.

Seven CVEs are in plperl and one is in pltcl. If you do not use those extensions, remove them.

The minor upgrade only swaps binaries. You do not need a dump/reload or pg_upgrade. The bug fixes are the part that needs work: corruption fixes in GIN indexes, pg_trgm GiST indexes, TOAST tables reindexed concurrently, and B-tree indexes on unlengthed bpchar columns can leave existing indexes wrong. After you upgrade:

post-upgrade-checks.sql
-- 1. Reindex GIN indexes and pg_trgm GiST indexes (gist_trgm_ops) you suspect are corrupt
REINDEX INDEX CONCURRENTLY your_gin_index;

-- 2. Tables throwing "missing chunk number" errors (also reindexes the TOAST table)
REINDEX TABLE CONCURRENTLY your_table;

-- 3. Find NOT NULL NO INHERIT constraints on partitioned tables (now disallowed)
SELECT conrelid::regclass, conname
FROM pg_constraint
WHERE contype = 'n' AND connoinherit
  AND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');

If you use incremental backups, take a new full base backup after the upgrade. For Docker, the official image tags 18, 17, 16, 15 and 14 were rebuilt this week, and so were the pgvector images (0.8.7-pg18 and others). A docker compose pull followed by a restart picks them up.

PostgreSQL 14.25 is the final release of the 14 line. If you are still on 14, plan the major upgrade now. PostgreSQL 19 lands on November 19.

Node.js: 16 CVEs across HTTP/2 and TLS

The pre-announced Node.js security release shipped on November 10 and 11 as v26.13.1, v24.22.3 and v22.23.5. The High-severity fixes that matter most for web servers:

  • CVE-2026-123864: a zero-length TLS write re-enters llhttp_execute(), which causes a use-after-free that can leak heap memory into HTTPS response bodies. All three lines are affected. Cleartext node:http is not.
  • CVE-2026-123866 and CVE-2026-123874: HTTP/2 stream teardown use-after-frees can send freed heap memory to the peer.
  • CVE-2026-123863 and CVE-2026-123865: remote HTTP/2 process crashes and file-descriptor leaks.
  • CVE-2026-123872: TLS 1.2 renegotiation lets a client change the servername and bypass client-certificate policy for another hostname.
  • CVE-2026-126051: a remotely triggered uncaught exception in TLS servers that use SNICallback, OCSPRequest or server.addContext().

The release also updates llhttp, undici (24.x and 26.x) and sqlite (22.x and 24.x). There is no workaround, so upgrading is the fix. Next.js, NestJS, Fastify, Express and Hono-on-Node all inherit these fixes from the runtime and need no framework change.

Dockerfile
# Pin the major, not the patch, so a rebuild picks up security releases
FROM node:24-slim
rebuild.sh
# Refresh the base layer, then confirm the patched runtime
docker build --pull --no-cache -t app:latest .
docker run --rm app:latest node --version   # expect v24.22.3 or later

The official node images already carry 24.22.3 and 22.23.5.

2. Patch this week: framework, driver and auth advisories

Hono 4.13.18

Hono 4.13.18 (November 11) fixes four advisories, and the maintainers strongly encourage upgrading:

  • GHSA-92p4-j3wq-jmqx: validator('json') and validator('form') could validate an empty object while the handler read the real body, triggered by a malformed Content-Type such as a trailing ;. This completes an earlier fix.
  • GHSA-39q9-qp46-w8xg: bodyLimit() memory exhaustion when a body arrives in many tiny chunks.
  • GHSA-h25j-2p75-qj33: app.mount() with a custom getPath could skip middleware scoped to the mount prefix. This was a regression in 4.13.16 and 4.13.17.
  • GHSA-74fm-fwc7-3fwp: serveStatic() with allowPercentInPath: true double-decoded paths and could bypass middleware.
terminal
npm install [email protected]

MongoDB Node.js driver 7.9.0

mongodb 7.9.0 (November 12) fixes CVE-2026-126835: OIDC bearer tokens could be sent to domains outside the application's allowlist. Versions 6.7.0 up to 7.9.0 are affected. MongoClient now throws if you set both the ENVIRONMENT auth property and an OIDC callback. The release also stops forcing autoSelectFamily: true, so Node's process default now applies. If your containers have broken IPv6, check connection behavior after upgrading.

If you cannot upgrade right away, the release notes give this mitigation:

db.ts
// Mitigation for mongodb >=6.7.0 <7.9.0 when using OIDC callbacks
const uri = process.env.MONGODB_URI!;
if (/authMechanismProperties=[^&]*ENVIRONMENT/i.test(uri)) {
  throw new Error("Refusing MONGODB_URI with ENVIRONMENT alongside an OIDC callback");
}

Mongoose users get the new driver through mongoose 9.12.1 and 8.24.9. Check which mongodb version your lockfile resolves to. On the Python side, PyMongo 4.20.0 also shipped on November 12.

Laravel 12.72.0, 13.41.0 and 13.42.0

Laravel 12.72.0 (November 10) contains security fixes:

  • A temporary signed URL expiration bypass using a numeric query-fragment parameter (#62401).
  • How expires is read from QUERY_STRING and VAPOR_RAW_QUERY_STRING (#62349, #62391).
  • Stricter RFC 5321 email address validation (#62347).

Laravel 13.41.0 and 13.42.0 were tagged the same day, but their GitHub release pages and the 13.x changelog list no entries, so I could not confirm which fixes they include. The previous release, 13.40.0, fixed task output injection in the Concurrency process result envelope (#62297). If you use URL::temporarySignedRoute() for downloads or password flows, upgrade to the latest release on your line.

terminal
composer update laravel/framework --with-all-dependencies

Better Auth 1.7.19 to 1.7.25

Better Auth shipped seven patch releases in five days. No GHSA IDs were published, but several changes are security hardening:

  • 1.7.21: revokes in-flight opaque access tokens when refresh-token reuse or a replayed authorization code is detected. It also tightens SAML replay protection and stops SIWE 401 responses from leaking internal errors.
  • 1.7.23: failed PKCE, redirect_uri, resource or DPoP checks no longer consume the authorization or device code.
  • 1.7.25: fixes introspection reporting valid JWT access tokens as inactive.

Before you upgrade:

  • 1.7.20: if your issuer runs on http behind a TLS-terminating proxy, set baseURL to the public https URL.
  • 1.7.21: SCIM needs an adapter with native transactions. update on non-unique filters should move to updateMany. Errors thrown from sendVerificationEmail no longer block sign-up.
  • 1.7.23 and 1.7.24: multi-instance or serverless deployments need a shared dpop.replayStore, and endpoints that accept DPoP-bound tokens should call enforceDpopBinding.

Several releases add columns, so run the migration:

terminal
npm install [email protected]
npx auth@latest migrate   # or: npx auth@latest generate for Prisma/Drizzle

The 1.8.0 betas (beta.7 to beta.10) bring RFC 8693 token exchange and stricter DPoP and One Tap nonce rules. Wait for the stable release.

3. Breaking defaults to review

NestJS 12.5.0 and 11.2.10

NestJS 12.5.0 (November 12) is a minor release, but it changes defaults that can break production traffic:

  • WebSocket max payload goes from 100 MB to 1 MB.
  • TCP microservice maxBufferSize goes from 128 Mi to 16 Mi characters.
  • A TCP server with an empty or unset host now listens only on localhost. In containers, set host: '0.0.0.0' explicitly or other services will not reach it.
  • Multipart requests default to 1000 parts.
  • Guards, interceptors and pipes that cannot be resolved now fail at startup instead of at request time.

These are denial-of-service hardening changes, and I think the new defaults are right. Test any gateway that receives large frames, and upgrade @nestjs/core together with the platform packages. The 11.x line got 11.2.9 (Multer 2.5.0 for GHSA-q7qp-rjg7-q26m and Fastify 5.12.8) and 11.2.10 (validation and SSE hardening).

FastAPI 0.162.6 to 0.163.1

FastAPI 0.162.6 drops Python 3.10 (PR #16737). If your base image is python:3.10-slim, pin fastapi<0.162.6 until you move the interpreter. FastAPI 0.163.0 adds dependency concurrency limits through Depends(max_concurrency=...) (PR #16746). Here is the signature from the changelog. Read the docs for the exact semantics before you rely on it as a connection-pool guard:

main.py
from typing import Annotated
from fastapi import Depends, FastAPI

app = FastAPI()

async def get_conn(): ...

@app.get("/items")
async def read_items(conn: Annotated[object, Depends(get_conn, max_concurrency=5)]):
    ...

The same release ships an official agent skill, installed with uvx library-skills.

Elysia: npm latest tag fixed

Elysia 2.0.0-rc.4 had briefly taken npm's latest tag. Elysia 1.4.32 (November 11) only restores 1.4.x as latest. If a fresh install between November 8 and 11 gave you 2.0.0-rc.4, pin elysia@^1.4.32.

4. Routine releases worth knowing

Tool Version (date) What changed
Next.js 16.4.6 (Nov 9) Backport release: route handler responses are now compressed automatically, Turbopack dev GC fixes, and create-next-app pins Tailwind 4.3.3. Not a security release.
SvelteKit 3.2.0 (Nov 10) Clickable remote-function links in dev logs, __data.json 404 returns JSON, plus adapter-node 6.0.2 and adapter-vercel 7.0.3 (accepts Node 26+).
Astro 7.4.8 to 7.4.12 (Nov 9 to 13) 7.4.12 lowers astro build memory by releasing content collection entries after sync, and unpins @astrojs/* dependencies.
Motion 14.11.0 to 14.14.0 (Nov 9 to 13) Four minor releases in one week. Read the changelog before you upgrade animation-heavy pages.
BullMQ 6.7.3 to 6.7.6 (Nov 10 to 12) Deduplication keys are removed with their parent job, paused Postgres queues count waiting jobs, and job errors are recorded on telemetry spans.
Wrangler 4.159.0 to 4.162.0 (Nov 9 to 13) Steady weekly cadence. @cloudflare/workers-types publishes daily.
Vercel CLI 65.14.0 to 65.16.0 @vercel/functions 3.11.3.
Clerk @clerk/nextjs 7.10.0, @clerk/backend 3.29.0 (Nov 14) Minor releases. 6.x and 2.x also got backports on Nov 11.
Auth0 Node SDK 7.8.0 (Nov 12) Plus 5.14.2 and 4.37.2 maintenance releases.
Firebase JS SDK 13.3.0 (Nov 11) firebase-admin 14.5.1 (Nov 12).
Supabase CLI 3.1.0 (Nov 9) New minor release of the 3.x CLI.
Temporal Python SDK 1.36.0 and 1.36.1 (Nov 11 and 14) New minor release. The TypeScript SDK stays on 1.25.0.
Prisma 8.0.0-rc.33 Prisma 8 is still in release candidates. Stable @prisma/client stays on 7.10.1.

5. Quiet this week

No new stable releases from Nov 9 to Nov 15: React (19.3.1), Vue (3.5.45), Nuxt (4.6.4), Svelte (5.57.3), Tailwind CSS (4.3.5, v4.4 prereleases only), MUI (9.5.0), shadcn (4.23.0), Radix UI, Express (5.3.0), Fastify (5.12.8), Drizzle ORM (0.45.4), Auth.js (next-auth 4.24.15), Django (6.1.3) and the Temporal TypeScript SDK.

  • Keycloak: 26.8.2 shipped on November 5, before this window. The only release this week was Keycloak Client Libraries 26.0.13 on November 12.
  • Authentik: the latest is 2026.8.5 from October 21.
  • Redis: the security releases (8.8.4, 8.6.8 and others) came out on October 26. This week only brought 8.12 RC3, which fixes TLS session resumption across listeners.
  • Docker Engine: 29.9.3 (November 3, with four CVE fixes and BuildKit 0.34.2) is still current. 29.10.0 is at rc.2.
  • Kubernetes: a monthly patch release was scheduled for November 10, but I could not confirm the published versions this week.

My patch order for this week

  1. PostgreSQL minor upgrade, then the reindex checks.
  2. Rebuild every Node.js image with --pull.
  3. Hono, the MongoDB driver and Laravel, in whatever order matches your stack.
  4. Better Auth with migrations, tested in staging.
  5. NestJS 12.5.0 and FastAPI 0.163.x only after testing the new defaults.

Sources

Comments

Share your thoughts and join the conversation

Leave a Comment

Loading comments...
RELATED