Sourced fromnext's releases.

v11.1.0

A security team from one of our partners noticed an issue in Next.js that allowed for an open redirect to occur.

Specially encoded paths could be used whenpages/_error.js was statically generated allowing an open redirect to occur to an external site.

In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.

We recommend upgrading to the latest version of Next.js to improve the overall security of your application.

How to Upgrade

• We have released patch versions for both the stable and canary channels of Next.js.
• To upgrade runnpm install next@latest --save

Impact

• Affected: Users of Next.js between 10.0.5 and 10.2.0
• Affected: Users of Next.js between 11.0.0 and 11.0.1 usingpages/_error.js withoutgetInitialProps
• Affected: Users of Next.js between 11.0.0 and 11.0.1 usingpages/_error.js andnext export
• Not affected: Deployments on Vercel (vercel.com) are not affected
• Not affected: Deploymentswithpages/404.js

We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.

How to Assess Impact

If you think sensitive code or data could have been exposed, you can filter logs of affected sites by// (double slash at the start of the url) followed by a domain.

What is Being Done

As Next.js has grown in popularity and usage by enterprises, it has received the attention of security researchers and auditors. We are thankful to Gabriel Benmergui from Robinhood for their investigation and discovery of the original bug and subsequent responsible disclosure.

We've landed a patch that ensures path parsing is handled properly for these paths so that the open redirect can no longer occur.

Regression tests for this attack were added to thesecurity integration test suite

• We have notified known Next.js users in advance of this publication.
• A public CVE was released.
• We encourage responsible disclosure of future reports. Please email us atsecurity@vercel.com. We are actively monitoring this mailbox.

---

Release notes

Core Changes

• Don't test image domains in test env:#26502
• Fix props not updating when changing the locale and keeping hash:#26205
• Allow user to override next-image-loader:#26548
• Add logging when a custom babelrc is loaded:#26570

... (truncated)

• ce4adfc v11.1.0
• 092a476 v11.0.2-canary.31
• ebb6a30 Revert "Add warning duringnext build when sharp is missing (#27933)"
• 52486ce v11.0.2-canary.30
• 8ac3254 Revert "Next swc publish flow (#27932)"
• 6014b6e v11.0.2-canary.29
• 4cd45aa Add rootDir setting to eslint-plugin-next (#27918)
• e61ea6f Add manifest check step and add missing items (#27934)
• 94fc6f0 Next swc publish flow (#27932)
• 51a2a02 Add warning duringnext build when sharp is missing (#27933)
• Additional commits viewable incompare view

This version was pushed to npm byzeit-bot, a new releaser for next since your current version.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from theSecurity Alerts page.