-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
blog: add DoS mitigation post for async_hooks stack exhaustion #8542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/nodejs-website Please review the changes when you have a chance. Thank you! 🙏 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8542 +/- ##
==========================================
+ Coverage 75.00% 75.01% +0.01%
==========================================
Files 103 103
Lines 9036 9036
Branches 311 311
==========================================
+ Hits 6777 6778 +1
+ Misses 2257 2256 -1
Partials 2 2 ☔ View full report in Codecov by Sentry. |
📦 Build Size ComparisonSummary
Changes➕ Added Assets (1)
➖ Removed Assets (1)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds a comprehensive blog post documenting a critical DoS vulnerability affecting Node.js applications that use async_hooks, including React Server Components, Next.js, and all major APM tools. The vulnerability caused stack overflow errors to become uncatchable when async_hooks was enabled, leading to immediate process crashes with exit code 7.
Changes:
- Added detailed vulnerability disclosure blog post explaining the async_hooks stack exhaustion issue
- Documents the fix included in Node.js 20.20.0, 22.22.0, 24.13.0, and 25.3.0
- Provides technical deep dive, code examples, timeline, and mitigation guidance
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
|
I have some leftover suggestions from the original draft, I'll duplicate them here.. |
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
|
the |
Add blog post explaining the vulnerability where stack overflow errors became uncatchable when async_hooks was enabled, affecting React Server Components, Next.js, and APM tools. Co-Authored-By: Joyee Cheung <[email protected]>
0d18259 to
e095ef6
Compare
9579861 to
9b46208
Compare
9b46208 to
6c101fd
Compare
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
6c101fd to
66b49c1
Compare
66b49c1 to
80db087
Compare
|
@joyeecheung ping |
Summary
async_hookswas enabledTest plan