---
title: "GHSA-vpq2-c234-7xj6: @tootallnate/once vulnerable to Incorrect Control Flow Scoping"
description: "Low severity. @tootallnate/once vulnerable to Incorrect Control Flow Scoping. Affects @tootallnate/once; fixed in 3.0.1."
url: https://inlinr.com/advisories/GHSA-vpq2-c234-7xj6
lang: en
---

[Packages](https://inlinr.com/packages) / [@tootallnate/once](https://inlinr.com/packages/@tootallnate/once) / [Security](https://inlinr.com/packages/@tootallnate/once/security)

Low Vulnerability GHSA-vpq2-c234-7xj6 CVE-2026-3449 Published 3 Mar 2026

# @tootallnate/once vulnerable to Incorrect Control Flow Scoping

Your version 

Affected releases · [@tootallnate/once](https://inlinr.com/packages/@tootallnate/once)

- 3.x 3.0.0 Fixed in 3.0.1
- 2.x 2.0.0 Fixed in 2.0.1
- 1.x 1.0.0 – 1.1.2 No fix on this line yet

On 3.x, the newest line:

```
npm install @tootallnate/once@3.0.1
```

Every release on a timeline

3.x 

1. Affected

3.0.0  
1 release
2. Fixed

3.0.1  
1 release, latest

2.x 

1. Affected

2.0.0  
1 release
2. Fixed

2.0.1  
1 release

1.x 

1. Affected

1.0.0 – 1.1.2  
4 releases

8 stable releases of @tootallnate/once, oldest to newest, one row per major.

## What happens

Versions 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.

## How it is exploited

Exploitable with local access, with a low-privilege account and no action from a user.

- **Confidentiality**: none
- **Integrity**: none
- **Availability**: low

CVSS:3.1/​AV:L/​AC:L/​PR:L/​UI:N/​S:U/​C:N/​I:N/​A:L

## References

- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-3449 "https://nvd.nist.gov/vuln/detail/CVE-2026-3449")  
nvd.nist.gov/vuln/detail/CVE-2026-3449
- [Issue](https://github.com/TooTallNate/once/issues/8 "https://github.com/TooTallNate/once/issues/8")  
#8
- [Fix commit](https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a "https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a")  
b9f43cc
- [Package](https://github.com/TooTallNate/once "https://github.com/TooTallNate/once")  
github.com/TooTallNate/once
- [Reference](https://github.com/TooTallNate/once/releases/tag/v2.0.1 "https://github.com/TooTallNate/once/releases/tag/v2.0.1")  
github.com/TooTallNate/once/releases/tag/v2.0.1
- [Reference](https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612 "https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612")  
security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-1…

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
