Information exposure in Next.js dev server due to lack of origin verification
cve-program · CVE-2025-48068
PublishedNext.js is a React framework for building full-stack web applications. In versions starting from 13.0 to before 14.2.30 and 15.0.0 to before 15.2.2, Next.js may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active. This issue has been patched in versions 14.2.30 and 15.2.2.
Read the publisher's advisoryeuvd · EUVD-2025-16359
PublishedNext.js is a React framework for building full-stack web applications. In versions starting from 13.0 to before 14.2.30 and 15.0.0 to before 15.2.2, Next.js may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active. This issue has been patched in versions 14.2.30 and 15.2.2.
Read the publisher's advisorynvd · CVE-2025-48068
PublishedNext.js is a React framework for building full-stack web applications. In versions starting from 13.0 to before 14.2.30 and 15.0.0 to before 15.2.2, Next.js may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active. This issue has been patched in versions 14.2.30 and 15.2.2.
Read the publisher's advisoryosv · GHSA-3h52-269p-cp9r
Published## Summary A low-severity vulnerability in **Next.js** has been fixed in **version 15.2.2**. This issue may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while `npm run dev` is active. Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure `allowedDevOrigins` in your next config after upgrading to a patched version. [Learn more](https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins). Learn more: https://vercel.com/changelog/cve-2025-48068 ## Credit Thanks to [sapphi-red](https://github.com/sapphi-red) and [Radman Siddiki](https://github.com/R4356th) for responsibly disclosing this issue.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-48068 · CVE overview and exploitation status
cve-program · CVE-2025-48068
- https://github.com/vercel/next.js/security/advisories/GHSA-3h52-269p-cp9r
- https://vercel.com/changelog/cve-2025-48068
euvd · EUVD-2025-16359
- https://github.com/vercel/next.js/security/advisories/GHSA-3h52-269p-cp9r
- https://vercel.com/changelog/cve-2025-48068
nvd · CVE-2025-48068
- https://github.com/vercel/next.js/security/advisories/GHSA-3h52-269p-cp9r
- https://vercel.com/changelog/cve-2025-48068
osv · GHSA-3h52-269p-cp9r
Related changes
Linked by CVE identifierNo related changes are available here.