vercel next.js

57 vulnérabilités publiées citent ce produit.

Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.

CVEVersions vulnérablesTitreSévéritéPubliéeEPSSExploitation
CVE-2026-94482>= 13.0.0, < 15.5.28 ; >= 16.0.0, < 16.4.1Next.js: Denial of Service in App Router using Server ActionsHIGH 8.20.4 %
CVE-2026-94484>= 15.0.0, < 15.5.27 ; >= 16.0.0, < 16.3.8Next.js: Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of serviceMEDIUM 6.30.2 %
CVE-2026-94485>= 16.0.0, < 16.3.8Next.js: Information disclosure in Next.js App Router metadata image routes via dynamicParams bypassMEDIUM 6.30.2 %
CVE-2026-94483>= 16.0.0, < 16.3.8Next.js: Server-Side Request Forgery in Image OptimizationHIGH 8.30.3 %
CVE-2026-94543>= 15.0.0, < 15.5.27 ; >= 16.0.0, < 16.3.8Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applicationsMEDIUM 6.30.5 %
CVE-2026-94544>= 16.3.0, < 16.3.8Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pagesMEDIUM 6.30.2 %
CVE-2026-94486>= 16.0.0, < 16.3.8Next.js: Information disclosure in the Next.js development server's Model Context Protocol endpointLOW 2.30.1 %
CVE-2026-103004< 16.3.8next.js cache leak on warm `use cache` handlers accessing root paramMEDIUM 6.30.3 %
CVE-2026-75604>= 13.4.0, < 15.5.24 ; >= 16.0.0, < 16.3.3Next.js: Unauthenticated Remote Code Execution on windows-hosted serversCRITICAL 9.02.1 %
CVE-2026-64649>= 14.1.1, < 15.5.21 ; >= 16.0.0 < 16.2.11Next.js: Server-Side Request Forgery in Server Actions on Custom ServersHIGH 8.30.5 %
CVE-2026-64648>= 13.0.0, < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Response Body Cache Confusion for Requests Containing BodiesMEDIUM 6.00.3 %
CVE-2026-64647>= 13.0.0, < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Response Body Cache Confusion with Invalid UTF-8 Request BodiesMEDIUM 6.30.3 %
CVE-2026-64646>= 13.0.0 < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Unbounded Server Action payload in Edge runtimeMEDIUM 6.30.5 %
CVE-2026-64644>= 15.5.0, < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Denial of Service in the Image Optimization API using SVGsMEDIUM 6.30.7 %
CVE-2026-64643>= 13.0.0, < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Unauthenticated Disclosure of Internal Server Function endpointsMEDIUM 6.30.5 %
CVE-2026-64642>= 16.0.0, < 16.2.11Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single localeHIGH 8.30.6 %
CVE-2026-64641>= 13.0.0, < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Denial of Service in App Router using Server ActionsHIGH 8.20.9 %
CVE-2026-64645>= 12.0.0 < 15.5.21 ; >= 16.0.0, < 16.2.11Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostnameHIGH 8.30.4 %
CVE-2026-45109>= 15.2.0, < 15.5.17 ; >= 16.0.0, < 16.2.6Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routesHIGH 7.50.6 %
CVE-2026-44582>= 13.4.6, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Cache poisoning via collisions in React Server Component cache-bustingLOW 3.70.2 %
CVE-2026-44581>= 13.4.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Cross-site scripting in App Router applications using CSP noncesMEDIUM 4.70.2 %
CVE-2026-44580>= 13.0.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Cross-site scripting in beforeInteractive scripts with untrusted inputMEDIUM 6.10.2 %
CVE-2026-44579>= 16.0.0, < 16.2.5 ; >= 15.0.0, < 15.5.16Next.js: Denial of Service via connection exhaustion in applications using Cache ComponentsHIGH 7.50.7 %
CVE-2026-44578>= 16.0.0, < 16.2.5 ; >= 13.4.13, < 15.5.16Next.js: Server-side request forgery in applications using WebSocket upgradesHIGH 8.636 %
CVE-2026-44577>= 10.0.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Denial of Service in the Image Optimization APIHIGH 7.50.7 %
CVE-2026-44576>= 14.2.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Cache poisoning in React Server Component responsesMEDIUM 5.40.3 %
CVE-2026-44574>= 15.4.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Middleware / Proxy bypass through dynamic route parameter injectionHIGH 8.10.6 %
CVE-2026-44575>= 16.0.0, < 16.2.5 ; >= 15.2.0, < 15.5.16Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routesHIGH 7.51.6 %
CVE-2026-44573>= 12.2.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Middleware / Proxy bypass in Pages Router applications using i18nHIGH 7.50.8 %
CVE-2026-44572>= 12.2.0, < 15.5.16 ; >= 16.0.0, < 16.2.5Next.js: Middleware / Proxy redirects can be cache-poisonedMEDIUM 5.90.3 %
CVE-2026-29057>= 16.0.0-beta.0, < 16.1.7 ; >= 9.5.0, < 15.5.13Next.js: HTTP request smuggling in rewritesMEDIUM 6.30.5 %
CVE-2026-27980>= 10.0.0, < 16.1.7Next.js: Unbounded next/image disk cache growth can exhaust storageMEDIUM 6.90.7 %
CVE-2026-27979>= 16.0.1, < 16.1.7Next.js: Unbounded postponed resume buffering can lead to DoSMEDIUM 6.90.7 %
CVE-2026-27978>= 16.0.1, < 16.1.7Next.js: null origin can bypass Server Actions CSRF checksMEDIUM 5.30.2 %
CVE-2026-27977>= 16.0.1, < 16.1.7Next.js: null origin can bypass dev HMR websocket CSRF checksLOW 2.30.2 %
CVE-2025-57752>= 15.0.0, < 15.4.5 ; < 14.2.31Next.js Affected by Cache Key Confusion for Image Optimization API RoutesMEDIUM 6.20.3 %
CVE-2025-55173>= 15.0.0, < 15.4.5 ; < 14.2.31Next.js Content Injection Vulnerability for Image OptimizationMEDIUM 4.30.6 %
CVE-2025-57822< 14.2.32 ; < 15.4.7Next.js Improper Middleware Redirect Handling Leads to SSRFHIGH 8.22.6 %
CVE-2025-49826>= 15.0.4-canary.51, < 15.1.8Next.js DoS vulnerability via cache poisoningHIGH 7.51.1 %
CVE-2025-49005>= 15.3.0, < 15.3.3Next.js cache poisoning due to omission of Vary headerLOW 3.70.5 %
CVE-2025-48068>= 13.0, < 14.2.30 ; >= 15.0.0, < 15.2.2Information exposure in Next.js dev server due to lack of origin verificationLOW 2.30.2 %
CVE-2025-32421< 14.2.24 ; >= 15.0.0, < 15.1.6Next.js Race Condition to Cache PoisoningLOW 3.70.8 %
CVE-2025-30218= 12.3.5 ; = 13.5.9 ; = 14.2.25 ; …Next.js may leak x-middleware-subrequest-id to external hostsLOW 1.70.4 %
CVE-2025-29927>= 11.1.4, < 12.3.5 ; >= 14.0.0, < 14.2.25 ; >= 15.0.0, < 15.2.3 ; …Authorization Bypass in Next.js MiddlewareCRITICAL 9.199 %
CVE-2024-56332>= 13.0.0, < 13.5.8 ; >= 14.0.0, < 14.2.21 ; >= 15.0.0, < 15.1.2Next.js Vulnerable to Denial of Service (DoS) with Server ActionsMEDIUM 5.30.8 %
CVE-2024-51479>= 9.5.5, < 14.2.15Authorization bypass in Next.jsHIGH 7.54.0 %
CVE-2024-47831>= 10.0.0, < 14.2.7Next.js image optimization has Denial of Service conditionHIGH 7.50.7 %
CVE-2024-46982>= 13.5.1, < 13.5.7 ; >= 14.0.0, < 14.2.10Cache Poisoning in next.jsHIGH 7.559 %
CVE-2024-39693>= 13.3.1, < 13.5.0Next.js Denial of Service (DoS) conditionHIGH 7.50.5 %
CVE-2024-34351>= 13.4.0, < 14.1.1Next.js Server-Side Request Forgery in Server ActionsHIGH 7.55.5 %
CVE-2024-34350>= 13.4.0, < 13.5.1Next.js Vulnerable to HTTP Request SmugglingHIGH 7.51.2 %
CVE-2022-36046= 12.2.3Unexpected server crash in Next.js version 12.2.3MEDIUM 5.31.2 %
CVE-2022-23646>= 10.0.0, < 12.1.0Improper CSP in Image Optimization API for Next.jsHIGH 7.51.8 %
CVE-2021-43803>= 11.1.0, < 11.1.3 ; >= 12.0.0, < 12.0.5Unexpected server crash in Next.jsHIGH 7.547 %
CVE-2021-39178>= 10.0.0, < 11.1.1XSS in Image Optimization API for Next.js versions between 10.0.0 and 11.1.0HIGH 7.51.1 %
CVE-2021-37699< 11.1.0Open Redirect in Next.js versions below 11.1.0MEDIUM 6.91.0 %
CVE-2020-15242>= 9.5.0, <9.5.4Open Redirect in Next.jsMEDIUM 6.10.8 %