Source
Release notes, security advisories, and design decisions for the framework this portal itself runs on.
Vercel shipped Next.js 16.4 on October 6, 2026. Cache Components, the opt-in caching model built over the 16.x line, is now the recommended choice for every app and the default in new projects. The release adds a way to force a route to stay static, two APIs that keep content out of prefetches, an agent-driven upgrade command, React 19.3, and a smaller Turbopack cache.
Next.js Blogverified
Next.js published its September security release on September 30, 2026. Versions 16.3.8 and 15.5.27 close one high, five medium, and one low severity vulnerability, from server-side request forgery in image optimization to cache poisoning on self-hosted sites. Two more fixes, one critical and one high, are held for a later release while an upstream dependency catches up. If you self-host, most of the list applies to you.
Next.js Blogverified
The Next.js team announced on September 23, 2026 that versions 16.3.7 and 15.5.27 will ship on September 30, 2026. The release addresses nine vulnerabilities, one of them rated critical. The advisories that describe them appear only with the release. It follows the out-of-band 16.3.6 by eight days, so many projects will upgrade twice in the same month.
Next.jsverified
The out-of-band release is available as 16.3.6 on Active LTS and 15.5.26 on Maintenance LTS. Versions from 16.2.0 up to but not including 16.3.6 are affected through the Node.js ImageResponse implementation in next/og, where improper escaping in Satori's SVG output can lead to remote code execution. Applications on the Edge implementation are not affected, and Next.js 15.x does not carry the remote code execution issue at all. The fix works by upgrading the upstream dependencies, Satori among them.
Next.jsverified
Vercel says a critical security issue has been found in a package that Next.js pulls in. Patched releases 16.3.6 and 15.5.26 are due in an out-of-band update on September 22, 2026. The advisory that spells out impact and affected versions appears only alongside those releases. Until it does, nobody running the framework can size up their own exposure.
Next.jsverified