CyberRota Analysis
AI-GeneratedNext.js versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10 are vulnerable to a caching issue where a server-side fetch with a non-UTF-8 request body can return cached responses from different requests, potentially exposing sensitive data to unauthorized users. This vulnerability primarily affects applications that handle request bodies with content types other than UTF-8. Developers using affected versions should prioritize updating to versions 15.5.21 or 16.2.11 to mitigate the risk of data leakage.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache. This issue has been fixed in versions 15.5.21 and 16.2.11.
Related CVEs
Other vulnerabilities affecting the same vendor(s)