CVE-2026-44582

low

Published 2026-05-13 · Modified 2026-05-14

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

3.7

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

CVSS v4 NEW

—

not yet in upstream

VIR risk

3.7

Description

Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting

Predictions

Exploit likelihood

47%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

Package impact

Ecosystem	Package	Vulnerable	Fixed
npm	next	`>=13.4.6,<15.5.16`	`15.5.16`
npm	next	`>=16.0.0,<16.2.5`	`16.2.5`
NPM	next	`>= 16.0.0, < 16.2.5`	`16.2.5`
NPM	next	`>= 13.4.6, < 15.5.16`	`15.5.16`

Application impact

Vendor	Product	Versions	Fixed
vercel	next.js	`{"startIncluding":"13.4.6","endExcluding":"15.5.16"}`	`15.5.16`

References

CWEs

CWE-328

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.