diff --git a/Dockerfile b/Dockerfile
index eb7f1643..d42b291c 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -28,7 +28,7 @@ RUN bun install --frozen-lockfile
 # between whichever ones are present. Every stage here is glibc, so the glibc
 # package is the one installed and the one loaded; keeping the stages on the
 # same base is what makes that hold.
-FROM node:26.7.0-trixie-slim AS builder
+FROM node:26.8.1-trixie-slim AS builder
 WORKDIR /usr/src/app
 COPY --from=deps /usr/src/app/node_modules ./node_modules
 COPY . .
@@ -49,7 +49,7 @@ RUN node scripts/copy-monaco.mjs && npx next build
 
 # Production image - use Node.js slim for lower memory footprint
 # trixie-slim: glibc must match the stage where native modules were built (see builder).
-FROM node:26.7.0-trixie-slim AS runner
+FROM node:26.8.1-trixie-slim AS runner
 WORKDIR /app
 
 ENV NODE_ENV=production
diff --git a/docs/DISTRIBUTION.md b/docs/DISTRIBUTION.md
index cac16b78..531ffc92 100644
--- a/docs/DISTRIBUTION.md
+++ b/docs/DISTRIBUTION.md
@@ -26,7 +26,7 @@ starting with the first release that includes the release-artifacts workflow —
 have Docker images only.
 
 > **Runtime note:** every channel here runs the production server under Node (`node server.js`),
-> including the Docker image — its runner stage is `node:24.16.0-trixie-slim` and `CMD` execs
+> including the Docker image — its runner stage is `node:26.8.1-trixie-slim` and `CMD` execs
 > `node server.js`; Bun is only used to install dependencies during the Docker build and for local
 > development (`bun dev`). The SQLite DB provider adapts to whichever runtime it finds
 > (`bun:sqlite` under Bun, `node:sqlite` under Node) — see
diff --git a/docs/providers/sqlite.md b/docs/providers/sqlite.md
index 75bae33c..c1a9f92b 100644
--- a/docs/providers/sqlite.md
+++ b/docs/providers/sqlite.md
@@ -51,7 +51,7 @@ for a web-based editor:
   connect time — see [Runtime & driver selection](#runtime--driver-selection). All packaged
   distribution channels — the official Docker image, `npx @libredb/studio`, the Homebrew tap, the
   `.deb`/`.rpm` packages, and the standalone tarballs — run the built app with `node server.js` (the
-  Docker image's runner stage is `node:24.16.0-trixie-slim`; the other channels bundle their own pinned
+  Docker image's runner stage is `node:26.8.1-trixie-slim`; the other channels bundle their own pinned
   Node 24 runtime), so they all use `node:sqlite`. `bun:sqlite` is used for local development
   (`bun dev`) and the test suite, where Next.js runs directly under Bun. Only on a runtime with
   neither driver does `connect()` throw a `DatabaseConfigError`.