CVE-2026-44576
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNext.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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNext.js versions 14.2.0 through 15.5.15 and before 16.2.5 contain a cache poisoning vulnerability in React Server Components. When shared caches fail to correctly partition response variants, an attacker can poison cache entries so subsequent visitors receive RSC component payloads instead of the expected HTML from the original URL.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 14.2.0, < 15.5.16>= 16.0.0, < 16.2.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Next.js versionRun `npm list next` in the project directory or check the package.json dependencies fieldAffected if Version is 14.2.0 through 15.5.15, or 16.0.0 through 16.2.4
-
Confirm React Server Components are in useCheck if the application uses the App Router (app directory) or explicitly imports from 'react' server components, which is the default behavior in Next.js 14.2+Affected if App Router is used, as RSC is enabled by default in affected versions
-
Verify caching is enabledInspect next.config.js or next.config.mjs for caching configurations such as `experimental` or `experimental` settings, or check for use of `unstable_cache` / `cache` functions in the codebaseAffected if Any form of RSC caching or shared cache mechanisms are configured
User is affected if Next.js version falls within 14.2.0 to 15.5.15 or 16.0.0 to 16.2.4, and the application uses React Server Components with caching enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.5.1616.2.5
Upgrade Next.js to version 15.5.16 or 16.2.5 or later. Review application caching configurations and consider implementing additional cache validation to ensure proper response partitioning.
Next.js 15.5.16 (for v15 line) or 16.2.5 (for v16 line)
- Check current Next.js version in package.json or package-lock.json
- If using Next.js 15.x, run: npm install [email protected] or yarn add [email protected]
- If using Next.js 16.x, run: npm install [email protected] or yarn add [email protected]
- Clear any shared cache layers (e.g., CDN, reverse proxy) to remove poisoned entries
- Verify the upgrade by running your test suite, particularly any RSC-related tests
- Deploy and monitor for any issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44576 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data