Next.js weak _rsc cache-busting hash cache poisoning
CVE-2026-44582 is a low-severity cache poisoning vulnerability in Next.js affecting versions from 13.4.6 before 15.5.16 and before 16.2.5. The issue affects React Server Component (RSC) responses in deployments that rely on shared caches that do not sufficiently partition response variants. According to the provided content, the _rsc cache-busting value is weak enough that collisions can occur. Under affected caching conditions, an attacker can induce collisions in this _rsc value and poison cached entries, causing subsequent requests for a given URL to be served an incorrect response variant. The flaw is therefore tied to the interaction between Next.js RSC response handling and intermediary/shared cache behavior rather than a purely client-side issue.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Vary semantics for RSC-related request differences. Review CDN, reverse proxy, and other shared-cache configurations to prevent cache key collisions across distinct RSC response variants.Remediation
Patch, then assume compromise.
Exploits
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.