Repository navigation
fix(deps): update dependency next to v16.4.5 [security] - #1285
Merged
Merged
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
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:
16.4.1→16.4.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
CVE-2026-119790 / GHSA-mfr8-8qww-v76h
More information
Details
Next.js applications with
'use cache'can disclose cached data across root params when the same'use cache'function is called both directly during rendering and throughunstable_cache(), and that function reads a root param. Root params are route parameters of the root layout, and applications commonly use them to scope data, for example per locale.During a cold process start, a cross-request deduplication race allowed an
unstable_cache()call to join the in-flight fill of a concurrent direct call and receive its result, bypassing the root param check that would normally reject it.unstable_cache()then stored that result under a cache key without root params, so subsequent requests for other root param values received the same entry until it is revalidated or evicted. Cached data produced for one root param value is returned to requests for other values.Exploitation requires the
unstable_cache()request to arrive while the function's first fill after a process start is still in flight. Outside this race, the nesting already throws an error:'use cache' inside unstable_cache() is unsupported, and avoiding it is a complete workaround.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vercel/next.js (next)
v16.4.5Compare Source
This release contains security fixes for the following advisories:
Moderate
v16.4.4Compare Source
Core Changes
reads fallback params after a client navigationdeployment test (#100668)Credits
Huge thanks to @icyJoseph, @mischnic, @wbinnssmith, @lukesandberg, and @eps1lon for helping!
v16.4.3Compare Source
Core Changes
Credits
Huge thanks to @mischnic, @lukesandberg, @acdlite, @eps1lon, and @sokra for helping!
v16.4.2Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.4.1...v16.4.2
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.