CWE-190: Integer Overflow or Wraparound

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.

Consequences

• Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Memory), DoS: Instability
• Integrity: Modify Memory
• Confidentiality, Availability, Access Control: Execute Unauthorized Code or Commands, Bypass Protection Mechanism
• Availability, Other: Alter Execution Logic, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU)
• Access Control: Bypass Protection Mechanism

How to prevent it

• 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. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
• 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. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
• Implementation: Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7] Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.
• Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
• Implementation: Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.

Recent advisories

• GHSA-4642-5mcj-2rqw — Forge: ASN.1 OID first arc truncation in asn1.oidToDer
• GHSA-4rm8-3hmm-39fg — Pillow: Reachable undefined behavior in native integer operations, potentially leading to denial of service or logic integrity compromise
• GHSA-f63g-mx39-3r38 — Microsoft Security Advisory CVE-2026-85363 - .NET and Visual Studio Remote Code Execution Vulnerability
• CVE-2026-97229 — Integer Overflow or Wraparound in GitLab
• RUSTSEC-2026-0314 — Guest can panic host through filesystem datetime overflow
• GHSA-p6m2-r3w9-mpxw — rclone local: crafted Range request against a translated symlink panics (DoS)
• EEF-CVE-2026-82737 — Ash.Vector wraps the 16-bit dimension header for vectors over 65,535 elements, corrupting data and crashing reads
• GHSA-mrpp-v6pg-p54x — klever-go: SFT add-quantity `int64` overflow bypasses a finite per-nonce MaxSupply
• GHSA-cgc5-v3f2-8m2v — Klever: Integer overflow in split-royalty validation enables unbounded minting of KLV (native token)
• GHSA-7m6h-x95x-82q5 — vLLM: Cross-User Data Leak Vulnerability
• GHSA-xwg4-73v4-xw9w — nanoid: Integer Overflow or Wraparound
• GHSA-fx4q-gjrx-2jw6 — Microsoft Security Advisory CVE-2026-62897 – .NET Remote Code Execution Vulnerability
• GHSA-jqhp-238x-qhgf — Microsoft Security Advisory CVE-2026-62886 – .NET Elevation of Privilege Vulnerability
• GHSA-h22j-f9xw-xjjm — ImageMagick: Integer Overflow in JNX decoder causes heap buffer over-write when processing extremly large files on 32-bit builds
• GHSA-f5m7-cqgw-8hm7 — ImageMagick: Heap Buffer Over-Write in morphology operation when an invalid kernel is provided

All advisories for CWE-190