CVE-2025-57752
Vercel Next.Js ≤ 14.2.31
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-57752 is a medium-severity Use of Cache Containing Sensitive Information (CWE-524) vulnerability in Vercel Next.Js. Its CVSS base score is 6.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-28624
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so that cached sensitive data cannot be read by actors outside the intended sphere.
Directly prevents unauthorized transfer of information through shared resources such as caches.
Controls information flows to keep sensitive data from leaving its authorized control sphere via caches.
Requires cryptographic or other protection of sensitive information at rest, which covers cached data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Protecting confidentiality of data-at-rest covers caches that persist sensitive information.
Enforcing least-privilege access permissions directly limits who can read cached sensitive data.
Protecting data-in-use can mitigate exposure when caches hold transient sensitive values.
Logical access controls on environments reduce the chance an outsider can reach the cache.
Hardened configuration baselines can disable or secure caching of sensitive data.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Data leakage prevention can block unauthorized access to cached sensitive information.
Information access restriction directly limits who can read cached sensitive data.
Information deletion ensures sensitive data is removed from caches when no longer needed.
Cryptography can protect cached data at rest, but does not address access control scope.
Secure coding practices prevent caching of sensitive data outside intended boundaries.
Environment separation reduces risk of cache exposure across development/test/production.