{“lastseen”:”2026-01-14T07:13:00″,”description”:”\\n\\nNode.js has released updates to fix what it described as a critical security issue impacting \\”virtually every production Node.js app\\” that, if successfully exploited, could trigger a denial-of-service (DoS) condition.\\n\\n\\”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,\\” Node.js’s Matteo Collina and Joyee Cheung said in a Tuesday bulletin.\\n\\n\\”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.\\”\\n\\nAt its core, the shortcoming stems from the fact that Node.js exits with code 7 (denoting an Internal Exception Handler Run-Time Failure) instead of gracefully handling the exception when a stack overflow occurs in user code while async_hooks is enabled. Async_hooks is a low-level Node.js API that allows developers to track the lifecycle of asynchronous resources, such as database queries, timers, or HTTP requests.\\n\\n\\n\\nThe issue, Node.js said, impacts several frameworks and Application Performance Monitoring (APM) tools, including React Server Components, Next.js, Datadog, New Relic, Dynatrace, Elastic APM, and OpenTelemetry, owing to the use of AsyncLocalStorage, a component built atop the async_hooks module that makes it possible to store data throughout the lifetime of an asynchronous operation.\\n\\nIt has been addressed in the following versions -\\n\\n * Node.js 20.20.0 (LTS)\\n * Node.js 22.22.0 (LTS)\\n * Node.js 24.13.0 (LTS)\\n * Node.js 25.3.0 (Current)\\n\\n\\n\\nThe problem also impacts all Node.js versions from 8.x, which was the first version with async_hooks, to 18.x. It’s worth noting that Node.js version 8.0.0, codenamed Carbon, was released on May 30, 2017. However, these versions are unpatched as they have reached end-of-life (EoL) status.\\n\\nThe fix put in place detects stack overflow errors and re-throws them to user code instead of treating them as fatal. This is being tracked under the CVE identifier **CVE-2025-59466** (CVSS score: 7.5). Despite the significant practical impact, Node.js said it’s treating the fix as only a mitigation owing to a couple of reasons -\\n\\n * Stack space exhaustion is not part of the ECMAScript specification\\n * The V8 JavaScript engine does not treat it as a security issue\\n * Limitations with the \\”uncaughtException\\” handler, which is designed to be used as a last resort mechanism for exception handling\\n\\n\\n\\n\\n\\n\\”Although it is a bug fix for an unspecified behavior, we chose to include it in the security release because of its widespread impact on the ecosystem,\\” Node.js said. \\”React Server Components, Next.js, and virtually every APM tool are affected. The fix improves developer experience and makes error handling more predictable.\\”\\n\\nIn light of the severity of the vulnerability, users of the frameworks\/tools and server hosting providers are recommended to update as soon as possible. Maintainers of libraries and frameworks are being recommended to apply more robust defenses to counter stack space exhaustion and ensure service availability.\\n\\nThe disclosure comes as Node.js also released fixes for three other high-severity flaws (CVE-2025-55131, CVE-2025-55130, and CVE-2025-59465) that could be exploited to achieve data leakage or corruption, read sensitive files using crafted relative symbolic link (symlink) paths, and trigger a remote denial-of-service, respectively.\\n\\nFound this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.\\n”,”published”:”2026-01-14T07:05:00″,”modified”:”2026-01-14T07:05:17″,”type”:”thn”,”title”:”Critical Node.js Vulnerability Can Cause Server Crashes via async_hooks Stack Overflow”,”source”:””,”references”:””,”id”:”THN:75919F10A55C043DEECC4739CB32C7CD”,”bulletinFamily”:”info”,”cwe”:null,”cvelist”:[“CVE-2025-55130″,”CVE-2025-55131″,”CVE-2025-59465″,”CVE-2025-59466″],”sourceData”:””,”sourceHref”:””,”cvss”:{“score”:0,”severity”:”NONE”,”vector”:”NONE”,”version”:”NONE”},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:”https:\/\/thehackernews.com\/2026\/01\/critical-nodejs-vulnerability-can-cause.html”,”category_name”:”News”,”post_link”:””,”product”:””,”version”:””,”vendor”:””,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:”2026-01-14T07:13:00″,”description”:”\\n\\nNode.js has released updates to fix what it described as a critical security issue impacting \\”virtually every production Node.js app\\” that, if successfully…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,8,12,13,33,7,11,43,5],"class_list":["post-35619","post","type-post","status-publish","format-standard","hentry","category-category_news","tag-cve","tag-cvss","tag-exploit","tag-news","tag-none","tag-security","tag-tapic","tag-thn","tag-vulnerability"],"yoast_head":"\n