CVE-2025-57752VulnerabilityPublished 29 Aug 2025Updated 2 Sep 2025

CVE-2025-57752: vercel next.js · Use of Cache Containing Sensitive Information

Affects vercel next.jsSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium : upgrade to 14.2.31 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 14.2.31

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vercel next.js to 14.2.31.

Affected software

Product	Affected	Fixed in
vercel next.js	Affected <14.2.31	Fixed in 14.2.31

AI-suggested

1. Immediate upgrade: Organizations should upgrade all affected Next.js instances to versions 14.2.31 or 15.4.5 or later, where the vulnerability is patched. 2. Cache configuration review: Review and adjust cache key configurations to ensure that all headers influencing the response (e.g., Authorization, Cookie) are included in the cache key to prevent cross-user cache leakage. 3. Audit API routes: Identify all API routes serving images that vary based on request headers and verify that they are not vulnerable to cache key confusion. 4. Implement strict access controls: Restrict access to internal networks and API endpoints to reduce the risk of local attackers exploiting the vulnerability. 5. Monitoring and logging: Enable detailed logging of image API requests and cache hits/misses to detect anomalous access patterns that may indicate exploitation attempts. 6. Security testing: Conduct penetration testing focusing on cache behavior and header-based response variations to confirm the vulnerability is mitigated. 7. User education: Inform development teams about secure caching practices and the importance of including all relevant request headers in cache keys when serving sensitive content. 8. Incident response planning: Prepare to respond to potential data leakage incidents, including notification procedures compliant with GDPR.

Description

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.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive image data served via Next.js applications. Organizations that rely on Next.js for web applications that serve personalized or sensitive images—such as healthcare providers, financial institutions, e-commerce platforms, or government services—could inadvertently expose private user data to unauthorized parties. This could lead to data privacy violations under GDPR, resulting in regulatory penalties and reputational damage. Since the vulnerability allows unauthorized users to receive cached images intended for others without requiring authentication or user interaction, the risk of data leakage is elevated. The impact is particularly critical for applications that use authentication tokens or cookies to deliver user-specific images, as these images could be cached and served incorrectly. Although the attack vector is local, meaning the attacker must have some level of access to the network or application environment, the ease of exploitation is low complexity and does not require privileges, increasing the threat surface. The lack of impact on integrity and availability means the primary concern is confidentiality loss. European organizations with public-facing Next.js applications or internal apps accessible within corporate networks should assess their exposure promptly.

CWE-524Use of Cache Containing Sensitive Information (opens in a new tab)
Base weakness
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
Architecture and Design
Protect information stored in cache.
Architecture and Design
Do not store unnecessarily sensitive information in the cache.
Architecture and Design
Consider using encryption in the cache.
OWASP ASVS 4.0.3
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Sep 2025, 00:32 UTC

WeaknessesCWE-524

Technical details

References

Community reviews

Related threats