@next/mdx
16.4.6 · 9 Nov 2026MIT2.2M / weekRepositoryHomepagenpmAtom feed
9.5.5 is the newest release of 9.x.
In short
1 security9 new26 fixed10 changed9 internal
- 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.3.2. For future security related communications of our OSS projects, please join this mailing list.
Next.js has just been audited by one of the top security firms in the world.
They found that attackers could craft special requests to access files in the dist directory (.next).
This does not affect files outside of the dist directory (.next).
In general, the dist directory only holds build assets unless your application intentionally stores other assets under this directory.
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
Not affected: Deployments on ZEIT Now v2 (https://zeit.co) are not affected
Not affected: Deployments using the
serverlesstargetNot affected: Deployments using
next exportAffected: Users of Next.js below 9.3.2 that use
next start
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 ../ with a 200 response.
What is Being Done
As Next.js has grown in popularity, it has received the attention of security researchers and auditors. We are thankful to Luca Carettoni from Doyensec for their investigation and discovery of the original bug and subsequent responsible disclosure.
We've landed a patch that ensures only known filesystem paths of .next/static are made available under /_next/static.
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 issued.
If you want to stay on top of our security related news impacting Next.js or other ZEIT projects, please join this mailing list.
We encourage responsible disclosure of future issues. Please email us at security@zeit.co. We are actively monitoring this mailbox.
Patches
Add Numeric Separator Support for TypeScript
Update CLI custom config documentation link
Add error when attempting to export GSSP page
Update blog-starter example
Add CSS file to build output
Update <dir> reference in help text: 5274535
Clean up examples directory
Remove react-ssr-prepass alias as it's not longer needed
Add section on reading files
Updated with-typescript example to SSG
Add CMS example for Sanity
Group CSS files in shared build output separate from JS files
Updating min nodejs requirement
Add support for baseUrl option in tsconfig and jsconfig
CMS TakeShape Example
Ensure hybrid AMP works correctly with SSG
Update mocha example with yml configuration.
Fix with-firebase-cloud-messaging example setup code
Update wording of new data fetching methods recommendation
Updated Api Routes Middleware example to use getServerSideProps
With Firebase Client-Side example
Remove mkdirp, bump fs-extra to 9.0.0
Add support for paths in tsconfig.json and jsconfig.json
Add test for single alias
Update GIP docs
Add custom amp optimizer and skip validation mode
Update handling for ENOENT from GSSP methods
Fix assignment of props in WithApollo.getInitialProps
Skip paths that are routed to a .d.ts file
Upgrade loader-utils
Fix warning for API routes with next export
Make sure to copy AMP SSG files during export
Use records to init store
Update data-fetching.md: 074c60e
Update to prevent re-using workers for getStaticPaths in dev mode
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.