Is there a public exploit for CVE-2026-44579?

Yes. Proof-of-concept code for CVE-2026-44579 has been published publicly.

Is there a proof of concept for CVE-2026-44579?

Yes — 1 proof-of-concept entry is linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-44579?

CVE-2026-44579 scores CVSS 7.5 (v3.1), rated high. EPSS puts the chance of exploitation in the next 30 days at 0.75%.

What does CVE-2026-44579 affect?

CVE-2026-44579 affects vercel next.

7.5 High

Next.js is a React framework for building full-stack web applications.

CVE-2026-44579

Impact Applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service. Fix We now treat the header used for resuming Partial Prerendered requests as an internal-only header and strip it from untrusted incoming requests. This header should never be accepted directly from external clients. Workarounds If you cannot upgrade immediately, block requests that would be handled by Next.js if they contain the Next-Resume header at the edge.

Proof-of-concept code is published

Public PoC

Public PoCiamfarzad/fbcounsulting_v2

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 7.5 (v3.1)
Severity: High
EPSS: 0.75% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC
Published: 11 May 2026
Last updated: 26 October 2026
Affected: vercel · next.js · next
Weakness: CWE-770, CWE-833
Assigner: security-advisories@github.com

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

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 3 + 7? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-44579