Application task hangs via unsettled aborted Promises
Published Mar 3, 2026 · Updated Mar 3, 2026
Incorrect control-flow scoping in @tootallnate/once before 2.0.1 and 3.0.0 allows local users to hang application tasks. Within once(), the abort listener calls cleanup(), which removes event listeners but neither resolves nor rejects the returned Promise. Reachability requires an application path that supplies AbortSignal to once(); aborting it can stall requests or block workers without disclosing or altering data.
Summary
What happened
Incorrect control-flow scoping in @tootallnate/once before 2.0.1 and 3.0.0 allows local users to hang application tasks. Within once(), the abort listener calls cleanup(), which removes event listeners but neither resolves nor rejects the returned Promise. Reachability requires an application path that supplies AbortSignal to once(); aborting it can stall requests or block workers without disclosing or altering data.
The record
- CVE
- CVE-2026-3449
- Published
- Mar 3, 2026
- Updated
- Mar 3, 2026
- Vendor
- TooTallNate
- Product
- @tootallnate/once
- Classifications
- CWE-705
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2026CVE publishedPublication date reported by the CVE source.
- Mar 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- AbortSignal Promise hang proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo