⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5.9

How to Fix CVE-2026-44577: Denial of Service in next.js

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 5.9 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected>= 10.0.0, < 15.5.16, >= 16.0.0, < 16.2.5
Fixed in15.5.16
Type (CWE)CWE-770: Allocation of Resources Without Limits or Throttling

What is CVE-2026-44577?

CVE-2026-44577 is a denial of service flaw in next.js. A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor description: Next.js is a React framework for building full-stack web applications. From 10.0.0 to before 15.5.16 and 16.2.5, when self-hosting Next.js with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit.

Why this CVE matters

Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.

For deployments of next.js that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open next.js's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-44577

  1. Read the vendor advisory in full: https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh
  2. Upgrade next.js to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Update the npm package


# CVE-2026-44577 affects next.js >= 10.0.0, < 15.5.16. Fixed in 15.5.16.
# Vendor advisory: https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh

# 1. Show the currently resolved version inside the project.
npm ls next.js

# 2. Update to the patched release named in the advisory.
npm install next.js@15.5.16
npm audit fix

# 3. Lock-file enforcement for CI / production.
npm ci

# 4. Verify.
npm ls next.js
# The resolved version must match 15.5.16 (or a later patched release).


# Same flow from a Windows admin workstation.
npm install next.js@15.5.16
npm ls next.js

Verify the fix landed


# CVE-2026-44577 verification checklist.

# 1. Confirm the running version matches 15.5.16 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-44577.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh

If you cannot patch immediately

Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-44577 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-44577?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for next.js run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*