# Next.js use cache Reused the Same Cache Entry for Different Files Before 16.4.5

Source: [DEV Community: javascript](https://dev.to/shubhradev/nextjs-use-cache-reused-the-same-cache-entry-for-different-files-before-1645-598g) · 2026-11-18 · Frontend
Page: https://themorning.dev/story/next-js-use-cache-reused-the-same-cache-entry-for-different-files-before-16-4-5-5d9126f0a135d69d
Kind: research · Impact: medium

## In brief

- Next.js versions before 16.4.5 reused the same use cache entry for different files, according to the article.
- The Next.js docs say serializable arguments to a use cache function form its cache key, but the article says they do not explain how binary values enter that key.
- The headline says the issue is fixed in Next.js 16.4.5.

## Why it matters

If your use cache functions take binary inputs such as files, cached results can be returned for the wrong input on affected versions.

## What to do

- Upgrade Next.js to 16.4.5 or later

## Versions

- Next.js 16.4.5

## Coverage

- [Next.js use cache Reused the Same Cache Entry for Different Files Before 16.4.5](https://dev.to/shubhradev/nextjs-use-cache-reused-the-same-cache-entry-for-different-files-before-1645-598g) — DEV Community: javascript, 2026-11-18

Tags: nextjs, caching, use-cache, react, bug

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
