Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

vercel — Vulnerabilities & Security Advisories 65

Browse all 65 CVE security advisories affecting vercel. AI-powered Chinese analysis, POCs, and references for each vulnerability.

Vercel operates as a cloud platform for frontend development, primarily hosting static sites and serverless functions. With thirty-five recorded Common Vulnerabilities and Exposures, the platform has historically faced issues ranging from Cross-Site Scripting (XSS) to Remote Code Execution (RCE). These vulnerabilities often stem from complex dependency chains or misconfigured serverless environments rather than fundamental architectural flaws. Notable incidents have included data exposure risks due to improper header configurations and potential privilege escalation through flawed API access controls. While the platform emphasizes rapid deployment, its reliance on third-party libraries and dynamic runtime environments introduces attack surfaces that require rigorous input validation and secure coding practices. Security audits frequently highlight the need for strict isolation between tenant environments to prevent cross-tenant data leakage, ensuring that the convenience of serverless architecture does not compromise overall system integrity.

Found 48 results / 65Clear Filters
CVE IDTitleCVSSSeverityPublished
CVE-2026-64649 Next.js: Server-Side Request Forgery in Server Actions on Custom Servers — next.jsCWE-918 8.3 High2026-07-27
CVE-2026-64648 Next.js: Response Body Cache Confusion for Requests Containing Bodies — next.jsCWE-524 6.0 Medium2026-07-27
CVE-2026-64647 Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies — next.jsCWE-116 6.3 Medium2026-07-27
CVE-2026-64646 Next.js: Unbounded Server Action payload in Edge runtime — next.jsCWE-770 6.3 Medium2026-07-27
CVE-2026-64644 Next.js: Denial of Service in the Image Optimization API using SVGs — next.jsCWE-407 6.3 Medium2026-07-27
CVE-2026-64643 Next.js: Unauthenticated Disclosure of Internal Server Function endpoints — next.jsCWE-201 6.3 Medium2026-07-27
CVE-2026-64642 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale — next.jsCWE-285 8.3 High2026-07-27
CVE-2026-64641 Next.js: Denial of Service in App Router using Server Actions — next.jsCWE-834 8.2 High2026-07-27
CVE-2026-64645 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname — next.jsCWE-918 8.3 High2026-07-27
CVE-2026-45109 Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes — next.jsCWE-288 7.5 High2026-05-13
CVE-2026-44582 Next.js: Cache poisoning via collisions in React Server Component cache-busting — next.jsCWE-328 3.7 Low2026-05-13
CVE-2026-44581 Next.js: Cross-site scripting in App Router applications using CSP nonces — next.jsCWE-79 4.7 Medium2026-05-13
CVE-2026-44580 Next.js: Cross-site scripting in beforeInteractive scripts with untrusted input — next.jsCWE-79 6.1 Medium2026-05-13
CVE-2026-44579 Next.js: Denial of Service via connection exhaustion in applications using Cache Components — next.jsCWE-770 7.5 High2026-05-13
CVE-2026-44578 Next.js: Server-side request forgery in applications using WebSocket upgrades — next.jsCWE-918 8.6 High2026-05-13
CVE-2026-44577 Next.js: Denial of Service in the Image Optimization API — next.jsCWE-770 5.9 Medium2026-05-13
CVE-2026-44576 Next.js: Cache poisoning in React Server Component responses — next.jsCWE-436 5.4 Medium2026-05-13
CVE-2026-44574 Next.js: Middleware / Proxy bypass through dynamic route parameter injection — next.jsCWE-288 8.1 High2026-05-13
CVE-2026-44575 Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes — next.jsCWE-288 7.5 High2026-05-13
CVE-2026-44573 Next.js: Middleware / Proxy bypass in Pages Router applications using i18n — next.jsCWE-863 7.5 High2026-05-13
CVE-2026-44572 Next.js: Middleware / Proxy redirects can be cache-poisoned — next.jsCWE-349 3.7 Low2026-05-13
CVE-2026-29057 Next.js: HTTP request smuggling in rewrites — next.jsCWE-444 9.1 -2026-03-18
CVE-2026-27980 Next.js: Unbounded next/image disk cache growth can exhaust storage — next.jsCWE-400 6.5 -2026-03-18
CVE-2026-27979 Next.js: Unbounded postponed resume buffering can lead to DoS — next.jsCWE-770 5.4 -2026-03-18
CVE-2026-27978 Next.js: null origin can bypass Server Actions CSRF checks — next.jsCWE-352 8.8 -2026-03-17
CVE-2026-27977 Next.js: null origin can bypass dev HMR websocket CSRF checks — next.jsCWE-1385 7.1 -2026-03-17
CVE-2025-57752 Next.js Affected by Cache Key Confusion for Image Optimization API Routes — next.jsCWE-524 6.2 Medium2025-08-29
CVE-2025-55173 Next.js Content Injection Vulnerability for Image Optimization — next.jsCWE-20 4.3 Medium2025-08-29
CVE-2025-57822 Next.js Improper Middleware Redirect Handling Leads to SSRF — next.jsCWE-918 6.5 Medium2025-08-29
CVE-2025-49826 Next.js DoS vulnerability via cache poisoning — next.jsCWE-444 7.5 High2025-07-03

This page lists every published CVE security advisory associated with vercel. Each entry links to a detailed page with CVSS scoring, CWE classification, affected products and references. AI-generated Chinese analysis is provided for fast triage.