Incorrect Control Flow Scoping

Every one of the 5 is a mark on the map. Named now: 1 to 5, most at risk first.

1. OpenSynergy BlueSDK (aka Blue SDK) through 6.x has Incorrect Control Flow Scoping. The specific flaw exists within the BlueSDK Bluetooth stack. The issue results from the lack of…CVE-2024-45433Opensynergy · CVSS 6.5 · 0.5% likely
2. baseline-browser-mapping 2.x before 2.11.0 calls process.exit() instead of throwing on invalid or conflicting input parameters, and can trigger immediate process termination, caus…CVE-2026-45819web-platform-dx · CVSS 6.6 · 0.5% likely
3. Denial of service via DoH3 queriesCVE-2026-40208PowerDNS · CVSS 3.7 · 0.4% likely

   PowerDNS

4. TMM vulnerabilityCVE-2025-53856F5 · CVSS 7.5 · 0.3% likely

   F5

5. 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 i…CVE-2026-3449@tootallnate/once · CVSS 3.3 · 0.1% likely

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.