Vulnerability in @tootallnate/once (CVE-2026-3449)
Summary
Vulnerability in @tootallnate/once (CVE-2026-3449). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.0.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3449 has been found in @tootallnate/once.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade @tootallnate/once to 2.0.1 or later.
If unsure, ask your IT team or search "@tootallnate/once CVE-2026-3449" on the vendor's site.
CVE-2026-3449 (@tootallnate/once) — CWE-705 / CVSS v3 3.3
Attack vector: local / no user interaction
Patched: 2.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-705) exists in @tootallnate/once.
Check the vendor advisory for the affected versions of @tootallnate/once.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@tootallnate/once' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@tootallnate/once' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@tootallnate/onceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @tootallnate/once to 2.0.1ステージング環境で 2.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web security.snyk.io
- web github.com
- web github.com