Skepra / Web recovery & resilience
Next.js use cache binary arguments and cache isolation.
A customer portal that caches document or preview results needs a clear decision about binary arguments and shared cache entries.
Discuss the next maintenance decisionWhat the advisory says
The Next.js maintainer published GHSA-rhh4-g77r-r9qj, CVE-2026-119349, on 3 November 2026. App Router functions using use cache with binary arguments such as Uint8Array or Blob can produce identical cache keys for distinct inputs. The affected range is 16.0.0 through 16.4.4 and the listed fix is 16.4.5.
Check the function boundary
Record the deployed version, the cached function, binary argument types, authorization boundary and returned business data. A binary value elsewhere in the repository is not enough to establish applicability. Keep unknown call paths unresolved.
Use synthetic isolation checks
In staging, use two synthetic users and deliberately different binary inputs. Exercise the same business route in both request orders, including a cold run, repeated reads and normal invalidation. Record artifact identity and output-to-input correspondence.
This is a proposed regression plan, not an executed exploit reproduction.
Limits and handoff
The advisory does not establish a customer incident or exposure on a particular application. The practical output is a function-boundary worksheet, decision table and owner handoff.