CyberSecBulletin

Integer Overflow or Wraparound

CWE-190

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.

We track 963 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.2. 22 have been exploited in real attacks.

How this weakness is prevented

  • 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. 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++).
  • 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. Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

Latest Integer Overflow or Wraparound vulnerabilities

  • 7.8 High severity

    GeForce: Integer Overflow or Wraparound

    CVE-2026-47502NVIDIA

    NVIDIA vGPU Virtual GPU Manager for Windows and Linux contains a vulnerability in the kernel mode layer, where a guest user could cause an integer overflow leading to memory corruption. A successful exploit of this vulnerability might lead to code execution, d

  • 7.5 High severity

    Apache WSS4J: Integer Overflow or Wraparound

    CVE-2026-95616Apache

    An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation. An unauthenticated attacker can send a SOAP message carrying an X.509 certificate whose SubjectKeyIdentifier extension declares a length of 0x7FFFFFFF; WSS4J decodes

  • 8.7 High severity

    Apache PLC4X: Improper Validation of Array Index

    CVE-2026-102510Apache

    Integer Overflow, Improper Validation of Array Index, Uncontrolled Recursion and Memory Allocation with Excessive Size Value in the Go implementation of Apache PLC4X (PLC4Go) allow a malicious device, or an attacker able to inject network traffic, to crash or

  • 7.8 High severity

    DeepStream: Integer Overflow or Wraparound

    CVE-2026-65102NVIDIA

    NVIDIA DeepStream contains a vulnerability where an attacker could cause an integer overflow by supplying crafted tensor dimensions in a YAML configuration file. A successful exploit of this vulnerability might lead to denial of service, information disclosure

  • 7.5 High severity

    compress: Integer Overflow or Wraparound

    CVE-2026-63209Klauspost

    compress provides various compression algorithms. Prior to version 1.18.7, a signed integer overflow vulnerability in s2.NewDict() allows an attacker to bypass repeat index validation by supplying a dictionary with a uvarint-encoded repeat value exceeding MaxI

  • 7.5 High severity

    Lerc: Integer Overflow or Wraparound

    CVE-2026-10758Esri

    Esri LERC is an open-source image or raster format which supports rapid encoding and decoding for any pixel type. A Heap based Out-of-Bounds Write via Integer Overflow in LERC versions 4.1.0 and earlier may allow a remote, unauthenticated attacker who can pass

  • 8.4 High severity

    Python Driver: Integer Overflow or Wraparound

    CVE-2026-96749MongoDB

    An integer overflow in the BSON document encoding component of the MongoDB Python Driver's bundled native extension may occur when a single document is built from an unusually large amount of caller-supplied data. Size arithmetic is performed in a signed 32-bi

  • 9.9 Critical severity

    GitLab: Integer Overflow or Wraparound

    CVE-2026-93577GitLab

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due

  • 7.5 High severity

    PgBouncer: Integer Overflow or Wraparound

    CVE-2026-6668PgBouncer

    Integer overflow in the packet buffer growth logic in PgBouncer through 1.25.2 allows an unauthenticated remote attacker to cause a denial of service. Sufficiently large input makes the buffer size computation overflow, leaving the growth loop unable to termin

  • 7.8 High severity

    FFmpeg: Integer Overflow or Wraparound

    CVE-2026-96611FFmpeg

    FFmpeg before 9.0 has a signed integer overflow in libavformat/mov.c. In mov_read_ispe(), uint32_t width/height values from a crafted HEIF ispe box are stored into signed int fields without bounds checking, allowing values exceeding INT_MAX to become negative.

  • 7.3 High severity

    Connext Professional: Integer Overflow or Wraparound

    CVE-2026-18462RTI

    Integer Overflow or Wraparound, Improper Access Control vulnerability in RTI Connext Professional (Core Libraries) allows Shared Resource Manipulation. This issue affects Connext Professional: from 7.4.0 before 7.7.0.1, from 7.0.0 before 7.3.1.6, from 6.1.0 be

  • 7.7 High severity

    Red Hat Enterprise Linux 8: Integer Overflow or Wraparound

    CVE-2026-95619Red Hat

    A flaw was found in libstdc++. An integer overflow can occur when processing large inputs to the aligned operator new in the C++ library. This vulnerability could lead to an undersized memory allocation, potentially causing memory corruption or application ins

  • 8.8 High severity

    MQ: Integer Overflow or Wraparound

    CVE-2026-11725IBM

    IBM MQ could allow an authenticated attacker to cause a denial of service or potentially execute arbitrary code due to an integer overflow in MQINQ request processing.

  • 7.8 High severity

    kvm-guest-drivers-windows: Heap-based Buffer Overflow

    CVE-2026-46655Virtio-win

    virtio-win provides Windows paravirtualized drivers for QEMU and KVM. From mm210 until mm320, the Viosock driver permits a low-privilege local process to submit an IOCTL_SELECT request with attacker-controlled VIRTIO_VSOCK_SELECT.Fdss[*].fd_count values that o

  • 8.8 High severity

    MQ: Integer Overflow or Wraparound

    CVE-2026-11378IBM

    IBM MQ could allow an authenticated attacker to cause a denial of service or potentially execute arbitrary code due to an integer overflow in distribution list processing.

  • 8.7 High severity

    ESPAsyncWebServer: Integer Overflow or Wraparound

    CVE-2026-54571ESP32Async

    ESPAsyncWebServer is an asynchronous HTTP and WebSocket server library for ESP32, ESP8266, RP2040 and RP2350. Prior to 3.11.1, the multipart/form-data parser in src/WebRequest.cpp stores _boundaryPosition as an 8-bit value while _parseMultipartPostByte process

  • 7.5 High severity

    wire: Integer Overflow or Wraparound

    CVE-2026-63126Square

    Wire provides gRPC and protocol buffers for Android, Kotlin, Swift, and Java. Prior to 6.4.5 and 7.0.0-alpha04, Wire protobuf readers do not consistently validate attacker-controlled lengths against the current logical message boundary before advancing cursors

  • 9.1 Critical severity

    amqp091-go: Integer Overflow or Wraparound

    CVE-2026-77408Rabbitmq

    RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, the writeShortstr function in write.go casts the byte length of AMQP shortstr property values to uint8 without first rejecting values longer than 255 bytes. An application that accepts an oversize

  • 7.8 High severity

    GIMP: Integer Overflow or Wraparound

    CVE-2026-92248GNOME

    A flaw was found in the file-psd plugin in GIMP. When generating a thumbnail preview for a specially crafted PSD (Photoshop Document) image file, an integer overflow occurs during the multiplication of values from an embedded JPEG header. This leads to an unde

  • 9.6 Critical severity

    Chrome: Integer Overflow or Wraparound

    CVE-2026-91728Google

    Integer overflow in V8 in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

  • 8.1 High severity

    EdgeConnect SD-WAN Gateways: Integer Overflow or Wraparound

    CVE-2026-76685Hewlett Packard Enterprise

    A vulnerability exists in the proxy packet processing logic of the affected component where it improperly processes malformed or truncated input. An unauthenticated remote attacker could exploit this vulnerability by providing specially crafted input that trig

  • 7.8 High severity

    Android: Integer Overflow or Wraparound

    CVE-2026-55351Google

    In VPU, there is a possible out-of-bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Integer Overflow or Wraparound

    CVE-2026-0194Google

    In multiple locations, there is a possible permission bypass due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 7.3 High severity

    iOS and iPadOS: Integer Overflow or Wraparound

    CVE-2026-84620Apple

    An integer overflow was addressed with improved input validation. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27, watchOS 27. Processing a maliciously craf

  • 7.1 High severity

    macOS: Integer Overflow or Wraparound

    CVE-2026-84548Apple

    An integer overflow was addressed with improved input validation. This issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7. Processing a maliciously crafted document may lead to an out-of-bounds read.

  • 7.5 High severity

    macOS: Integer Overflow or Wraparound

    CVE-2026-84544Apple

    An integer overflow was addressed with improved input validation. This issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7. Connecting to a malicious NFS server may cause unexpected system termination or corrupt kernel memory.

  • 8.8 High severity

    Safari: Integer Overflow or Wraparound

    CVE-2026-65391Apple

    An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in Safari 26.6.1, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, watchOS 27. Processing maliciously crafted web content may lead to memory co

  • 8.8 High severity

    Safari: Integer Overflow or Wraparound

    CVE-2026-65390Apple

    An integer overflow was addressed with improved input validation. This issue is fixed in Safari 26.6.1, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, watchOS 27. Processing maliciously crafted web content may lead to memory corruption

  • 7.3 High severity

    A security vulnerability has been detected in marcobambini Gravity up to 0.9.7.

    CVE-2026-90715Marcobambini

    A security vulnerability has been detected in marcobambini Gravity up to 0.9.7. This affects an unknown function of the file src/utils/gravity_json.c of the component udp json-parser. Such manipulation leads to integer overflow. The attack may be performed fro

  • 7.3 High severity

    A vulnerability was determined in embedded-graphics up to 0.8.2.

    CVE-2026-90593Embedded-graphics

    A vulnerability was determined in embedded-graphics up to 0.8.2. This affects the function ImageRaw::draw_sub_image of the file src/image/image_raw.rs. Executing a manipulation of the argument width can lead to integer overflow. The attack may be launched remo

  • 7.4 High severity

    libde265: Heap-based Buffer Overflow

    CVE-2026-54241Strukturag

    libde265 is an open source implementation of the h.265 video codec. Versions prior to 1.1.1 use signed 32-bit arithmetic to calculate the sample adaptive offset input-buffer size, allowing a crafted HEVC stream with large dimensions and 16-bit luma samples to

  • 7.4 High severity

    libde265: Integer Overflow or Wraparound

    CVE-2026-54240Strukturag

    libde265 is an open source implementation of the h.265 video codec. Versions prior to 1.1.1 use signed 32-bit arithmetic to calculate pixel offsets, allowing a crafted HEVC stream with large image dimensions to trigger an integer overflow and cause out-of-boun

  • 8.1 High severity

    DICOM Server: Integer Overflow or Wraparound

    CVE-2026-87020Orthanc

    An integer overflow in a specified pitch and buffer-size computation leads to a heap out-of-bounds write when Orthanc DICOM Server decodes an attacker-supplied PNG.

  • 7.5 High severity

    libp2p-rendezvous: Integer Overflow or Wraparound

    CVE-2026-89146Libp2p

    libp2p-rendezvous through 0.17.1 fails to validate registration TTL values in discovery responses, allowing attackers to trigger timer arithmetic overflow. A malicious rendezvous server can send a discovery response with an unbounded TTL value that causes the

  • 8.7 High severity

    Endpoint DLP: Integer Overflow or Wraparound

    CVE-2026-16174Netskope

    Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer over

  • 9.1 Critical severity

    Deep Java Library: Integer Overflow or Wraparound

    CVE-2026-85228Amazon

    An integer overflow in the tensor buffer validation component in Amazon Deep Java Library (DJL) from 0.13.0 through 0.36.0 on all platforms might allow a remote unauthenticated actor to obtain information from adjacent process memory or cause a denial of servi

  • 8.2 High severity

    zstd-jni: Integer Overflow or Wraparound

    CVE-2026-87823Luben

    zstd-jni before 1.5.7-14 performs 32-bit signed bounds checks on three direct-ByteBuffer frame-size native methods, allowing out-of-bounds memory reads via negative or overflowing offsets. Attackers can supply negative offset values near Integer.MIN_VALUE to r

  • 7.0 High severity

    VLC media player: Integer Overflow or Wraparound

    CVE-2026-56711VideoLAN

    VLC media player versions 3.0.0 through 3.0.23 contain a memory-safety vulnerability reachable when processing crafted media. Exploitation requires user interaction and may result in application termination or code execution with the privileges of the VLC proc

  • 9.6 Critical severity

    Chrome: Integer Overflow or Wraparound

    CVE-2026-87643Google

    Integer overflow in GPU in Google Chrome on on Android prior to 153.0.8010.36 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

  • 7.8 High severity

    Adobe Acrobat: Integer Overflow or Wraparound

    CVE-2026-81987Adobe

    Acrobat Reader is affected by an Integer Overflow or Wraparound vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.