-
Notifications
You must be signed in to change notification settings - Fork 2
fix(deps): update dependency next to v15.4.7 [security] #100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-next-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
2ce67ff to
32952f7
Compare
60d0adf to
32952f7
Compare
32952f7 to
07c8b7a
Compare
07c8b7a to
ea04cfb
Compare
ea04cfb to
dc3008e
Compare
dc3008e to
38c174a
Compare
38c174a to
a9370ff
Compare
a9370ff to
a2a1553
Compare
a2a1553 to
90d6a63
Compare
90d6a63 to
7eb544c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
15.1.7→15.4.7GitHub Vulnerability Alerts
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.314.2.25Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
Workaround
If patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the
x-middleware-subrequestheader from reaching your Next.js application.Credits
CVE-2025-48068
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 devis active.Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure
allowedDevOriginsin your next config after upgrading to a patched version. Learn more.Learn more: https://vercel.com/changelog/cve-2025-48068
Credit
Thanks to sapphi-red and Radman Siddiki for responsibly disclosing this issue.
CVE-2025-49826
Summary
A vulnerability affecting Next.js has been addressed. It impacted versions 15.0.4 through 15.1.8 and involved a cache poisoning bug leading to a Denial of Service (DoS) condition.
Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page
More details: CVE-2025-49826
Credits
CVE-2025-55173
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.
All users relying on
images.domainsorimages.remotePatternsare encouraged to upgrade and verify that external image sources are strictly validated.More details at Vercel Changelog
CVE-2025-57752
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as
CookieorAuthorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.
More details at Vercel Changelog
CVE-2025-57822
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into
NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the
next()function.More details at Vercel Changelog
GHSA-9qr9-h5gf-34mp
A vulnerability affects certain React packages1 for versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55182.
Fixed in:
React: 19.0.1, 19.1.2, 19.2.1
Next.js: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7, 15.6.0-canary.58, 16.1.0-canary.12+
The vulnerability also affects experimental canary releases starting with 14.3.0-canary.77. Users on any of the 14.3 canary builds should either downgrade to a 14.x stable release or 14.3.0-canary.76.
All users of stable 15.x or 16.x Next.js versions should upgrade to a patched, stable version immediately.
1 The affected React packages are:
GHSA-mwv6-3258-q52c
A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55184.
A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.
GHSA-w37m-7fhw-fmv9
A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55183.
A malicious HTTP request can be crafted and sent to any App Router endpoint that can return the compiled source code of Server Functions. This could reveal business logic, but would not expose secrets unless they were hardcoded directly into Server Function code.
Release Notes
vercel/next.js (next)
v15.4.7Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v15.4.6Compare Source
Core Changes
_errorpage'sreq.urlcan be overwritten to dynamic param on minimal mode (#82347)?dplto fonts in/_next/static/media(#82384)Credits
Huge thanks to @devjiwonchoi, @ijjk, and @styfle for helping!
v15.4.5Compare Source
Core Changes
Credits
Huge thanks to @ijjk, @sokra, and @styfle for helping!
v15.4.4Compare Source
Core Changes
Credits
Huge thanks to @bgw @mischnic @huozhi @lukesandberg and @ijjk for helping!
v15.4.3Compare Source
Core Changes
Credits
Huge thanks to @mischnic for helping!
v15.4.2Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @ijjk, and @ztanner for helping!
v15.4.1Compare Source
Core Changes
+,-or.: #779323fbfb9ba-20250409toc44e4a25-20250409: #78031c44e4a25-20250409to1d6c8168-20250411: #78067image-size@1.2.1: #78149strictNullChecksin test utils: #78142eslint-plugin-next: #781091d6c8168-20250411to39cad7af-20250411: #7815239cad7af-20250411tob04254fd-20250415: #78253@next/mdx: Use stable turbopack config options: #78261b04254fd-20250415to4a36d3ea-20250416: #78297next start --turbopack: #783844a36d3ea-20250416tobc6184dd-20250417: #78322experimental.turbois set: #77998bc6184dd-20250417to914319ae-20250423: #78468914319ae-20250423to197d6a04-20250424: #78516error.nameto label: #78198prerenderfunction for"use cache"with Dynamic IO: #78382node:prefixed in ESM emit of standalone server.js: #78624widthtransition logic: #78635@swc/counter: #78674197d6a04-20250424to5dc00d6b-20250428: #786405dc00d6b-20250428to408d055a-20250430: #78715draft.isEnabledsetter from exotic draftMode wrappers: #77972408d055a-20250430to197d6a04-20250424: #78834@swc/corenpm package tov1.11.24: #77668extensionregex in@next/mdx: #78734max-old-space-size: #78712runInCleanSnapshotto Work Store: #78930--no-manglingfor"use cache"functions: #78993"use cache"timeout errors from being caught in userland code: #78998LinkPropsin emitted declarations: #78773define-env-plugin.tstodefine-env.ts: #79224CacheHandler.getmethod: #79213onPostponeto determine if segment prefetch is partial: #79299pprwhendynamicIOis enabled: #79302app-render.tsx: #79303experimental.enablePrerenderSourceMapsis enabled: #79109@changesets/changelog-githubfor changelog format: #79040compiler.defineServerfor server-only constants: #79225@changesets/changelog-githubfor changelog format: #79040compiler.defineServerfor server-only constants: #79225someFunc(): void) type for client boundary warnings: #79144"use cache": #78882"use cache": #78882clientInstrumentationHooktype: #79701tscruns inpackages/nextwithout having to build first: #79782tscin watch mode duringpnpm dev: #79785vary(#79939)subissuesfromIssue: #79988taskrtasks: #80020@ts-expect-error: #80065get*Stackimplementation: #79789<option>in Preferences dropdowns: #80025require()instead ofnext/dist/if possible: #80054isRecoverableErrorimplementation: #80003wrapRequestHandler: #80055getSquashedHydrationErrorDetailsimplementation: #80046onErrorin /pages: #79982server-inserted-metadatamodule: #80143regionsproperty to the Functions Config Manifest file: #80104require()calls: #80056/.well-known/appspecific/com.chrome.devtools.jsonendpoint in dev: #80260Infinityexpiration for implicit tags: #80387config.allowedDevOrigins(#80410) (Learn More)Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.