CVE-2026-72854 json
msgpack-c Integer Overflow in msgpack_unpacker_expand_buffer Causes a False-Success Undersized Reservation
published 2mo ago modified 24d ago also EUVD-2026-63537
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
msgpack_unpacker_expand_buffer in src/unpack.c, reached through the public msgpack_unpacker_reserve_buffer API, computes its new buffer size using an unchecked size_t addition of the requested size and the amount already used. The doubling loop guards its own multiplication against overflow, but the addition in the loop condition is unguarded, so a request near SIZE_MAX wraps: the loop condition is already satisfied, the allocation is performed at the small pre-wrap size, and the function returns true. The caller is told the requested capacity was reserved when it was not, so a subsequent write of the requested length overflows the heap buffer. The library's own example/lib_buffer_unpack.c demonstrates the reserve-then-write pattern, and its defensive assert comparing capacity against the request is compiled out under NDEBUG. msgpack-c's own decode entry points do not derive the reservation size from untrusted input, so reaching this requires an integration that passes an attacker-influenced length to the reservation API, such as a length-prefixed streaming transport.
Patch / fix
- msgpack-c Debian 14 7.0.2-1
debian advisories DEBIAN-CVE-2026-72854
- msgpack-c SLES for SAP applications 16.0, SLES 16.0 7.0.2-160000.1.1
suse advisories SUSE-SU-2026:23630-1
- msgpack-c openSUSE Leap 16.0 7.0.2-160000.1.1
- msgpack-c openSUSE Tumbleweed 7.0.2-2.1
opensuse advisories openSUSE-SU-2026:21768-1openSUSE-SU-2026:11672-1
Is CVE-2026-72854 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72854 updated cvss 5.3
msgpack-c: msgpack-c: Heap buffer overflow via integer overflow in buffer expansion.
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/msgpack/msgpack-c/issues/1181 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:L |
| CNA | 4.0 | 5.8 | CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.8 | CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:L |
Affected products
- msgpack msgpack-c
Classification
References
-
github.com
/msgpack/msgpack-c/issues/1181
issue-tracking, exploit
-
github.com
/msgpack/msgpack-c/blob/c-7.0.1/src/unpack.c#L429-L502
technical-description
-
github.com
/msgpack/msgpack-c/blob/c-7.0.1/include/msgpack/unpack.h#L219-L223
technical-description
-
github.com
/msgpack/msgpack-c/blob/c-7.0.1/example/lib_buffer_unpack.c
technical-description
-
github.com
/msgpack/msgpack-c
product
-
vulncheck.com
/advisories/msgpack-c-integer-overflow-in-msgpack-unpacker-expand-buffer-causes-a-false-success-undersized-res
third-party-advisory
Sources
- CVE List CVE-2026-72854
- NVD CVE-2026-72854
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.