How severe is CVE-2026-3449?

CVE-2026-3449 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.

Is CVE-2026-3449 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-3449?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-3449 have an EU (EUVD) identifier?

Yes. CVE-2026-3449 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9278.

When was CVE-2026-3449 published?

CVE-2026-3449 was published on 2026-03-03 and last updated on 2026-06-17.

CVE-2026-3449

CVE-2026-3449 is a low-severity vulnerability with a CVSS 3.x base score of 3.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-705.

Key facts

Severity: Low (CVSS 3.x base score 3.3)
CVSS v4: 1.9
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-9278
Weakness: CWE-705
Published: 2026-03-03
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-3449?: 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 severe is CVE-2026-3449?: CVE-2026-3449 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2026-3449 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-3449?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-3449 have an EU (EUVD) identifier?: Yes. CVE-2026-3449 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9278.
When was CVE-2026-3449 published?: CVE-2026-3449 was published on 2026-03-03 and last updated on 2026-06-17.

References

Other CWE-705 vulnerabilities

CVE-2025-53856 — High (CVSS 7.5): When a virtual server, network address translation (NAT) object, or secure network address translation (SNAT) object…
CVE-2024-45433 — Medium (CVSS 6.5): OpenSynergy BlueSDK (aka Blue SDK) through 6.x has Incorrect Control Flow Scoping. The specific flaw exists within the…
CVE-2026-40208 — Low (CVSS 3.7): An attacker might be able to delay the processing of DoH3 queries by sending DoH3 GET queries with an invalid DATA…

Browse all CWE-705 vulnerabilities →