Packages

@next/bundle-analyzer

16.4.6 · 9 Nov 2026MIT6.4M / weekRepositoryHomepagenpmAtom feed

Your version

9.5.4

7 Oct 2020Where it was published

9.5.5 is the newest release of 9.x.

In short

1 removed4 security6 new14 fixed35 changed75 internal

  • Removed

    Remove left-over api-utils method

  • Security

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

  • Security

    Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.

  • Security

    We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.

  • Security

    Regression tests for this attack were added to the security integration test suite.

Release note

This upgrade is completely backwards compatible and recommended for all users on versions below 9.5.4. For future security related communications of our OSS projects, please join this mailing list.

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

Specially encoded paths could be used with the trailing slash redirect to allow 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 attackers 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 run npm install next@latest --save

Impact

  • Affected: Users of Next.js between 9.5.0 and 9.5.3

  • Not affected: Deployments on Vercel (vercel.com) are not affected

  • Not affected: Deployments using next export

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

How to Assess Impact

If you think users could have been affected, you can filter logs of affected sites by %2F with a 308 response.

What is Being Done

As Next.js has grown in popularity, it has received the attention of security teams and auditors. We are thankful to those that reached out for their investigation and discovery of the original bug and subsequent responsible disclosure.

We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.

Regression tests for this attack were added to the security integration test suite.

  • We have notified known Next.js users in advance of this publication.

  • A public CVE was released.

  • If you want to stay on top of our security related news impacting Next.js or other Vercel projects, please join this mailing list.

  • We encourage responsible disclosure of future issues. Please email us at security@vercel.com. We are actively monitoring this mailbox.


Core Changes

  • Make the image post-processor ignore SVG images

  • Only update lookups for dev overlay if mounted

  • Ensure interpolating dynamic href values works correctly

  • Add automatic reloading when editing GS(S)P methods

  • Update to show build indicator while re-fetching GS(S)P data in dev

  • Make parseRelativeUrl return a UrlObject

  • Add tests for searchParams dev warning

  • Fix invalid config export errors

  • Correct client rewrite resolving with query

  • Fix href resolving with trailing slash enabled

  • Divide export build output into 4 segments instead of showing it one by one

  • Include additional query values when interpolating href

  • Correct page path for GS(S)P data refreshing

  • Fix align documentation with the code

  • Remove next-head-count

  • Add Support for CSS Module Value Imports

  • Fix resolving href with a rewrite

  • Correct query behavior for falsey values to pre 9.5.1 behavior

  • Importing CSS from Third Party React Components

  • Add error when href interpolation fails

  • Security upgrade node-fetch

  • Upgrade sass loader

  • Prefer builtin optional chaining and nullish coalescing

  • Upgrade cacache of terser-webpack-plugin

  • Upgrade web-vitals

  • Remove false positive in circular structure detection

  • Fix Webpack 5 configuration for v5.0.0-beta.30

  • Improve custom document error message

  • Use babel 7 jsx syntax

  • webpack@5.0.0-beta.30: Invalid configuration

  • Normalize asPath for GS(S)P pages

  • Polyfill missing std lib fns for module browsers

  • Provide resolvedUrl to getServerSideProps

  • Fix API page check during SSG page collecting

  • Update webpack 5 resolving

  • Separate resolved asPath from resolved URL for GSSP

  • Fix export-cli progress label default value

  • Improve server performance by skipping decode/re-encode

  • Remove extra check in config loading

  • Expose dotenv loading under separate package

  • Fix empty title in head

  • Ensure optional-chaining/nullish coalescing is included

  • Removed

    Remove left-over api-utils method

  • Add warning when exporting with custom routes

  • Normalize optional catch-all fallback: true page params

  • Update to use hasNextSupport for custom-routes in next export check

Misc Changes

  • eslint-plugin-next: Support src/pages folder in no-html-link-for-pages rule

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.