SecurityNew

    Next.js Patches Nine Vulnerabilities Today. 16.3.7 Is Not the Patch.

    Next.js published 16.3.7 on 29 September. It is a bug fix. The nine September security fixes - one critical - are scheduled for 16.3.8 and 15.5.27 on 30 September. Upgrading to the newest version number yesterday did not patch you.

    Three dates, one trap

    On 22 September 2026, Next.js published an out-of-band security update: 16.3.6 on the Active LTS line and 15.5.26 on the Maintenance LTS line. It addressed a critical remote code execution issue in the Node.js ImageResponse implementation in next/og, where improper escaping in SVG output generated by Satori could lead to remote code execution through upstream dependencies. Versions from 16.2.0 up to but not including 16.3.6 were affected. Applications using the Edge ImageResponse implementation were not affected. Next.js noted that 15.5.26 contained related hardening only, because 15.x was not affected by the remote code execution issue.

    On 23 September 2026, Next.js announced a scheduled security release for 30 September: nine vulnerabilities, one critical, two high, five medium and one low, to be published as 16.3.8 and 15.5.27 alongside the full advisories.

    On 29 September 2026, 16.3.7 was published. The same announcement post was updated that day to say 16.3.7 carries a bug fix and, in its own words, does not include the security fixes planned for 30 September.

    That is the trap, in three dates. Someone who noticed a newer version on 29 September, ran an upgrade to the latest release, and closed the ticket is now running the highest version number Next.js has published, and is patched for none of the nine issues announced a week earlier.

    Being on the latest version is not the same as being patched

    Version numbers are a release sequence, not a patch level. They go up for bug fixes, for features, and for security fixes, and nothing in the number itself tells you which. The only thing that maps a version to a vulnerability is the advisory, and advisories live on a blog and an advisory database, not in your package manager.

    This is why the usual habit fails. Upgrading when something looks old is a maintenance habit. Upgrading because a specific advisory names your version is a security habit. They produce different upgrades on different days, and only the second one is reliable.

    Two LTS lines, two different answers

    Next.js currently labels 16.3 as Active LTS and 15.5 as Maintenance LTS. Both lines received the September fixes. They did not always receive the same fixes: on 22 September the Active line got the remote code execution fix and the Maintenance line got hardening, because the issue did not reach 15.x. Which line your application sits on therefore changes which advisories apply to you, and a migration that landed you on 15.5 is not simply an older copy of the same thing.

    VersionPublishedWhat it containsPatched for the 30 September release?
    16.3.325 August 2026The August security release, covering two critical severity issuesNo
    16.3.622 September 2026Out-of-band fix for the critical next/og remote code execution issueNo
    16.3.729 September 2026A bug fix. The announcement states it does not include the September security fixesNo
    16.3.8Scheduled 30 September 2026The nine September fixes: one critical, two high, five medium, one lowYes, once published
    15.5.2622 September 2026Hardening only; 15.x was not affected by the next/og issueNo
    15.5.27Scheduled 30 September 2026The nine September fixes on the Maintenance LTS lineYes, once published

    Why apps that started as prototypes miss this

    A prototype built on Lovable runs on Lovable's stack, on Lovable's schedule. The moment it becomes a Next.js application you host yourself, the dependency tree becomes yours, and so does everything published about it.

    Nothing about that handover announces itself. There is no prompt, no dashboard banner and no build failure. The August release is a clean illustration: one of its two critical issues was an unauthenticated remote code execution in the image optimization API when optimizing an attacker-controlled AVIF image, and the patched releases disabled AVIF optimization until an upstream fix propagated. That is a behaviour change inside a security patch. Nobody finds that by waiting for something to break.

    The second August critical is worth reading for a different reason. It affected applications using both the Pages Router and the App Router without Cache Components, served from a Windows filesystem, and Next.js stated there was no known workaround for affected applications. Whether it touched you depended on a routing detail and a hosting detail that a founder would not think of as security decisions at all.

    The version check, in five minutes

    1. Find the resolved version of next in your lockfile, not the range in package.json. A caret range tells you what is permitted; the lockfile tells you what is deployed.
    2. Confirm which line you are on: 16.3.x is Active LTS, 15.5.x is Maintenance LTS. If the answer is anything else, you are on a line that is not receiving these releases at all.
    3. Check the patch number against the table above. If it is 16.3.7 or lower, or 15.5.26 or lower, the September fixes are not in your build.
    4. Confirm whether your app uses the Node.js ImageResponse from next/og, and whether it optimizes images from URLs you do not control. Both were the entry points for the recent critical issues.
    5. Redeploy after upgrading, and verify the running build, not the repository. A patched lockfile that has not been deployed has patched nothing.

    A patch calendar is the actual deliverable

    Next.js has now published security releases on 20 August, 25 August, 22 September, 23 September and a scheduled one for 30 September. Supabase shipped PostgreSQL 15.19 and 17.11 on 25 September, bundling five upstream security cycles, closing 44 CVEs, and flagging four changes that may require action before upgrading. Vite replaced its bundler with Rolldown in Vite 8 in March. None of these appear in your application. All of them appear on somebody's changelog.

    The useful question when comparing build offers is not whether the app ships production-ready. Nearly every offer in the category says so, and on handover day it is usually true. The question is who is reading those changelogs in month three, and what happens on the morning a version number goes up without the fixes in it.

    Getting this checked against your app

    IdeaFlo has completed 80 jobs on Upwork, turning Lovable and Vite prototypes into applications that hold up in production. If you want the version check above run against your build, alongside the rest of the pre-launch inventory, the Strategy Audit is $499 one-time and is credited toward any build. If the app needs to become a real application first, the Publishable MVP is $4,999 one-time and ships ready to publish, and the Founding Client package is $2,999 one-time with a 14-day build guarantee and a full refund if the deadline is missed. Both carry the revenue guarantee: first paying customers within 90 days of launch, or a full refund.

    Book a Call

    Sources

    Related posts