CWEweakness
CWE-1119 Excessive Use of Unconditional Branching
- Alternate terms
- Spaghetti code
- Abstraction
- Base
- Structure
- Simple
- Status
- Incomplete
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
The code uses too many unconditional branches (such as "goto").
Common consequences
• Other: Reduce Maintainability, Increase Analytical Complexity — This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.
Detection methods
• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Related
Child of · CWE (1)
- CWE-1120 Excessive Code Complexity weakness
Referenced by CVE · weakness (2)
- CVE-2026-56847 A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. vulnerability
- CVE-2026-21500 iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of ICC color management profiles. vulnerability