fkie_cve-2025-49005
Vulnerability from fkie_nvd
Published
2025-07-03 21:15
Modified
2025-07-08 16:19
Severity ?
Summary
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.
References
Impacted products
Vendor | Product | Version |
---|
{ "cveTags": [], "descriptions": [ { "lang": "en", "value": "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." }, { "lang": "es", "value": "Next.js es un framework React para crear aplicaciones web full-stack. En Next.js App Router (versi\u00f3n 15.3.0) y versiones anteriores a la 15.3.3, y en Vercel CLI (versi\u00f3n 41.4.1) a la 42.2.0, se detect\u00f3 una vulnerabilidad de envenenamiento de cach\u00e9. Este problema permit\u00eda que las solicitudes de contenido HTML devolvieran un payload de React Server Component (RSC) en ciertas condiciones. Al implementarse en Vercel, esto solo afectaba a la cach\u00e9 del navegador y no provocaba el envenenamiento de la CDN. Al alojarse en la propia aplicaci\u00f3n y desplegarse externamente, esto pod\u00eda provocar el envenenamiento de cach\u00e9 si la CDN no distingue correctamente entre RSC y HTML en las claves de cach\u00e9. Este problema se ha resuelto en Next.js 15.3.3." } ], "id": "CVE-2025-49005", "lastModified": "2025-07-08T16:19:11.700", "metrics": { "cvssMetricV31": [ { "cvssData": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 3.7, "baseSeverity": "LOW", "confidentialityImpact": "NONE", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N", "version": "3.1" }, "exploitabilityScore": 2.2, "impactScore": 1.4, "source": "security-advisories@github.com", "type": "Secondary" } ] }, "published": "2025-07-03T21:15:26.787", "references": [ { "source": "security-advisories@github.com", "url": "https://github.com/vercel/next.js/commit/ec202eccf05820b60c6126d6411fe16766ecc066" }, { "source": "security-advisories@github.com", "url": "https://github.com/vercel/next.js/issues/79346" }, { "source": "security-advisories@github.com", "url": "https://github.com/vercel/next.js/releases/tag/v15.3.3" }, { "source": "security-advisories@github.com", "url": "https://github.com/vercel/next.js/security/advisories/GHSA-r2fc-ccr8-96c4" }, { "source": "security-advisories@github.com", "url": "https://vercel.com/changelog/cve-2025-49005" }, { "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "url": "https://github.com/vercel/next.js/issues/79346" } ], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Awaiting Analysis", "weaknesses": [ { "description": [ { "lang": "en", "value": "CWE-444" } ], "source": "security-advisories@github.com", "type": "Secondary" } ] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…