From cd841813a268f0154c3503c38425802f29625c30 Mon Sep 17 00:00:00 2001 From: Malav Shah Date: Tue, 13 Jan 2026 17:51:17 -0700 Subject: [PATCH] fix(blog): remove duplicate blog title for jan 2026 --- .../vulnerability/january-2026-dos-mitigation-async-hooks.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md b/apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md index c6457f4790c38..7bdb14d4b85f6 100644 --- a/apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md +++ b/apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md @@ -7,8 +7,6 @@ layout: blog-post author: Matteo Collina and Joyee Cheung --- -# Mitigating Denial-of-Service Vulnerability from Unrecoverable Stack Space Exhaustion for React, Next.js, and APM Users - ## TL;DR Node.js/V8 makes a best-effort attempt to recover from stack space exhaustion with a catchable error, which frameworks have come to rely on for service availability. A bug that only reproduces when `async_hooks` are used would break this attempt, causing Node.js to exit with 7 directly without throwing a catchable error when recursions in user code exhaust the stack space. This makes applications whose recursion depth is controlled by unsanitized input vulnerable to Denial-of-Service attacks. This silently affects countless applications because: