
PEACH
Un cadre d’isolation des locataires
CVE-2026-119790 is an information disclosure vulnerability in Next.js affecting applications that use Cache Components (such as unstable_cache) when a function is called both directly and through different invocation paths (e.g., via root params). The vulnerability affects Next.js 16.3+ applications that use Cache Components calling the same function directly and through different invocation paths, potentially causing cross-request data leakage. As of the time of this report, the CVE status is listed as "Reserved" and no official CVSS score has been published, though Feedly estimates the severity as Medium (Feedly, Netlify Changelog).
The root cause of CVE-2026-119790 is improper isolation of cached data across different invocation paths in Next.js Cache Components (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor). When a function is invoked both directly and through root params within the same cached context, Next.js 16.3+ may inadvertently share or leak cached state between these invocation paths, resulting in information disclosure. This issue is specific to applications that use unstable_cache or similar caching primitives and call the same underlying function through multiple code paths (Netlify Changelog, BestPractic Blog).
Successful exploitation of this vulnerability can result in unintended disclosure of sensitive data cached from one request or invocation path being exposed to another, potentially leaking user-specific or request-specific information across different users or sessions. The confidentiality impact is the primary concern, as cached data (which may include authentication tokens, personal data, or application state) could be exposed to unauthorized parties. Integrity and availability are not directly impacted, but data leakage could facilitate further attacks such as session hijacking or privilege escalation (Feedly, BrandDefense).
No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported for CVE-2026-119790 as of this writing. The CVE remains in "Reserved" status, and no EPSS score or CISA KEV catalog entry has been published. Exploitation would require an attacker to interact with a Next.js 16.3+ application that uses Cache Components with the specific invocation pattern described, limiting the attack surface to applications with this particular architectural pattern (Feedly, Netlify Changelog).
Developers should audit their Next.js 16.3+ applications for use of unstable_cache or similar Cache Components where the same function is called both directly and through root params or different invocation paths. Until an official patch is released, consider refactoring code to avoid calling the same function through multiple invocation paths within cached contexts, or disable caching for affected functions. Monitor the official Next.js security advisories and the Netlify changelog for patch releases and further guidance (Netlify Changelog, BestPractic Blog).
Netlify published a changelog entry on November 3, 2026, acknowledging Next.js security vulnerabilities including this issue, indicating awareness among major Next.js hosting providers. BrandDefense noted that React RSC-related vulnerabilities may go undetected by CVE scanners, highlighting a broader concern about tooling gaps in detecting framework-level cache vulnerabilities. Community discussion has emerged around the risks of unstable_cache usage patterns in Next.js applications (Netlify Changelog, BrandDefense, BestPractic Blog).
Source: Ce rapport a été généré à l’aide de l’IA
Évaluation gratuite des vulnérabilités
Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."