Skip to content
Fencer Intel
medium 6.2

CVE-2025-57752 json

Next.js Affected by Cache Key Confusion for Image Optimization API Routes

published last yr. modified 22d ago also EUVD-2025-28624 , GHSA-g5qg-72qw-gw5v

cvss
6.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

Next.js is a React framework for building full-stack web applications. In versions before 14.2.31 and from 15.0.0 to before 15.4.5, Next.js Image Optimization API routes are affected by cache key confusion. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug. This vulnerability has been fixed in Next.js versions 14.2.31 and 15.4.5. All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.

Patch / fix

  • npm next 14.2.31, 15.4.5
  • vercel next.js 14.2.31, 15.4.5

Is CVE-2025-57752 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-57752 updated cvss 6.2

nextjs: Next.js Affected by Cache Key Confusion for Image Optimization API Routes

  • Red Hat Enterprise Linux 7 firefox Red Hat Enterprise Linux 8 firefox, thunderbird Red Hat Enterprise Linux 9 firefox, dotnet7.0, dotnet-host, firefox-x11, thunderbird, dotnet-sdk-7.0, +9 more Red Hat Enterprise Linux 10 firefox, thunderbird Red Hat Trusted Artifact Signer rhtas/rekor-search-ui-rhel9 Red Hat streams for Apache Kafka 2 com.github.streamshub-console
    +1 more products
    Red Hat streams for Apache Kafka 3 com.github.streamshub-console
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm next
>=0.9.9, <14.2.31
>=15.0.0, <15.4.5
14.2.31
15.4.5

Affected products

  • vercel next.js

Classification

Weakness
  • CWE-524 Use of Cache Containing Sensitive Information
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.