CWE-190: Integer Overflow or Wraparound
Sources read 2026-10-29. MITRE's own page · All weakness notes · Added to CISA's list in the last seven days
What it is
From MITRE's CWE catalogue
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
MITRE classes it as a base-level weakness and rates the likelihood of exploit as medium.
What it lets an attacker do
From MITRE's CWE catalogue
- DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Memory), DoS: Instability (affects: availability)
- Modify Memory (affects: integrity)
- Execute Unauthorized Code or Commands, Bypass Protection Mechanism (affects: confidentiality, availability, access control)
- Alter Execution Logic, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU) (affects: availability, other)
On CISA's exploited list
From CISA's exploited list
1 of the 108 entries CISA added from 2026-08-02 to 2026-10-30 name CWE-190, against 1 of 69 in the 90 days before. Over the whole catalogue 17 entries name it. The counts are small, so read them as a rough order, not a rate.
CISA's list is not every flaw that is exploited: it holds the ones CISA has evidence of, listed on the day it added them.
- CVE-2026-97229, GitLab Community Edition and Enterprise Edition, added 2026-10-29
- CVE-2025-48595, Android Framework, added 2026-06-02
- CVE-2021-30952, Apple Multiple Products, added 2026-03-05
- CVE-2026-21385, Qualcomm Multiple Chipsets, added 2026-03-03
- CVE-2018-14634, Linux Kernel, added 2026-01-26
How MITRE says to find it
From MITRE's CWE catalogue
- Automated Static Analysis
- Black Box
- Manual Analysis
- Automated Static Analysis - Binary or Bytecode
- Dynamic Analysis with Manual Results Interpretation
What MITRE suggests
From MITRE's CWE catalogue
- Requirements: Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
- Implementation: Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range. Use unsigned integers where possible. This makes it easier to perform validation for integer overflows.
Attack patterns MITRE links to it
From MITRE's CWE catalogue
Start with one piece of work.
Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.
Talk to us