CVE-2026-44578
Next.js May 2026 coordinated security release (13 advisories): SSRF via the middleware/proxy request path, plus middleware and proxy bypass CVE-2026-44573, cache poisoning on middleware redirects CVE-2026-44572 and image-optimizer DoS CVE-2026-44577
- Severity
- high
- Affected product
- Next.js
- Affected versions
- Next.js ≥ 16.0.0, < 16.2.6
- Affected versions
- Next.js ≥ 15.0.0, < 15.5.18
- Fixed in
- Next.js 16.2.6
- Fixed in
- Next.js 15.5.18
- Detection basis
- Component version range
- Shipped rule
- Next.js: Next.js May 2026 coordinated security release (13 advisories): SSRF via the middleware/proxy request path, plus middleware and proxy bypass CVE-2026-44573, cache poisoning on middleware redirects CVE-2026-44572 and image-optimizer DoS CVE-2026-44577
- Added to NewScan
- 2026-07-30
- Detected by
- NewScan — free, self-hosted
How NewScan reports it
COMPONENT VERSION RANGE
NewScan fingerprints Next.js from its response and reports this CVE when the detected version falls inside the affected range below.
COMPONENT VERSION RANGE
NewScan fingerprints Next.js from its response and reports this CVE when the detected version falls inside the affected range below.
Related CVEs covered by this detection
The same shipped rule and upgrade also cover these identifiers:
References
Scan for this yourself — local, in-band scanning is free.
Get NewScan (FREE) →Review the measured benchmark, then use the verified remediation process.