Review reviewHigh

CVE-2026-44573

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

Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5.

CVSS
7.5
EPSS
0.61%
45.6% 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.61%
Technical severityCVSS 7.5

Vulnerability overview

Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. 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.3
Affected versions
>= >= 12.2.0, < 15.5.16, >= >= 16.0.0, < 16.2.5, >= 12.2.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.3 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:H/I:N/A:N
CWE
CWE-551, CWE-863