Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-44576

Next.js: Cache poisoning in React Server Component responses

Medium5.4EPSS 0.29%
Published
Updated
Reserved
Assigned by
GitHub_M

Description

Next.js is a React framework for building full-stack web applications. From 14.2.0 to before 15.5.16 and 16.2.5, 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. This vulnerability is fixed in 15.5.16 and 16.2.5.

Scores

CVSS scores of CVE-2026-44576, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1Medium5.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
NVDNVD · Analyzed3.1Medium5.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.

Weakness

Affected products

  • vercel · next.js

    • affected >= 14.2.0, < 15.5.16
    • affected >= 16.0.0, < 16.2.5

Affected packages

From reviewed advisories of the GitHub Advisory Database.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-44576 badge
[![CVE-2026-44576](https://trackcve.app/badge/CVE-2026-44576.svg)](https://trackcve.app/cve/CVE-2026-44576)

Record last updated .