Repository navigation
fix(deps): update dependency next to v14.2.32 [security] - autoclosed - #174
Closed
renovate-bot wants to merge 1 commit into
Closed
renovate-bot wants to merge 1 commit into
renovate-bot wants to merge 1 commit into
Conversation
renovate-bot
requested review from
a team,
LukeSchlangen and
donmccasland
as code owners
September 1, 2025 00:36
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 1, 2025 08:33
2d08d94 to
fec20fe
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 1, 2025 12:57
fec20fe to
a19a3e6
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 1, 2025 17:29
a19a3e6 to
a8ed695
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 1, 2025 21:06
a8ed695 to
5bf1f34
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 2, 2025 02:23
5bf1f34 to
3e23acd
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 2, 2025 05:27
3e23acd to
486d0fe
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 2, 2025 10:27
486d0fe to
ef1a590
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 2, 2025 14:44
ef1a590 to
7cb3878
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 3, 2025 10:45
583b7df to
2dc984e
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 3, 2025 14:28
2dc984e to
3085a26
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 3, 2025 23:08
3085a26 to
2531a49
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 4, 2025 04:45
2531a49 to
872c871
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 4, 2025 11:27
872c871 to
f6e11b1
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 4, 2025 16:08
f6e11b1 to
0f5aace
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 4, 2025 18:31
0f5aace to
aea3bd8
Compare
renovate-bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 4, 2025 22:22
aea3bd8 to
f3379d7
Compare
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
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:
14.2.30->14.2.32GitHub Vulnerability Alerts
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
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
Release Notes
vercel/next.js (next)
v14.2.32Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.31Compare Source
Core Changes
Credits
Huge thanks to @styfle and @ztanner for helping!
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.