The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.

What CVEs are caused by CWE-480?

5 recorded CVEs are attributed to CWE-480, including CVE-2026-15043, CVE-2026-43114, CVE-2026-48497.

How is CWE-480 detected?

Automated Static Analysis: This weakness can be found easily using static analysis. However in some cases an operator might appear to be incorrect, but is actually correct and reflects unusual logic within the program.

What are the consequences of CWE-480?

Exploiting CWE-480 can lead to: Alter Execution Logic.

Is CWE-480 actively exploited?

5 recorded CVEs are caused by CWE-480; none are currently in CISA's KEV catalog of actively exploited flaws.

CWE-480: Use of Incorrect Operator

RadicalNotion.AI

Code examples

Illustrative examples from MITRE showing how the weakness appears in code.

The following C/C++ and C# examples attempt to validate an int input parameter against the integer value 100.

Vulnerable example

int isValid(int value) {

Vulnerable example

csharp

bool isValid(int value) {

However, the expression to be evaluated in the if statement uses the assignment operator "=" rather than the comparison operator "==". The result of using the assignment operator instead of the comparison operator causes the int variable to be reassigned locally and the expression in the if statement will always evaluate to the value on the right hand side of the expression. This will result in the input value not being properly validated, which can cause unexpected results.

The following C/C++ example shows a simple implementation of a stack that includes methods for adding and removing integer values from the stack. The example uses pointers to add and remove integer values to the stack array variable.

Vulnerable example

#define SIZE 50

The example code below is taken from the CVA6 processor core of the HACK@DAC'21 buggy OpenPiton SoC. Debug access allows users to access internal hardware registers that are otherwise not exposed for user access or restricted access through access control protocols. Hence, requests to enter debug mode are checked and authorized only if the processor has sufficient privileges. In addition, debug accesses are also locked behind password checkers. Thus, the processor enters debug mode only when the privilege level requirement is met, and the correct debug password is provided.

CWE-480: Use of Incorrect Operator

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Applies to

How to detect it

Automated Static Analysis

Manual Static Analysis

Code examples

Illustrative examples

Terminology & mappings

Mapped taxonomies

Frequently asked questions

References

Stay ahead of CWE-480

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Applies to

How to detect it

Automated Static Analysis

Manual Static Analysis

Code examples

Illustrative examples

Related weaknesses

Parent

Child

Terminology & mappings

Mapped taxonomies

Frequently asked questions

References

Stay ahead of CWE-480