@tootallnate/once · Vulnerability
cve-program · CVE-2026-3449
PublishedVersions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.
Read the publisher's advisoryeuvd · EUVD-2026-9278
PublishedVersions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.
Read the publisher's advisorynvd · CVE-2026-3449
PublishedVersions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.
Read the publisher's advisoryosv · GHSA-vpq2-c234-7xj6
PublishedVersions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-3449 · CVE overview and exploitation status
cve-program · CVE-2026-3449
- https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612
- https://github.com/TooTallNate/once/issues/8
- https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a
euvd · EUVD-2026-9278
- https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612
- https://github.com/TooTallNate/once/issues/8
- https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a
nvd · CVE-2026-3449
- https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a
- https://github.com/TooTallNate/once/issues/8
- https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612
osv · GHSA-vpq2-c234-7xj6
- https://nvd.nist.gov/vuln/detail/CVE-2026-3449
- https://github.com/TooTallNate/once/issues/8
- https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a
- https://github.com/TooTallNate/once
- https://github.com/TooTallNate/once/releases/tag/v2.0.1
- https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612