NPM · SEPTEMBER 2026 · EARLY WARNING

Next.js Vulnerability on Windows Servers: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

Severity: HIGH
Affected component: next.js (npm)
Patched version: Not yet available

GHSA-P293-QW3H-JR36

An early warning has been issued for a critical vulnerability in Next.js applications that use Pages and App router without Cache Component. This vulnerability can lead to remote code execution when the server is hosted on machines using a Windows filesystem.

What happened

An early warning has been issued for a critical vulnerability in Next.js applications. This vulnerability, tracked as GHSA-p293-qw3h-jr36, can lead to unauthenticated remote code execution on servers hosted on Windows machines. The vulnerability affects Next.js applications that use Pages and App router without Cache Component. The issue was first flagged on September 8, 2026.

The vulnerability is particularly dangerous because it allows remote code execution without any authentication. This means that an attacker could potentially take over the server if they exploit this vulnerability. The vulnerability has not been exploited in the wild yet, but it is under investigation.

What to do about it

Upgrade to the latest version of Next.js to mitigate the risk.
Consider alternative hosting solutions if your server is using a Windows filesystem.
Monitor the primary sources for updates on this vulnerability.
No official fix has been published yet. Continue to monitor the situation and apply any patches as soon as they become available.

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If next.js is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You may be affected if you are using Next.js applications that use Pages and App router without Cache Component and your server is hosted on a Windows machine.

What should I do right now?

Upgrade to the latest version of Next.js and consider alternative hosting solutions if your server is using a Windows filesystem. Monitor the primary sources for updates on this vulnerability.

Has this vulnerability been exploited in the wild?

No, this vulnerability has not been exploited in the wild yet. It is currently under investigation.

Sources

Join the 0Day waitlist →

← Back to all threats