Packages

@next/eslint-plugin-next

16.4.6 · 9 Nov 2026MIT57.3M / weekRepositoryHomepagenpmAtom feed

Upgrading @next/eslint-plugin-next From 11.0.1 to 11.1.0

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 11.0.1Newest 11.x11.1.4Latest16.4.6
  1. 11.0.1yours
  2. 11.1.0target
0
changes to make
0
advisories fixed
55
new
41
fixes

Security

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

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

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

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

    11.1.0

Release by release

  1. 11.1.0

    Security fix11 Aug 202155 new · 41 fixes
    • Security

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

    • Security

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

    • Security

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

    • Security

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

74 other lines we could not sort, mostly version bumps
  • We have released patch versions for both the stable and canary channels of Next.js.

    11.1.0
  • To upgrade run npm install next@latest --save

    11.1.0
  • Affected: Users of Next.js between 10.0.5 and 10.2.0

    11.1.0
  • Affected: Users of Next.js between 11.0.0 and 11.0.1 using pages/_error.js without getInitialProps

    11.1.0
  • Affected: Users of Next.js between 11.0.0 and 11.0.1 using pages/_error.js and next export

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

    11.1.0
  • Not affected: Deployments with pages/404.js

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

    11.1.0
  • A public CVE was released.

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

    11.1.0

135 internal lines (docs, tests, tooling) left out.

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.