Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

nvd логотип

CVE-2025-32421

Опубликовано: 14 мая 2025
Источник: nvd
CVSS3: 3.7
EPSS Низкий

Описание

Next.js is a React framework for building full-stack web applications. Versions prior to 14.2.24 and 15.1.6 have a race-condition vulnerability. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML. This issue was patched in versions 15.1.6 and 14.2.24 by stripping the x-now-route-matches header from incoming requests. Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on 200 OK status without explicit cache-control headers. Those who self-host Next.js deployments and are unable to upgrade immediately can mitigate this vulnerability by stripping the x-now-route-matches header from all incoming requests at the content development network and setting cache-control: no-store for all responses under risk. The maintainers of Next.js strongly recommend only caching responses with explicit cache-control headers.

Уязвимые конфигурации

Конфигурация 1

Одно из

cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
Версия до 14.2.24 (исключая)
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
Версия от 15.0.0 (включая) до 15.1.6 (исключая)

EPSS

Процентиль: 6%
0.00028
Низкий

3.7 Low

CVSS3

Дефекты

CWE-362

Связанные уязвимости

CVSS3: 3.7
redhat
4 месяца назад

Next.js is a React framework for building full-stack web applications. Versions prior to 14.2.24 and 15.1.6 have a race-condition vulnerability. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve `pageProps` data instead of standard HTML. This issue was patched in versions 15.1.6 and 14.2.24 by stripping the `x-now-route-matches` header from incoming requests. Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on `200 OK` status without explicit `cache-control` headers. Those who self-host Next.js deployments and are unable to upgrade immediately can mitigate this vulnerability by stripping the `x-now-route-matches` header from all incoming requests at the content development network and setting `cache-control: no-store` for all responses under risk. The maintainers of Next.js strongly recommend only caching responses with explicit cache-control headers.

CVSS3: 3.7
github
4 месяца назад

Next.js Race Condition to Cache Poisoning

EPSS

Процентиль: 6%
0.00028
Низкий

3.7 Low

CVSS3

Дефекты

CWE-362