https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 01:53:18 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-00538 bdu:2025-00538 https://cve.radiocsirt.org/vuln/bdu:2025-00538 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0481 certfr-2025-avi-0481 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0481 https://cve.radiocsirt.org/vuln/euvd-2026-208973 EUVD-2026-208973 https://cve.radiocsirt.org/vuln/euvd-2026-208973 https://cve.radiocsirt.org/vuln/fkie_cve-2024-56332 <p>Next.js is a React framework for building full-stack web applications. Starting in version 13.0.0 and prior to versions 13.5.8, 14.2.21, and 15.1.2, Next.js is vulnerable to a Denial of Service (DoS) attack that allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. This vulnerability can also be used as a Denial of Wallet (DoW) attack when deployed in providers billing by response times. (Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.). Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. The issue was resolved in Next.js 13.5.8, 14.2.21, and 15.1.2. We recommend that users upgrade to a safe version. There are no official workarounds.</p> <p>Next.js is a React framework for building full-stack web applications. Starting in version 13.0.0 and prior to versions 13.5.8, 14.2.21, and 15.1.2, Next.js is vulnerable to a Denial of Service (DoS) attack that allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. This vulnerability can also be used as a Denial of Wallet (DoW) attack when deployed in providers billing by response times. (Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.). Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. The issue was resolved in Next.js 13.5.8, 14.2.21, and 15.1.2. We recommend that users upgrade to a safe version. There are no official workarounds.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-56332 https://cve.radiocsirt.org/vuln/ghsa-7m27-7ghc-44w9 <p><strong>Affected:</strong> npm: next</p> <p>### Impact A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.</p> <p>_Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time._</p> <p>Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing.</p> <p>This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel.</p> <p>This vulnerability affects only Next.js deployments using Server Actions.</p> <p>### Patches</p> <p>This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.</p> <p>### Workarounds</p> <p>There are no official workarounds for this vulnerability.</p> <p>### Credits</p> <p>Thanks to the PackDraw team for responsibly disclosing this vulnerability.</p> <p><strong>Affected:</strong> npm: next</p> <p>### Impact A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.</p> <p>_Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time._</p> <p>Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing.</p> <p>This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel.</p> <p>This vulnerability affects only Next.js deployments using Server Actions.</p> <p>### Patches</p> <p>This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.</p> <p>### Workarounds</p> <p>There are no official workarounds for this vulnerability.</p> <p>### Credits</p> <p>Thanks to the PackDraw team for responsibly disclosing this vulnerability.</p> https://cve.radiocsirt.org/vuln/ghsa-7m27-7ghc-44w9 https://cve.radiocsirt.org/vuln/rhsa-2025:3807 <p>next.js: next: authorization bypass in Next.js next.js: Next.js Vulnerable to Denial of Service (DoS) with Server Actions</p> <p>next.js: next: authorization bypass in Next.js next.js: Next.js Vulnerable to Denial of Service (DoS) with Server Actions</p> https://cve.radiocsirt.org/vuln/rhsa-2025:3807