ClassDraft

CWE-670Always-Incorrect Control Flow Implementation

Category: other

Description

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. This weakness captures cases in which a particular code segment is always incorrect with respect to the algorithm that it is implementing. For example, if a C programmer intends to include multiple statements in a single block but does not include the enclosing braces (CWE-483), then the logic is always incorrect. This issue is in contrast to most weaknesses in which the code usually behaves correctly, except when it is externally manipulated in malicious ways.

Common consequences· 1

  • Other — Other, Alter Execution Logic

References

  1. https://cwe.mitre.org/data/definitions/670.html

(incoming)6

TypeTargetConfidenceTier
VulnerabilityCVE-2025-29312cve-2025-293120%live
VulnerabilityCVE-2025-43359cve-2025-433590%live
VulnerabilityCVE-2025-49091cve-2025-490910%live
VulnerabilityCVE-2026-35414cve-2026-354140%live
VulnerabilityCVE-2026-40200cve-2026-402000%live
VulnerabilityCVE-2026-40960cve-2026-409600%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Incorrect Block Delimitation
CWE
Insufficient Control Flow Management
CWE
Missing Default Case in Multiple Condition Expression
CWE
Excessive Use of Unconditional Branching
CWE
Use of Uninitialized Variable
CWE
Unchecked Error Condition
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.