Skip to content
Security

Next.js Patches Vulnerabilities Twice in One Week: What to Do About 16.3.8 and 15.5.27

3 min read

If your website or online store runs on Next.js, it should have landed on your update calendar twice in the past two weeks. On September 22 the Next.js team shipped an out-of-band fix for a critical issue in an upstream dependency, and on September 30 it released a scheduled security update covering seven vulnerabilities. And that is not the end: two more, more serious flaws are still waiting for a fix.

What happened on September 22

On September 22 the Next.js team announced that a critical security issue had been identified in an upstream dependency. Outside its normal schedule it released versions 16.3.6 and 15.5.26. Details on impact, affected versions and upgrade steps are in the advisory GHSA-vcvr-r3jv-pc5j. An unscheduled release is a signal that this could not wait for the regular cycle.

The scheduled release on September 30

A week later came the planned security release. Next.js announced it in advance, on September 23, so teams could plan their upgrades. It was originally expected to cover nine vulnerabilities, but the final release addresses seven: one high severity, five medium and one low. The fixes ship in 16.3.8 and 15.5.27.

One detail that can trip people up: version 16.3.7 from September 29 does not contain the security fixes; it was an ordinary bug-fix release. If you stopped there, you are still vulnerable.

Two flaws are still pending

The remaining two vulnerabilities, one critical and one high, were pulled from this release. According to the team they are pending upstream coordination and will be fixed in a later Next.js release. The practical consequence: upgrading to 16.3.8 or 15.5.27 is not the end of the story. Follow the project’s blog and security advisories and expect another upgrade.

How to act in practice

  • Find out which version you run. Check package.json and the lock file. What matters is the version actually installed, not the range in your dependencies.
  • Upgrade within your branch. On 16.x go to 16.3.8, on 15.x go to 15.5.27. No major-version jump is needed, as patches were released for both lines.
  • Staging first. Even a patch release can change behavior. Test forms, login, payments and dynamic pages.
  • Turn on automatic alerts. Dependabot or Renovate will offer security updates immediately and save you days of needless exposure.
  • Watch your dependencies too. The September emergency fix came from an upstream package, so run npm audit or your package manager’s equivalent regularly.

Why smaller sites should care too

Frameworks like Next.js now power company sites, online stores and web apps alike. Attackers scan for publicly known vulnerabilities automatically and do not care how big a site is. A published security advisory is also a map of where to look. The longer your site stays on an old version after a fix is out, the greater the risk.

Conclusion

Two security releases in eight days and two more fixes on the way mean one thing: framework updates cannot be put off until “some day”. Check today which Next.js version your site runs and plan the upgrade to 16.3.8 or 15.5.27. Don’t want to handle it yourself? At FullNet Servis we take care of website updates and security, so get in touch.

Potřebujete pomoc s webovým projektem?

Rádi vám pomůžeme. Konzultace je zdarma a nezávazná.

Poraďte se s námi
Let's collaborate

Tell us about your project

Describe your project and we'll get back to you.

50+ satisfied companies
We reply within 24h
Free consultation
Bc. Martin Procházka
founder & developer
Please enter your name.
Please enter a valid email address.
Please enter a valid phone number.
Please describe what you need.
You must agree to the processing of personal data.