CWE · MITRE source

CWE-480Use of Incorrect Operator

Abstraction: Base · CVEs in our corpus: 10

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

These types of errors are generally the result of a typo by the programmer.

Last updated: 15 October 2026 07:26 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent

Stop it (NIST 800-53 / CSF Protect)

PR.PS-06
SA-11 Developer Testing and Evaluation

Detect

Catch it (CSF Detect / Respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control	Title	Family	Why it addresses this CWE
No NIST controls proposed yet.

Top CVEs of this weakness type, ranked by Risk Priority

CVE	Risk	CVSS	EPSS	Published
`CVE-2026-15043`	7.3	9.8	0.0039	2026-07-14
`CVE-2026-43114`	7.0	9.4	0.0037	2026-05-06
`CVE-2026-63421`	5.9	7.5	0.0067	2026-08-21
`CVE-2026-4748`	5.8	7.5	0.0042	2026-04-01
`CVE-2026-79643`	5.6	7.3	0.0033	2026-09-07
`CVE-2022-1947`	5.3	6.5	0.0124	2022-05-31
`CVE-2026-48497`	4.7	5.9	0.0040	2026-06-26
`CVE-2024-35190`	4.6	5.8	0.0056	2024-05-17
`CVE-2026-44722`	4.6	6.2	0.0012	2026-07-17
`CVE-2025-52985`	4.4	5.3	0.0030	2025-07-11