Skip to content
Noroxi
CVE-2025-57752· NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 24/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: next (npm) 14.2.31, 15.4.5.

Low priority for now. Upgrade to next (npm) 14.2.31, 15.4.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.2 · v3.1—No exploit Fix available
Published
Aug 29, 2025
Updated
Oct 18, 2026
EPSS
0.3% · 26th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.2
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-57752

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for vercel records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
vercelnext.js

Is the Next.js on your site affected?

The free JavaScript library scanner reads the Next.js version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.

Scan JavaScript libraries

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • vercel next.jsbefore 14.2.31
  • vercel next.js15.0.0 and later · before 15.4.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • vercel next.js

    • >= 15.0.0, < 15.4.5, < 14.2.31affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmnextfrom 0.9.9 · before 14.2.3114.2.31
npmnextfrom 15.0.0 · before 15.4.515.4.5

Same product

vercel: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-29927Authorization Bypass in Next.js Middleware
    66This week
  • CVE-2026-75604Next.js: Unauthenticated Remote Code Execution on windows-hosted servers
    60This week
  • CVE-2024-46982Cache Poisoning in next.js
    48Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-49826Jul 3, 2025 · Next.js DoS vulnerability via cache poisoning
    30Monitor
  • ← EarlierCVE-2025-55173Aug 29, 2025 · Next.js Content Injection Vulnerability for Image Optimization
    17Monitor
  • Later →CVE-2025-57822Aug 29, 2025 · Next.js Improper Middleware Redirect Handling Leads to SSRF
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:next14.2.31Package registry (OSV)
npm:next15.4.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-103004398 days apartnext.js cache leak on warm `use cache` handlers accessing root param
    25Monitor
  • CVE-2026-94484399 days apartNext.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service
    25Monitor
  • CVE-2026-94543399 days apartNext.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications
    25Monitor
  • CVE-2026-94544399 days apartNext.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages
    25Monitor
  • CVE-2026-64648332 days apartNext.js: Response Body Cache Confusion for Requests Containing Bodies
    24Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-524 · Use of Cache Containing Sensitive Information

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records