CVE-2025-49005 Vulnerability Analysis & Exploit Details

CVE-2025-49005
Vulnerability Scoring

3.7
/10
Moderate Risk

Exploiting CVE-2025-49005 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-49005 Details

Status: Analyzed

Last updated: 🕖 10 Sep 2025, 19:14 UTC
Originally published on: 🕘 03 Jul 2025, 21:15 UTC

Time between publication and last update: 68 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-49005 Vulnerability Summary

CVE-2025-49005: Next.js is a React framework for building full-stack web applications. In Next.js App Router from 15.3.0 to before 15.3.3 and Vercel CLI from 41.4.1 to 42.2.0, a cache poisoning vulnerability was found. The issue allowed page requests for HTML content to return a React Server Component (RSC) payload instead under certain conditions. When deployed to Vercel, this would only impact the browser cache, and would not lead to the CDN being poisoned. When self-hosted and deployed externally, this could lead to cache poisoning if the CDN does not properly distinguish between RSC / HTML in the cache keys. This issue has been resolved in Next.js 15.3.3.

Assessing the Risk of CVE-2025-49005

Access Complexity Graph

The exploitability of CVE-2025-49005 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-49005

CVE-2025-49005 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-49005, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-49005, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-49005 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2025-49005 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2025-49005 does not impact system availability.

CVE-2025-49005 References

External References

CWE Common Weakness Enumeration

CWE-444

CAPEC Common Attack Pattern Enumeration and Classification

  • HTTP Response Smuggling CAPEC-273 An adversary manipulates and injects malicious content in the form of secret unauthorized HTTP responses, into a single HTTP response from a vulnerable or compromised back-end HTTP agent (e.g., server). See CanPrecede relationships for possible consequences. Modification/manipulation of HTTP message headers, request-line and body parameters to disrupt and interfere in the interpretation and parsing of HTTP message lengths/boundaries for consecutive HTTP messages by HTTP agents in a HTTP chain or network path.
  • HTTP Request Smuggling CAPEC-33 An adversary abuses the flexibility and discrepancies in the parsing and interpretation of HTTP Request messages using various HTTP headers, request-line and body parameters as well as message sizes (denoted by the end of message signaled by a given HTTP header) by different intermediary HTTP agents (e.g., load balancer, reverse proxy, web caching proxies, application firewalls, etc.) to secretly send unauthorized and malicious HTTP requests to a back-end HTTP agent (e.g., web server). See CanPrecede relationships for possible consequences. Modification/manipulation of HTTP message headers, request-line and body parameters to disrupt and interfere in the interpretation and parsing of HTTP message lengths/boundaries for consecutive HTTP messages by HTTP agents in a HTTP chain or network path.

Vulnerable Configurations

  • cpe:2.3:a:vercel:next.js:15.3.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary11:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary11:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary12:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary12:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary13:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary13:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary14:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary14:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary15:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary15:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary16:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary16:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary17:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary17:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary18:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary18:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary19:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary19:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary20:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary20:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary21:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary21:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary22:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary22:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary23:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary23:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary24:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary24:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary25:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary25:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary26:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary26:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary27:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary27:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary28:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary28:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary29:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary29:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary30:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary30:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary31:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary31:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary32:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary32:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary33:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary33:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary34:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary34:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary35:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary35:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary36:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary36:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary37:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary37:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary38:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary38:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary39:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary39:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary40:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary40:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary41:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary41:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary42:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary42:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary43:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary43:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary44:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary44:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary45:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary45:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary46:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary46:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.0:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.0:canary9:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary11:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary11:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary12:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary12:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary13:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary13:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary14:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary14:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary15:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary15:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.1:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.1:canary9:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:15.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:15.3.2:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2025-49005: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-11940 – A security vulnerability has been detected in LibreWolf up to 143.0.4-1 on Windows. This affects an unknown function of the file assets/setup.nsi o...
  • CVE-2025-11939 – A vulnerability was determined in ChurchCRM up to 5.18.0. This issue affects some unknown processing of the file src/ChurchCRM/Backup/RestoreJob.ph...
  • CVE-2025-11938 – A vulnerability was found in ChurchCRM up to 5.18.0. This vulnerability affects unknown code of the file setup/routes/setup.php. Performing manipul...
  • CVE-2025-62672 – rplay through 3.3.2 allows attackers to cause a denial of service (SIGSEGV and daemon crash) or possibly have unspecified other impact. This occurs...
  • CVE-2025-47410 – Apache Geode is vulnerable to CSRF attacks through GET requests to the Management and Monitoring REST API that could allow an attacker who has tric...