# nextjs/release
Next.js v16.4.5
importance: criticalsecurity
This release contains security fixes addressing seven moderate advisories. The issues affect caching, response handling, image optimization, and cookie exposure in Edge runtime routes.
affected
Applications using Next.js may be affected, particularly those relying on 'use cache', forwarded fetched responses, image optimization, or Edge runtime routes.
action
Upgrade to Next.js 16.4.5 to receive the listed security fixes.
release_signals
!Fixed cross-tenant sensitive information disclosure involving 'use cache' called through unstable_cache (GHSA-mfr8-8qww-v76h).
!Fixed cache leakage across root parameter values in nested 'use cache' functions (GHSA-vc7v-qv4w-wrv8).
!Fixed cache poisoning of shared fallback shells through request-supplied placeholder route parameters (GHSA-vvgp-ww4w-46vf).
!Fixed cross-user cache disclosure and poisoning involving binary arguments to 'use cache' (GHSA-rhh4-g77r-r9qj).
!Fixed cross-client response injection and disclosure, an SVG rejection bypass, and HttpOnly cookie exposure through an internal response header (GHSA-pc58-hwjq-p385, GHSA-7qx7-33qx-rqx2, GHSA-f3mh-rxg3-f5g2).
# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.