Interpretation Conflict in Next.js - #VU130280
Published: May 6, 2026
Next.js
vercel
Description
The vulnerability allows a remote attacker to cause cache poisoning that results in component payloads being served instead of the expected HTML.
The vulnerability exists due to interpretation conflict in React Server Component response handling when shared caches do not correctly partition response variants. A remote attacker can cause an RSC response to be served from the original URL to cause cache poisoning that results in component payloads being served instead of the expected HTML.
The issue affects applications using React Server Components with shared caches under affected conditions.