Skip to content

fix(deps): update dependency next to v16.4.5 [security] - #1285

Merged
renovate[bot] merged 1 commit into
masterfrom
renovate/npm-next-vulnerability
Nov 17, 2026
Merged

renovate[bot] merged 1 commit into
masterfrom
renovate/npm-next-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
next (source) 16.4.1 → 16.4.5 age confidence

Warning

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 through unstable_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 Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vercel/next.js (next)

v16.4.5

Compare Source

This release contains security fixes for the following advisories:

Moderate

v16.4.4

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary. The announced security released for November will be published tomorrow.

Core Changes
  • [lts-active] test: disable the reads fallback params after a client navigation deployment test (#​100668)
  • [lts-active] Reload on missed Turbopack startup CSS updates (#​100619)
  • [lts-active] Revert "Optimize strict module factory chunks (#​98421)" (#​100866)
  • [lts-active] Emit the Turbopack shared-runtime bootstrap in the PPR resume so it gets the CSP nonce (#​100907)
  • [lts-active] [ci] Pin deploy test deployments to Node.js 22.x (#​100886)
  • [lts-active] fix(analyze): use route summaries as the analyzer route index (#​100974)
  • [lts-active] Use fast-jwt instead of jsonwebtoken (#​100885)
Credits

Huge thanks to @​icyJoseph, @​mischnic, @​wbinnssmith, @​lukesandberg, and @​eps1lon for helping!

v16.4.3

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
Credits

Huge thanks to @​mischnic, @​lukesandberg, @​acdlite, @​eps1lon, and @​sokra for helping!

v16.4.2

Compare Source

What's Changed

Full Changelog: vercel/next.js@v16.4.1...v16.4.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 16, 2026
@renovate
renovate Bot merged commit 39f8520 into master Nov 17, 2026
23 checks passed
@renovate
renovate Bot deleted the renovate/npm-next-vulnerability branch November 17, 2026 05:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants