fix(deps): update dependency next to ^13.5.11 [security] #98
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
|
Deployment failed with the following error: |
|
Deployment failed with the following error: |
|
Deployment failed with the following error: |
❌ Deploy Preview for safe-vault failed. Why did it fail? →
|
❌ Deploy Preview for safe-vaultt failed. Why did it fail? →
|
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
bcf6a20 to
265a3f8
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
renovate
bot
added
breaking
and removed
dependencies
renovate
bot
changed the title
|
Deployment failed with the following error: |
|
Deployment failed with the following error: |
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
265a3f8 to
91c09c7
Compare
renovate
bot
added
dependencies
renovate
bot
changed the title
|
Deployment failed with the following error: Learn More: https://vercel.com/safewallet-pros-projects?upgradeToPro=build-rate-limit |
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
91c09c7 to
e5b9657
Compare
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
e2a86f6 to
72936eb
Compare
renovate
bot
added
breaking
and removed
dependencies
renovate
bot
changed the title
|
Deployment failed with the following error: Learn More: https://vercel.com/safewallet-pros-projects?upgradeToPro=build-rate-limit |
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
72936eb to
28e08d8
Compare
renovate
bot
added
dependencies
renovate
bot
changed the title
|
Deployment failed with the following error: Learn More: https://vercel.com/safewallet-pros-projects?upgradeToPro=build-rate-limit |
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:
^13.5.0->^13.5.11GitHub Vulnerability Alerts
CVE-2024-34351
Impact
A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the
Hostheader is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself.Prerequisites
<14.1.1) is running in a self-hosted* manner./.* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner.
Patches
This vulnerability was patched in #62561 and fixed in Next.js
14.1.1.Workarounds
There are no official workarounds for this vulnerability. We recommend upgrading to Next.js
14.1.1.Credit
Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to:
Adam Kues - Assetnote
Shubham Shah - Assetnote
CVE-2024-47831
Impact
The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.
Not affected:
next.config.jsfile is configured withimages.unoptimizedset totrueorimages.loaderset to a non-default value.Patches
This issue was fully patched in Next.js
14.2.7. We recommend that users upgrade to at least this version.Workarounds
Ensure that the
next.config.jsfile has eitherimages.unoptimized,images.loaderorimages.loaderFileassigned.Credits
Brandon Dahler (brandondahler), AWS
Dimitrios Vlastaras
CVE-2024-51479
Impact
If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.
Patches
This issue was patched in Next.js
14.2.15and later.If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.
Workarounds
There are no official workarounds for this vulnerability.
Credits
We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
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-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
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-32421
Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve
pagePropsdata instead of standard HTML.Learn more here
Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.
Release Notes
vercel/next.js (next)
v13.5.11Compare Source
Core Changes
v13.5.10Compare Source
Core Changes
v13.5.9Compare Source
Core Changes
v13.5.8Compare Source
Core Changes
d900fadto1dba980: #74202Credits
Huge thanks to @wyattjoh and @ztanner for helping!
v13.5.7Compare Source
Core Changes
Credits
Huge thanks to @wyattjoh and @ijjk for helping!
v13.5.6Compare Source
Core Changes
Credits
Huge thanks to @ijjk @huozhi @gnoff for helping!
v13.5.5Compare Source
Core Changes
fs.existsSyncto avoid race condition: #56387waitUntilinto the handler: #56404existSynccall: #56419isolateModulestotsconfigwhen extending from tsconfig withverbatimModuleSyntax: #54164verbatimModuleSyntaxto make type imports/exports explicit: #56551server-onlyandclient-only: #56760useParams: #56771x-forwarded-*headers: #56797Documentation Changes
JSON.parseto make reading output easier: #56713Example Changes
@radix-ui/react-icons: #56452Misc Changes
permalinkoption ofuseFormState: #56329cargo fmtto lint staged: #56430.../templates/*/app/layout.*import order: #56380.env.examplefile: #56469Credits
Huge thanks to @ijjk, @timneutkens, @shuding, @wyattjoh, @Syphini, @manovotny, @ForsakenHarmony, @gnoff, @anonrig, @viktorronnback, @Rylab, @sokra, @hamirmahal, @huozhi, @jridgewell, @SukkaW, @wbinnssmith, @feedthejim, @balazsorban44, @jazsouf, @2XG-DEV, @stefanprobst, @ztanner, @mzab1985, @Mustafadagkiranlar, @JoRyGu, @cmbritten, @styfle, @Krishnanand2517, @bahag-buttf, @kwonoj, @Shadid12, @delbaoliveira, @mayankkamboj47, @dvoytenko, @mayank1513, @himself65, @suravshrestha, @fvaysh, @dianacpg, @joristirado, and @Kikobeats for helping!
v13.5.4Compare Source
Core Changes
beta.nextjs.orgLinks: #55924config.experimental.workerThreads: #55257swc_coretov0.83.26: #55780swc_coretov0.83.26": #56077permanentRedirectreturn 308 in route handlers: #56065booleaninstead offalsefor experimental logging config: #56110postcss: #56225Documentation Changes
not-foundto file conventions page: #55944extensionoption tocreateMDX(): #55967.bindmethod: #56164Response.jsonoverNextResponse.json: #56173Example Changes
with-jest: #56152with-jesttypes: #56193with-stripe-typescriptexample: #56274Misc Changes
swc_coretov0.83.28: #56134Credits
Huge thanks to @balazsorban44, @sdkdeepa, @aayman997, @mayank1513, @timneutkens, @2XG-DEV, @eliot-akira, @hi-matthew, @riobits, @wbinnssmith, @ijjk, @sokra, @dvoytenko, @rishabhpoddar, @manovotny, @A7med3bdulBaset, @huozhi, @jridgewell, @joulev, @SukkaW, @kdy1, @feedthejim, @Fredkiss3, @styfle, @MildTomato, @ForsakenHarmony, @walfly, @bzhn, @shuding, @boylett, @Loki899899, @devrsi0n, @ImBIOS, @vinaykulk621, @ztanner, @sdaigo, @hamirmahal, @blurrah, @omarmciver, and @alexBaizeau for helping!
v13.5.3Compare Source
Core Changes
build: #55628fs.existsSyncinstead ofaccessSync: #55675next/dist/esmrewriteResolvePlugin: #55689fetchServerResponseis a valid record when stored in router cache: #55690next/navigation: #55743generate_typestask: #55748next infooutput: #55704--experimental-https: #55775turbopack-230922.2: #55828--experimental-https: #55775turbopack-230922.2: #55828Documentation Changes
useFormState: #55564Example Changes
Misc Changes
nissuer: #55723dependencies/devDependencies: #55730Credits
Huge thanks to @sokra, @ztanner, @anonrig, @huozhi, @mayank1513, @travisanderson, @wyattjoh, @jridgewell, @ryanagillie, @Brooooooklyn, @kwonoj, @balazsorban44, @naruaway, @S3Prototype, @feedthejim, @joulev, @icyJoseph, @ijjk, @ForsakenHarmony, @timneutkens, @wbinnssmith, @sdkdeepa, @sdaigo, @leerob, @dominiksipowicz, @joao-vasconcelos, and @mostafaegouda for helping!
v13.5.2Compare Source
Core Changes
d6dcad6](https://redirConfiguration
📅 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.