Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. next
  4. ›
  5. CVE-2026-44576

CVE-2026-44576: Next.js vulnerable to cache poisoning in React Server Component responses

May 11, 2026 (updated May 14, 2026)

Applications using React Server Components can be vulnerable to cache poisoning when shared caches do not correctly partition response variants. Under affected conditions, an attacker can cause an RSC response to be served from the original URL and poison shared cache entries so later visitors receive component payloads instead of the expected HTML.

References

  • github.com/advisories/GHSA-wfc6-r584-vfw7
  • github.com/vercel/next.js/releases/tag/v15.5.16
  • github.com/vercel/next.js/releases/tag/v16.2.5
  • github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7
  • nvd.nist.gov/vuln/detail/CVE-2026-44576

Code Behaviors & Features

Detect and mitigate CVE-2026-44576 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 14.2.0 before 15.5.16, all versions starting from 16.0.0 before 16.2.5

Fixed versions

  • 15.5.16
  • 16.2.5

Solution

Upgrade to versions 15.5.16, 16.2.5 or above.

Impact 5.4 MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L

Learn more about CVSS

Weakness

  • CWE-436: Interpretation Conflict

Source file

npm/next/CVE-2026-44576.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Tue, 23 Jun 2026 12:22:18 +0000.