
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-119349 is a cache disclosure and cache poisoning vulnerability affecting Next.js 16.x applications. Specifically, applications that use cache with binary arguments passed to a shared function are vulnerable to cross-user cache disclosure and cache poisoning attacks. The CVE is currently in "Reserved" status, indicating it is in early stages of public disclosure. It was first indexed by Feedly on November 3, 2026, with a related Netlify changelog entry referencing Next.js security vulnerabilities (Netlify Changelog). No CVSS score has been publicly assigned at this time.
The vulnerability arises in Next.js 16.x when the caching mechanism processes binary arguments passed to a shared function, leading to improper cache key generation or cache boundary enforcement (consistent with CWE-524: Use of Cache Containing Sensitive Information). This flaw can allow one user's cached response — potentially containing sensitive data — to be served to another user (cross-user cache disclosure), or allow an attacker to inject malicious content into the cache that is subsequently served to other users (cache poisoning). The specific conditions require that the application actively uses Next.js caching features with binary argument inputs to shared/cached functions (Netlify Changelog).
Successful exploitation can result in sensitive user data being disclosed to unauthorized parties via cross-user cache leakage, compromising confidentiality. Cache poisoning attacks could allow an attacker to serve malicious or manipulated content to other users of the application, impacting integrity. In multi-tenant or high-traffic Next.js 16.x deployments, the blast radius could be significant, potentially exposing session data, personal information, or application secrets cached between requests.
No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported for CVE-2026-119349 at this time. The CVE remains in "Reserved" status, and no EPSS score or CISA KEV catalog listing has been assigned. Exploitation requires that the target application uses Next.js 16.x with caching enabled and binary arguments passed to shared functions, which narrows the attack surface to specific application configurations (Netlify Changelog).
Developers should review the Netlify changelog and official Next.js security advisories for patched versions addressing this vulnerability. As an immediate workaround, avoid passing binary arguments to shared cached functions in Next.js 16.x, or disable caching for functions that handle user-specific or sensitive data until a patch is applied. Monitor for updated Next.js releases that address this cache handling flaw and apply them promptly (Netlify Changelog).
Netlify published a changelog entry on November 3, 2026, referencing multiple Next.js security vulnerabilities including this issue, suggesting awareness among hosting providers of the risk to deployed Next.js applications (Netlify Changelog). No significant broader community or social media discussion has been identified at this stage given the early disclosure status.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."