74 matches found
CVE-2026-114115
A flaw was found in Vyper. The compiler improperly calculates memory offsets when handling conditional ternary expressions that select between nested arrays with mismatched dimensions. A remote user interacting with an affected smart contract can trigger this condition, causing the contract to re...
CVE-2021-48019 Vyper before 0.2.9 Incorrect RETURNDATASIZE in create_forwarder_to Proxies
Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...
CVE-2021-48019
Vyper versions before 0.2.9 are vulnerable to an issue where the built-in create_forwarder_to function deploys forwarder proxies that report a fixed 4096-byte RETURNDATASIZE instead of the actual return data size. This discrepancy can lead to corrupted data if a function returns more than 4096 by...
CVE-2021-48019 Vyper before 0.2.9 Incorrect RETURNDATASIZE in create_forwarder_to Proxies
Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...
CVE-2021-48019: Buffer Access with Incorrect Length Value
Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...
Vyper buffer error vulnerability
Vyper versions prior to 0.2.9 contain a buffer error vulnerability. This vulnerability arises because the forwarder proxy deployed via the built-in createforwarderto function reports a fixed value of 4096 bytes for RETURNDATASIZE instead of the actual size of returned data. When the function...
AZL-106854 CVE-2026-107296 affecting package msgpack 3.3.0-1
msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, decoding a negative signed 64-bit integer modifies the corresponding bytes in the caller-provided input buffer while computing the value. Applications that retain or reuse encoded input for integrity checks,...
CVE-2026-107296
msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, decoding a negative signed 64-bit integer modifies the corresponding bytes in the caller-provided input buffer while computing the value. Applications that retain or reuse encoded input for integrity checks,...
PT-2026-108671
Impact Decoding a negative signed 64-bit integer modifies the corresponding bytes in the caller-provided input buffer. Applications that retain or reuse encoded input for integrity checks, logging, or subsequent processing may observe silently corrupted data. Positive integers and other MessagePa...
PT-2026-89718
Several functions in cstruct may use wrong data, leading to unexpected exceptions and return corrupted data. Impact - Cstruct.filter map writes retained bytes at their original input positions, producing corrupted output when earlier bytes are dropped. - Cstruct.tail rev:true removes two bytes...
CVE-2026-63818
In the Linux kernel, the following vulnerability has been resolved: f2fs: validate orphan inode entry count f2fsrecoverorphaninodes trusts the orphan block entrycount when replaying orphan inodes from the checkpoint pack. A corrupted entrycount larger than F2FSORPHANSPERBLOCK makes the recovery...
PT-2026-65425
The updated bind packages fix a security vulnerability: When BIND 9 was configured to use DNS64 and encounters a DNAME redirect, it could end up using freed memory for the DNS response owner name. This caused the response to contain corrupted data...
CVE-2026-31449
The CVE-2026-31449 entry concerns the Linux kernel ext4 extent code. A vulnerability was fixed in ext4_ext_correct_indexes where path[k].p_idx could point outside the valid index range if the on-disk eh_entries were corrupted, causing a slab-out-of-bounds read. The fix validates path[k].p_idx aga...
CVE-2025-47392
Memory corruption when decoding corrupted satellite data files with invalid signature offsets...
EUVD-2025-209230
Memory corruption when decoding corrupted satellite data files with invalid signature offsets...
CVE-2025-47392
Memory corruption when decoding corrupted satellite data files with invalid signature offsets...
CVE-2026-0954
There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted DSB file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially...
CVE-2026-0954 Out-Of-Bounds Write When Opening a Corrupt DSB File in Digilent DASYLab
There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted DSB file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially...
CVE-2026-0954 Out-Of-Bounds Write When Opening a Corrupt DSB File in Digilent DASYLab
There is a memory corruption vulnerability due to an out-of-bounds write when loading a corrupted DSB file in Digilent DASYLab. This vulnerability may result in information disclosure or arbitrary code execution. Successful exploitation requires an attacker to get a user to open a specially...
Digilent DASYLab security vulnerabilities
Digilent DASYLab is a graphical data acquisition and application development platform developed by Digilent, Inc. There is a security vulnerability in Digilent DASYLab, which stems from out-of-bound writing when loading corrupted DSB files. This vulnerability may lead to information leakage or th...