Skip to content

Commit 25e968b

Browse files
joyeecheungCopilot
andauthored
Update apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Co-authored-by: Copilot <[email protected]> Signed-off-by: Joyee Cheung <[email protected]>
1 parent eca69b4 commit 25e968b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ It's worth noting that even when ECMAScript specifies that [proper tail calls](h
195195

196196
### This Behavior Is Not Part of The Security Guarantees of V8
197197

198-
In Node.js, the stack space usage from JavaScript function calls is primarily implemented by V8. JavaScript engines developed for browsers have a different security model, and they do not triage crashes like this as security vulnerabilities This means similar behavior inconsistencies reported in the upstream (like [this](https://issues.chromium.org/issues/432385241)) are not guaranteed to go through vulnerability disclosure procedures, making any security classification by Node.js alone ineffective.
198+
In Node.js, the stack space usage from JavaScript function calls is primarily implemented by V8. JavaScript engines developed for browsers have a different security model, and they do not triage crashes like this as security vulnerabilities. This means similar behavior inconsistencies reported in the upstream (like [this](https://issues.chromium.org/issues/432385241)) are not guaranteed to go through vulnerability disclosure procedures, making any security classification by Node.js alone ineffective.
199199

200200
### uncaughtException Limitations
201201

0 commit comments

Comments
 (0)