CVE-2026-3449: @tootallnate/once vulnerability
Vendor not named in the CVE record · @tootallnate/once
Fixed in 3.0.1 · Affected: @tootallnate/once before 3.0.1 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 2% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- @tootallnate/oncebefore 3.0.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- March 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-3449 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.