@next/mdx
16.4.6 · 9 Nov 2026MIT2.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @next/mdx From 11.0.1 to 11.1.0
1 release in betweenevery note read
Security
- 11.1.0
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.jswas 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
Release by release
- 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.jswas 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
- Security
74 other lines we could not sort, mostly version bumps
- 11.1.0
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.jswithoutgetInitialProps - 11.1.0
Affected: Users of Next.js between 11.0.0 and 11.0.1 using
pages/_error.jsandnext 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.
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.