CVE-2026-41144 is an integer overflow vulnerability in the nasa fprime framework prior to version 4.2.0. The flaw occurs due to a 32-bit unsigned integer wraparound in a bounds check, allowing an attacker to bypass file size validation. This enables arbitrary file writes at controlled offsets combined with lack of sanitization on file paths, potentially leading to remote code execution on embedded targets. Version 4.2.0 includes a patch for this issue. No known workarounds exist.
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.4.0 through 3.4.9, 3.3.0 through 3.3.9, and 3.2.0 through 3.2.7, `internal_dwa_compressor.h:1040` performs `chan->width * chan->bytes_per_element` in `int32` arithmetic without a `(size_t)` cast. This is the same overflow pattern fixed in other decoders by CVE-2026-34589/34588/34544, but this line was missed. Versions 3.4.10, 3.3.10, and 3.2.8 contain a fix that addresses `internal_dwa_compressor.h:1040`.
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.4.0 through 3.4.9, 3.3.0 through 3.3.9, and 3.2.0 through 3.2.7, `internal_dwa_compressor.h:1722` performs `curc->width * curc->height` in `int32` arithmetic without a `(size_t)` cast. This is the same overflow pattern fixed in other locations by the recent CVE-2026-34589 batch, but this line was missed. Versions 3.4.10, 3.3.10, and 3.2.8 contain a fix that addresses `internal_dwa_compressor.h:1722`.
OpenEXR versions 3.4.0 through 3.4.9 contain a signed integer overflow vulnerability in the HTJ2K decompression path. The vulnerability occurs in the ht_undo_impl() function where a 32-bit signed integer accumulator for bytes-per-line (bpl) can overflow when processing a specially crafted EXR file with a large number of FLOAT channels and maximum width. This overflow can lead to undefined behavior and potentially a heap out-of-bounds write on hosts that allow large memory allocations. Version 3.4.10 includes a fix for this issue.
KissFFT before commit 8a8e66e contains an integer overflow vulnerability in the kiss_fftndr_alloc() function in kiss_fftndr.c where the allocation size calculation dimOther*(dimReal+2)*sizeof(kiss_fft_scalar) overflows signed 32-bit integer arithmetic before being widened to size_t, causing malloc() to allocate an undersized buffer. Attackers can trigger heap buffer overflow by providing crafted dimensions that cause the multiplication to exceed INT_MAX, allowing writes beyond the allocated buffer region when kiss_fftndr() processes the data.
OpenEXR is a high dynamic-range (HDR) image file format developed by Industrial Light & Magic for use in computer imaging applications. This package contains libraries and sample applications for handling the format.
Security Fix(es):
* openexr: OpenEXR: Arbitrary code execution via integer overflow in EXR file processing (CVE-2026-27622)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Firebird is an open-source relational database management system. In versions prior to 5.0.4, 4.0.7 and 3.0.14, the ClumpletReader::getClumpletSize() function can overflow the totalLength value when parsing a Wide type clumplet, causing an infinite loop. An authenticated user with INSERT privileges on any table can exploit this via a crafted Batch Parameter Block to cause a denial of service against the server. This issue has been fixed in versions 5.0.4, 4.0.7 and 3.0.14.
libsixel versions prior to 1.8.7-r1 contain a heap-based buffer overflow vulnerability caused by an integer overflow in the sixel_frame_convert_to_rgb888() function. This overflow leads to an undersized heap allocation and invalid pointer arithmetic when processing large palettised images, resulting in heap corruption. An attacker can exploit this by supplying a specially crafted large palettised PNG file, potentially causing a crash or arbitrary code execution. The issue is fixed in version 1.8.7-r1.
libsixel versions prior to 1.8.7-r1 contain an integer overflow vulnerability in the --crop option handling of img2sixel. This flaw allows an out-of-bounds heap read when processing specially crafted crop arguments with positive coordinates up to INT_MAX, leading to a crash and potential information disclosure. The issue arises because the calculation of clip boundaries overflows and bypasses bounds checking, causing memory beyond the image buffer to be accessed. This vulnerability has been fixed in version 1.8.7-r1.
jq is a command-line JSON processor. An integer overflow vulnerability exists through version 1.8.1 within the jvp_string_append() and jvp_string_copy_replace_bad functions, where concatenating strings with a combined length exceeding 2^31 bytes causes a 32-bit unsigned integer overflow in the buffer allocation size calculation, resulting in a drastically undersized heap buffer. Subsequent memory copy operations then write the full string data into this undersized buffer, causing a heap buffer overflow classified as CWE-190 (Integer Overflow) leading to CWE-122 (Heap-based Buffer Overflow). Any system evaluating untrusted jq queries is affected, as an attacker can crash the process or potentially achieve further exploitation through heap corruption by crafting queries that produce extremely large strings. The root cause is the absence of string size bounds checking, unlike arrays and objects which already have size limits. The issue has been addressed in commit e47e56d226519635768e6aab2f38f0ab037c09e5.
CVE-2026-40447 is an integer overflow or wraparound vulnerability in Samsung Open Source Escargot, specifically affecting version 97e8115ab1110bc502b4b5e4a0c689a71520d335. This vulnerability can cause undefined behavior due to improper handling of integer values. The issue has a medium severity rating with a CVSS score of 5.1. There is no known exploit in the wild and no official patch or remediation guidance has been provided yet.
CVE-2026-25208 is an integer overflow vulnerability in Samsung Open Source Escargot version 97e8115ab1110bc502b4b5e4a0c689a71520d335. The flaw allows for buffer overflow conditions due to improper handling of integer values. This vulnerability has a high severity rating with a CVSS score of 8.1, indicating it can lead to significant confidentiality, integrity, and availability impacts. No official patch or remediation guidance has been provided yet, and there are no known exploits in the wild at this time.
In libexif through 0.6.25, an unsigned 32bit integer overflow in Nikon MakerNote handling could be used by local attackers to cause crashes or information leaks. This only affects 32bit systems.
osslsigncode is a tool that implements Authenticode signing and timestamping. Prior to 2.13, an integer underflow vulnerability exists in osslsigncode version 2.12 and earlier in the PE page-hash computation code (pe_page_hash_calc()). When page hash processing is performed on a PE file, the function subtracts hdrsize from pagesize without first validating that pagesize >= hdrsize. If a malicious PE file sets SizeOfHeaders (hdrsize) larger than SectionAlignment (pagesize), the subtraction underflows and produces a very large unsigned length. The code allocates a zero-filled buffer of pagesize bytes and then attempts to hash pagesize - hdrsize bytes from that buffer. After the underflow, this results in an out-of-bounds read from the heap and can crash the process. The vulnerability can be triggered while signing a malicious PE file with page hashing enabled (-ph), or while verifying a malicious signed PE file that already contains page hashes. Verification of an already signed file does not require the verifier to pass -ph. This vulnerability is fixed in 2.13.
Integer Overflow or Wraparound vulnerability in Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ MQTT.
The fix for "CVE-2025-66168: MQTT control packet remaining length field is not properly validated" was only applied to 5.19.2 (and future 5.19.x) releases but was missed for all 6.0.0+ versions.
This issue affects Apache ActiveMQ: from 6.0.0 before 6.2.4; Apache ActiveMQ All: from 6.0.0 before 6.2.4; Apache ActiveMQ MQTT: from 6.0.0 before 6.2.4.
Users are recommended to upgrade to version 6.2.4 or a 5.19.x version starting with 5.19.2 or later (currently latest is 5.19.5), which fixes the issue.
A heap buffer overflow vulnerability exists in the DICOM image decoder. Dimension fields are encoded using Value Representation (VR) Unsigned Long (UL), instead of the expected VR Unsigned Short (US), which allows extremely large dimensions to be processed. This causes an integer overflow during frame size calculation and results in out-of-bounds memory access during image decoding.
A heap buffer overflow vulnerability exists during the decoding of `PALETTE COLOR` DICOM images. Pixel length validation uses 32-bit multiplication for width and height calculations. If these values overflow, the validation check incorrectly succeeds, allowing the decoder to read and write to memory beyond allocated buffers.