# Next.js November 2026 security release: are you affected, and how to patch (16.4.5 and 15.5.29)

Source: [DEV Community: javascript](https://dev.to/vishall/nextjs-november-2026-security-release-are-you-affected-and-how-to-patch-1645-and-15529-4oo2) · 2026-11-15 · Frontend
Page: https://themorning.dev/story/next-js-november-2026-security-release-are-you-affected-and-how-to-patch-16-4-5-fd0dec7d88c4166c
Kind: security · Impact: high

## In brief

- On 3 November 2026, the Next.js team released versions 16.4.5 and 15.5.29 to fix seven security issues.
- The most serious issue is a cache bug where data cached for one tenant or locale can be served to another in apps that use use cache.
- Four of the seven issues involve Cache Components and affect only apps that use them.

## Why it matters

Apps that use use cache can serve one tenant's or locale's cached data to another, so affected Next.js applications should check whether they are exposed and patch.

## What to do

- Upgrade to Next.js 16.4.5 or 15.5.29, depending on your release line

## Versions

- Next.js 16.4.5
- Next.js 15.5.29

## Timeline

- 2026-11-03: Next.js 16.4.5 and 15.5.29 released to fix seven security issues

## Coverage

- [Next.js November 2026 security release: are you affected, and how to patch (16.4.5 and 15.5.29)](https://dev.to/vishall/nextjs-november-2026-security-release-are-you-affected-and-how-to-patch-1645-and-15529-4oo2) — DEV Community: javascript, 2026-11-15

Tags: nextjs, security, caching, react, vulnerability

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
