A patched application runs Next.js 16.4.1 or later on the 16.x line, or 15.5.28 or later on the 15.x line. Any 16.x release before 16.4.1 is affected. So is any release from 10.x through 15.x before 15.5.28. The version that counts is the one running in production, not the one written in a planning document.
Read the resolved version from the installed package tree. The version in the manifest file shows only a range, so it can hide an older copy.
Exposure depends on what the app does. Note whether it uses Cache Components, image optimization with SVG files, or Server Actions.
The Next.js team announced the release on October 8 and shipped it on October 14. Two fixes had slipped from the September security release while upstream projects coordinated. A national cybersecurity agency scored both Critical flaws at 9.5 out of 10 on the CVSS v4.0 scale.
App Router applications with Cache Components are affected when a function marked with the use cache directive returns multiple typed arrays. Attackers need no login. No workaround exists. The advisory ID is GHSA-673q-mjm6-r5xr.
A memory-related weakness in an upstream image library can let an attacker run code when Next.js processes SVG files on glibc-based Linux. It is tracked as CVE-2026-96889. Raising the sharp library to 0.35.5 or later works as a temporary measure. Dynamic Open Graph image routes may expose the same path.
This High severity flaw lets an attacker exhaust resources on App Router apps that define a Server Action. Autoscaling serverless platforms cope better than a single self-managed server. The advisory ID is GHSA-p3m5-59mp-jv5r.
Remote code execution lets an outsider run commands on your server. The results can include exposed customer records, website downtime, altered pages, and lost trust.
Regulated sectors may also face reporting duties after a breach.
Next.js 15.x reaches the end of its Maintenance LTS period around late October 2026, so teams on that line should plan a move to 16.x. Confirm dates on the official support policy page.
Ask for help when nobody owns dependency updates, when the app sits on an old release line, or when downtime would cost revenue.
A capable partner audits dependencies, reviews hosting settings, tests the deployment pipeline, and sets up security monitoring. Esight Solutions applies this review to client applications, covering the patch and the testing that proves nothing else broke. Request a written update plan and a rollback procedure from any provider.
A custom web application development company in Kochi can plan update schedules, dependency monitoring, and automated tests into a project from the start. Least privilege access and regular audits turn urgent patches into routine maintenance.
A web designing company in Kochi collaborating with programmers can ensure efficient, secure image processing and smooth performance of interactive visual elements.
It is patched if the running version is 16.4.1 or later on 16.x, or 15.5.28 or later on 15.x.
No. The use cache flaw needs Cache Components. The image flaw involves SVG processing on glibc-based Linux. The Server Action flaw needs a defined Server Action.
Delay is risky. Both Critical flaws allow remote code execution, and the use cache flaw needs no authentication.
Only for the image flaw: use sharp 0.35.5 or later. The use cache flaw has none.
Check the resolved version in the installed package tree, then confirm the deployed build reports the same version.
A development partner with security and testing experience can audit, update, and monitor it.
Waiting leaves two remote code execution paths open on unpatched apps. Check the installed version, move to 16.4.1 or 15.5.28, and verify the result after a clean build. Test caching, images, and Server Actions before going live. Businesses without internal capacity can work with Esight Solutions for audits, patching, and ongoing monitoring. A patched app protects customers today, and a steady update habit keeps every future release manageable.
Tell us about your business challenge. We’ll tell you how we’d solve it.