Stack Audit: RabbitMQ's 10-Advisory Security Drop, Keycloak 26.7.1, Authentik 2026.8, Better Auth 1.7, and Prisma ORM 8 RCs — August 16-19, 2026
Between August 16 and August 19, 2026, ten teams shipped code that touches almost every layer of a modern web stack: a ten-advisory security drop from RabbitMQ, a major version of Authentik, breaking changes in Better Auth 1.7, three release candidates of Prisma ORM 8, and quieter-but-real patches from Docker, Cloudflare, Astro, SvelteKit, Fastify, and Laravel. Below is a section-by-section audit of what actually changed, sourced directly from official changelogs, GitHub releases, and security advisories — with links so you can verify every claim yourself.
TL;DR: The Six Things Worth Your Attention
- RabbitMQ published ten security advisories in one day, the worst an unauthenticated Web STOMP memory-exhaustion bug rated CVSS 8.2 — see RabbitMQ Security Advisories.
- Keycloak 26.7.1 and Authentik 2026.8.0 both landed CVE fixes and, in Authentik's case, a Rust rewrite of its proxy outposts plus new PAM support — see authentik 2026.8.0.
- Better Auth 1.7.0/1.7.1 is a breaking-change release: account identity is now scoped by `(issuer, accountId)`, PKCE is mandatory for Electron, and the MCP plugin moved to its own package — see the v1.7.0 release notes.
- Prisma ORM 8 moved through three release candidates in two days, retiring the `prisma-next` binary and finalizing the config-file migration — see the Prisma changelog.
- Fastify patched two moderate advisories same-day — a schema-validation bypass and an X-Forwarded-* trustProxy spoofing issue — in v5.12.1, via Fastify's security advisories.
- Docker, Astro, SvelteKit, Laravel, Hono, and Podman all shipped stable patch releases in the window; details are in their sections below.
Containers, Edge & Infrastructure
Docker (Engine, Compose, Desktop)
Docker Desktop 4.87.0 shipped August 17, bundling Docker Agent v1.122.0, Buildx v0.36.1, and Compose v5.4.0, with fixes for in-app update errors, proxy diagnostics, and Windows WSL error recovery. The same day, Compose v5.5.0 added image-digest reconciliation to stop unnecessary container recreation and made `compose pull` honor `pull_policy` refresh windows more precisely.
services:
api:
image: myorg/api:latest
pull_policy: always # v5.5.0 now respects refresh windows on `compose pull`Worth noting as context: Docker Desktop 4.86.0 (August 10) patched CVE-2026-17106, a destination-escape flaw in `docker container cp` that could allow arbitrary file overwrites — confirm you're on 4.86.0 or later.
Cloudflare (Workers, Pages, KV, R2)
- R2 added a `us` jurisdiction (Aug 17) guaranteeing data stays within US boundaries for compliance-sensitive workloads.
- A WAF managed-rule update shipped for CVE-2026-65640 (a WordPress core RCE), with five more rules — including HTTP/2 request-smuggling and XSS coverage — scheduled for August 24.
- Cloudflare Tunnel origin application settings (HTTP/TLS/Connection) are now configurable directly from the dashboard (Aug 18).
- Workers AI added Qwen 3.8 27B (vision-language, 262K-token context), and Email Security SMTP gained post-quantum hybrid key exchange (X25519MLKEM768).
Vercel (Next.js hosting, Serverless, Edge Functions)
- Vercel for Platforms can now deploy directly from users' GitHub repos using short-lived, non-persisted tokens (Aug 18).
- Vercel KMS entered Public Beta — sign JWTs from Functions using managed keys and OIDC, with no private-key management required.
- Cursor's Origin repo-deploy integration reached public beta for automatic Preview/Production deploys.
Kubernetes & Podman
- Two CSI driver path-traversal CVEs are worth patching now: CVE-2026-3865 (SMB) and CVE-2026-3864 (NFS) — a malicious `subDir` value could delete unintended directories on the backing server.
- ingress-nginx disclosed CVE-2026-1580 and CVE-2026-24512/24513/24514 (up to CVSS 8.8) — upgrade to v1.13.7 or v1.14.3+.
- Podman v5.8.6 fixed CVE-2026-19730, where `podman quadlet install --replace` failed to truncate the target file, leaving stale content behind.
- Podman v6.1.0 (the current stable line) added `podman volume rename` and `podman machine restart`, and separately fixed a Buildah build-security issue, CVE-2026-44517, where a malicious Git repo or tar archive referenced in `ADD`/`COPY` could write files outside the build context.
Cloud Platforms: AWS, Railway, Render
AWS's weekly roundup (Aug 17) covers EC2 Application Status Checks (detects app-level failures like a stopped web server or Docker daemon), an IAM Role Manager that auto-creates required roles when you enable supported services, and OpenAI's "Daybreak" models arriving on Bedrock for defensive security research. Railway and Render had no changelog activity independently verifiable inside this window.
Identity & Authentication (IAM)
Keycloak
Keycloak 26.7.1 fixes 12 CVEs. The two most serious: CVE-2026-15572 (CVSS 8.8), a Dynamic Client Registration protocol-mapper type-swap that enables privilege escalation to realm admin, and CVE-2026-16102, where the default DCR policy allows role forgery. It also closes an unnormalized-URI authorization bypass in PathMatcher (CVE-2026-15573) and two SAML broker flaws. If you run self-hosted Keycloak with DCR enabled, this is a same-week upgrade.
Authentik
authentik 2026.8.0 (Aug 18) is a major release: PAM (privileged access management), agent accounts, multi-account browser switching, scheduled user offboarding, OAuth2 token exchange and dynamic client registration, and a Rust rewrite of the server/proxy outposts. Two breaking changes to plan for: the `hash_password` CLI command no longer accepts a password argument, and WebAuthn's "prevent duplicate device" option has been removed.
Clerk & Auth0
- Clerk shipped biometric sign-in (Face ID/Touch ID/Android biometric) for Expo, iOS, and Android SDKs on Aug 17, using device-bound challenges that never leave the device.
- Auth0 launched Custom Rate Limits in Early Access (per-app RPS via API) on Aug 17, and Flexible Password Policy reached General Availability days earlier.
Better Auth
Better Auth v1.7.0/1.7.1 landed Aug 17–18 with real breaking changes: database joins are now stable, account identity is scoped by `(issuer, accountId)` instead of provider alone, the MCP plugin moved into a standalone `@better-auth/mcp` package, SCIM decoupled from the organization plugin, and PKCE (S256) is now mandatory for Electron. New protocol support includes OAuth device authorization grant (RFC 8628) and DPoP sender-constrained tokens (RFC 9449).
import { betterAuth } from "better-auth";
export const auth = betterAuth({
// v1.7: account matching now keys on (issuer, accountId) — re-check
// any custom account-linking logic that assumed provider-only matching
advanced: {
database: { joins: true }, // promoted from experimental to stable
},
});Auth.js (NextAuth)
No release activity in this window. Auth.js has been in maintenance mode under the Better Auth team since September 2025; its most recent release, a security-patch cycle covering OAuth state/nonce/PKCE cookie binding, shipped July 20, 2026.
Meta-Frameworks & Core Web Standards
Next.js & React
Next.js 16.3.1 (backported Turbopack, image, and cache fixes) remains current, with canary builds shipping daily through Aug 18 but no new stable tag inside this window. React core had no release; the latest is v19.2.8 from July 21.
Nuxt & Vue.js
Nuxt's latest is v4.5.2 (Aug 5); worth flagging as recent context, v4.5.1/v3.21.10 patched a critical server-side RCE (GHSA-9473-5f9j-94wq) in late July. Vue core is mid-release-candidate for 3.6, which completes Vapor Mode and rewrites reactivity on `alien-signals` for 20–50% smaller Vapor-only bundles; rc.4 landed Aug 14.
SvelteKit & Svelte
SvelteKit 2.70.3 shipped Aug 18, fixing eager reads of `$app/state` dependencies during module init. The SvelteKit 3.0 preview channel is active in parallel, relocating remote-function types and moving `RequestEvent`/`Cookies` to new modules — a breaking change for preview users only. Svelte core is unchanged since 5.56.9 (Aug 12).
Astro
Astro 7.2.3 and its ecosystem packages (`@astrojs/vercel` 11.0.6, `@astrojs/node` 11.1.3, `@astrojs/mdx` 7.0.6) released Aug 18, fixing a memory leak with chunked collection storage, dev-server route matching after page changes, malformed Host-header port handling, and a Vercel server-islands 404 regression.
Backend Frameworks & Runtimes
NestJS & Node.js
NestJS v11.2.1 (Aug 14) fixed an early-return SSE abort issue; v11.2.0 the same day added HTTP QUERY method support (RFC 10008). Node.js's most recent release is v26.7.0 (Aug 5); its most recent security release, v26.5.1/24.18.1/22.23.2, patched a Permission Model path-allowlist bypass on July 29 — nothing new for Node in this window.
Fastify & Express
Fastify published two moderate security advisories on Aug 18, patched same-day in v5.12.1: a schema-validation bypass via root primitive coercion mismatch, and X-Forwarded-* header spoofing under `trustProxy` hop-count handling. If you rely on `trustProxy` for client-IP resolution behind a load balancer, upgrade and re-verify your hop-count configuration.
import Fastify from "fastify";
const app = Fastify({
// v5.12.1: verify hop-count matches your actual proxy chain depth
// to avoid X-Forwarded-* spoofing from client-controlled headers
trustProxy: 1,
});Express core had no release (still v5.2.1), but its `body-parser` dependency shipped 1.20.6/2.3.0 on July 31 for CVE-2026-12590, a DoS where an invalid `limit` value silently disabled size enforcement.
ElysiaJS & Hono
ElysiaJS has had no release since June 16. Hono v4.13.3 shipped Aug 18, fixing client `replaceUrlParam` URL corruption with `$` tokens, ETag handling, CORS header management, and wildcard route matching.
FastAPI & Django
FastAPI's latest is 0.141.1 (Jul 29); Django's latest is 6.0.8/5.2.17 (Aug 4), which fixed four CVEs including CVE-2026-15830, a DoS via geometry processing. Neither shipped anything in this window.
Laravel
laravel/framework v13.26.0/v13.26.1 shipped Aug 18 with roughly 47 changes — including a `JobReleased` queue event, a global queue-pause switch, Redis cluster improvements, and Guzzle 8 support — followed same-day by v13.26.1, which reverted a same-day Eloquent addition. The v12.67.0 LTS line also released Aug 18 with validation-rule fixes; note that Laravel 12's bug-fix window closed Aug 13, though security fixes continue through February 2027.
UI Systems, Styling & Motion
This corner of the stack was quiet for the window itself. shadcn/ui's CLI last published Aug 13 (`[email protected]`); Radix UI's last release was July 24; Tailwind CSS remains at stable v4.3.3 (July 16) with nightly insiders builds but no new stable tag; Material UI's latest is v9.3.1 (Aug 6), which fixed stuck exit transitions; and Motion (Framer Motion) last published `13.1.0` on Aug 10. None had security advisories in this window.
Databases, Caching & Vector Search
PostgreSQL & pgvector
The most significant database security event landed just before this window: PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 released Aug 13, fixing 28 CVEs up to CVSS 8.8 — including CVE-2026-14664 and CVE-2026-14680, both heap buffer overflows reachable via `regexp` and type-confusion paths that can lead to remote code execution. If you haven't patched yet, this is a priority. pgvector's latest, v0.8.6 (Jul 29), fixed a 32-bit IVFFlat build buffer overflow.
Redis
Redis Open Source 8.2.9 is a security release fixing CVE-2026-62356, a miscalculated buffer size in `CMSketch` RDB loading that causes a heap out-of-bounds write. It also closes an ACL key-permission bypass reachable via `SORT`/`GEORADIUS`/`XREAD`, and a malicious RDB `SLOT_INFO` payload that could corrupt memory. Anyone loading untrusted RDB files should upgrade immediately.
MongoDB
A security advisory published Aug 11–12 (mirrored by Canada's Centre for Cyber Security as AV26-810) affects MongoDB Server prior to 7.0.40, 8.0.29, 8.2.13, and 8.3.8, plus the MongoDB Driver prior to 5.9.2: an intra-cluster SASL mechanism allow-list was missing from egress connection setup, allowing a PLAIN-mechanism downgrade and cleartext keyfile disclosure between cluster members.
ClickHouse & DuckDB
ClickHouse's last minor line release was v26.7 (July 22), though LTS patch builds `v26.3.19.3-lts` and `v26.3.18.32-lts` tagged Aug 17–18 with routine backported fixes and no identified CVEs. DuckDB remains at v1.5.5 (July 21); it crossed 40,000 GitHub stars on Aug 5, with v2.0 slated for fall 2026.
Database Tools, ORMs & BaaS
Prisma ORM
Prisma ORM 8 moved through three release candidates in this window. v8.0.0-rc.2 (Aug 17) retires the `prisma-next` binary in favor of a unified CLI, reverts default aggregates to plain JS numbers (lossless variants remain available), and makes CHECK constraints part of the declared schema contract. v8.0.0-rc.4 (Aug 18) closes out the legacy ORM-config transition — anyone still on the old config format needs to rename config files and wrap options in `definePrismaConfig` before upgrading to stable.
import { definePrismaConfig } from "prisma/config";
export default definePrismaConfig({
// Prisma 8 removes fallback support for the legacy config format —
// wrap all CLI options here before upgrading past rc.4
schema: "./prisma/schema.prisma",
});Drizzle ORM, Supabase & Firebase
No verifiable activity inside this window for any of the three. Drizzle remains at v1.0.0-rc.4 (June 27) with v1 stable still unreleased; Supabase's nearest changes are the Aug 5 Postgres extension version-pinning deprecation and the self-hosted gateway switch from Kong to Envoy; Firebase's latest JS SDK is v12.17.1 (Aug 4).
Background Jobs, Messaging & Task Queues
RabbitMQ
RabbitMQ published ten security advisories simultaneously on Aug 18. The headline is GHSA-cfqc-c682-93mm, a High-severity (CVSS 8.2) Web STOMP flaw: an unauthenticated attacker can force decompression of up to 100 MiB per connection before authentication, exhausting broker memory. It affects 4.2.0–4.2.9 and 4.3.0–4.3.4, fixed in 4.2.10/4.3.5. A second advisory, GHSA-3526-xvv4-q9mr (Moderate, CVSS 5.9), lets an authenticated admin chain three behaviors into BEAM VM code execution without the Erlang cookie. If you run Web STOMP publicly, patch today.
# Check your current version, then upgrade to the fixed line for your series
rabbitmqctl version
# Fixed: 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5BullMQ
BullMQ's v6.x line kept a fast cadence: v6.1.0 (Aug 12) added explicit schema migrations for the new Postgres backend, v6.1.1 (Aug 14) fixed a flow parent-options bug, and v6.1.2 (Aug 16) shipped a dependency security patch — see the BullMQ changelog.
Kafka & Temporal
No activity in this window for either. Kafka's one recent high-severity issue, CVE-2026-35554 (a producer buffer-pool race condition causing silent cross-topic message misrouting), was disclosed back in April. Temporal's most recent news — Serverless Workers for AWS Lambda and Google Cloud Run reaching preview — landed Aug 3–7, just before this window.
What to Patch First
If you only act on five things from this audit, make it these, roughly in priority order:
- RabbitMQ — upgrade off any 4.2.0–4.2.9/4.3.0–4.3.4 install exposing Web STOMP (CVSS 8.2, unauthenticated).
- Redis — upgrade to 8.2.9 if you load RDB files from any untrusted or semi-trusted source (CVE-2026-62356).
- PostgreSQL — confirm you're on 18.6/17.11/16.15/15.19/14.24 or later; two of the 28 fixed CVEs are RCE-class.
- Keycloak — move to 26.7.1 if Dynamic Client Registration is enabled anywhere in your realms.
- Fastify — upgrade to 5.12.1 and re-check your `trustProxy` hop-count if you sit behind a load balancer.
Everything else in this audit is feature work or routine patching — worth knowing about, but not a fire drill. We'll be back tomorrow with the next 24 hours across the same stack.
Comments
Share your thoughts and join the conversation

