CVE-2020-15242: Open Redirect in Next.js

next Updated 02 Oct 2025

Summary

08/10/2020
Yes i
Moderate
4.7

CVE-2020-15242: Open Redirect in Next.js versions. Affects next versions >= 9.5.0, < 9.5.4. Fixed in 9.5.4. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Next.js is a popular framework for building server-side rendered (SSR) and static websites using React. It provides a seamless development experience with features like automatic code splitting, server-side rendering, and static site generation. However, Next.js versions between 9.5.0 and 9.5.3 are vulnerable to an open redirect vulnerability.

Vulnerability Detail

The open redirect vulnerability in Next.js allows an attacker to redirect users to a malicious website by manipulating the URL. This can lead to various attacks, such as phishing, where the attacker tricks users into visiting a fake website and stealing their sensitive information. The vulnerability affects users of Next.js versions between 9.5.0 and 9.5.3. Deployments on Vercel and using next export are not affected. The Common Vulnerabilities and Exposures (CVE) identifier for this vulnerability is CVE-2020-15242.

How To Fix

Latest published version: 16.4.2 as of 22 Oct 2026

npm install next@16.4.2

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

9.5.4

This is the first release that contains the fix.

npm install next@9.5.4

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. It is recommended to follow the fix instructions and upgrade Next.js to the latest version.

Conclusion

The open redirect vulnerability in Next.js versions between 9.5.0 and 9.5.3 can be mitigated by upgrading to version 9.5.4 or later. It is important to keep your Next.js installation up to date to ensure the security of your application. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for next →

Share this vulnerability

FAQ

Next.js is a framework for building server-side rendered (SSR) and static websites using React. It provides features like automatic code splitting, server-side rendering, and static site generation.

The open redirect vulnerability allows an attacker to redirect users to a malicious website by manipulating the URL. This can lead to various attacks, such as phishing, where the attacker tricks users into visiting a fake website and stealing their sensitive information.

Next.js versions between 9.5.0 and 9.5.3 are affected by this vulnerability.

No, deployments on Vercel are not affected by this vulnerability.

To mitigate this vulnerability, it is recommended to upgrade Next.js to version 9.5.4 or later. The patch for this vulnerability can be found in the Next.js releases page.

Related vulnerabilities

Recent vulnerabilities recorded for next.

How To Fix

Latest published version: 16.4.2 as of 22 Oct 2026

npm install next@16.4.2

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

9.5.4

This is the first release that contains the fix.

npm install next@9.5.4

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback