
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-130065 is a heap buffer overflow vulnerability in msgpack-c through version 7.0.2, located in the msgpack_vrefbuffer_migrate() function in src/vrefbuffer.c. The flaw was reported on October 28, 2026 by researcher AmirWilayah via a GitHub issue, and a fix was committed on October 30, 2026; the CVE was published on November 16, 2026. All releases of msgpack-c up to and including 7.0.2 are affected. It carries a CVSS v3.1 base score of 5.3 (Medium) and a CVSS v4.0 base score of 5.8 (Medium) (Github Advisory, Feedly).
The root cause is an out-of-bounds write (CWE-787) caused by a cross-object pointer comparison in msgpack_vrefbuffer_migrate() at line 201 of src/vrefbuffer.c. The buggy condition if(to->tail + nused < vbuf->end) compares a pointer derived from the destination buffer (to) against the end pointer of the source buffer (vbuf) — two independent heap allocations — which is undefined behavior per C11 §6.5.8p5. When this comparison incorrectly evaluates to false (depending on heap layout), the realloc growth step is skipped, and the subsequent memcpy() at line 227 writes nused iovec entries past the end of to->array's actual allocation, corrupting adjacent heap memory. The fix, committed as 1c47ce0, changes the condition to if(nused > (size_t)(to->end - to->tail)), comparing only within the destination object (GitHub Issue, Fix Commit, Vulnerable Source).
Successful exploitation results in heap memory corruption adjacent to the destination iovec array, with attacker-influenced content (iovec structs containing pointer and length pairs) written out of bounds. The primary impacts are high integrity loss (arbitrary heap corruption) and low availability impact (application crash/abort), with no direct confidentiality impact. Depending on heap layout, corruption of adjacent allocations could potentially be leveraged for further memory exploitation, though the local attack vector and high complexity significantly limit practical impact (Github Advisory, GitHub Issue).
No public proof-of-concept exploit code has been released beyond the minimal PoC included in the original GitHub issue report, which demonstrates heap corruption under plain glibc malloc and an AddressSanitizer-reproducible variant via AFL++ fuzzing. There is no evidence of in-the-wild exploitation, no known threat actor attribution, and the vulnerability is not listed in the CISA KEV catalog. The EPSS score is 0.0, reflecting negligible current exploitation probability (Feedly, GitHub Issue).
msgpack_vrefbuffer_migrate() code path, either directly or through higher-level buffer-merging logic.msgpack_vrefbuffer_init() on two independent buffers (vbuf and to) with default parameters.msgpack_vrefbuffer_append_ref() on vbuf approximately 20 times to grow its internal iovec array to 20 used entries.msgpack_vrefbuffer_append_ref() on to approximately 5 times (growing its array to a real capacity of ~8 iovecs), then call msgpack_vrefbuffer_clear() to reset to->tail without shrinking the allocation.msgpack_vrefbuffer_migrate(&vbuf, &to). Due to the cross-object pointer comparison bug, the realloc is skipped and memcpy() writes 20 iovecs (320 bytes) into a buffer with capacity for only 8 (136 bytes), overflowing by ~184 bytes into adjacent heap memory.SIGABRT or SIGSEGV, particularly with error messages such as free(): invalid size, heap-buffer-overflow, or AddressSanitizer: heap-buffer-overflow in stderr or crash logs, originating from msgpack_vrefbuffer_migrate in src/vrefbuffer.c:227.msgpack_vrefbuffer_migrate or vrefbuffer.c in stack traces.core, core.<pid>) in the application working directory following abnormal termination of a msgpack-c-linked process (GitHub Issue).Update msgpack-c to a version after 7.0.2 that includes the fix from commit 1c47ce020a019a3d4246e6394176779ecdf9d502, which corrects the bounds check in msgpack_vrefbuffer_migrate() to compare against the destination buffer's own end pointer. If immediate patching is not possible, limit or restrict user-controlled input that can trigger msgpack_vrefbuffer_migrate() operations with imbalanced buffer sizes. Applications using msgpack-c for streaming or zero-copy serialization via msgpack_packer-style paths should be prioritized for patching (Github Advisory, Fix Commit).
Fix availability across major Linux distributions and their releases.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."