Review reviewHigh

CVE-2026-44579

vercel next.js, Streams for Apache Kafka 2.9.4, Red Hat Trusted Artifact Signer 1.4

Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, 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. This vulnerability is fixed in 15.5.16 and 16.2.5.

CVSS
7.5
EPSS
0.71%
50.1% percentile
CISA KEV
Not listed
Published
2026.05.14
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.71%
Technical severityCVSS 7.5

Vulnerability overview

Next.js is a React framework for building full-stack web applications. From to before 15.5.16 and 16.2.5, 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. This vulnerability is fixed in 15.5.16 and 16.2.5.

Affected product and versions

Product
vercel next.js, Streams for Apache Kafka 2.9.4, Red Hat Trusted Artifact Signer 1.4
Affected versions
>= >= 16.0.0, < 16.2.5, >= >= 15.0.0, < 15.5.16, >= 15.0.0 < 15.5.16, >= 16.0.0 < 16.2.5
Fixed versions
15.5.16, 16.2.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that vercel next.js, Streams for Apache Kafka 2.9.4, Red Hat Trusted Artifact Signer 1.4 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
CWE-770, CWE-833