Debian Package Tracker
Register | Log in
Subscribe

msgpack-c

Choose email to subscribe with

general
  • source: msgpack-c (main)
  • version: 7.0.2-2
  • maintainer: James McCoy (DMD)
  • arch: all any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 3.3.0-4
  • oldstable: 4.0.0-3
  • stable: 6.0.1-3
  • testing: 7.0.2-2
  • unstable: 7.0.2-2
versioned links
  • 3.3.0-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.0.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 6.0.1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 6.1.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 7.0.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libmsgpack-c-dev
  • libmsgpack-c-doc
  • libmsgpack-c2
action needed
2 security issues in trixie high

There are 2 open security issues in trixie.

1 important issue:
  • CVE-2026-130065: msgpack-c through 7.0.2 contains a heap buffer overflow vulnerability in msgpack_vrefbuffer_migrate() in src/vrefbuffer.c that checks capacity against the source array's end pointer. When migrating between vrefbuffers of unequal size, the realloc is skipped and memcpy() writes iovec entries past the destination array, corrupting adjacent heap memory or crashing the application.
1 issue left for the package maintainer to handle:
  • CVE-2026-72854: (needs triaging) 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.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-08-21 Last update: 2026-11-17 10:47
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2026-130065: msgpack-c through 7.0.2 contains a heap buffer overflow vulnerability in msgpack_vrefbuffer_migrate() in src/vrefbuffer.c that checks capacity against the source array's end pointer. When migrating between vrefbuffers of unequal size, the realloc is skipped and memcpy() writes iovec entries past the destination array, corrupting adjacent heap memory or crashing the application.
Created: 2026-11-17 Last update: 2026-11-17 10:47
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-130065: msgpack-c through 7.0.2 contains a heap buffer overflow vulnerability in msgpack_vrefbuffer_migrate() in src/vrefbuffer.c that checks capacity against the source array's end pointer. When migrating between vrefbuffers of unequal size, the realloc is skipped and memcpy() writes iovec entries past the destination array, corrupting adjacent heap memory or crashing the application.
Created: 2026-11-17 Last update: 2026-11-17 10:47
2 security issues in bookworm high

There are 2 open security issues in bookworm.

1 important issue:
  • CVE-2026-130065: msgpack-c through 7.0.2 contains a heap buffer overflow vulnerability in msgpack_vrefbuffer_migrate() in src/vrefbuffer.c that checks capacity against the source array's end pointer. When migrating between vrefbuffers of unequal size, the realloc is skipped and memcpy() writes iovec entries past the destination array, corrupting adjacent heap memory or crashing the application.
1 issue postponed or untriaged:
  • CVE-2026-72854: (postponed; to be fixed through a stable update) 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.
Created: 2026-11-17 Last update: 2026-11-17 10:47
1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:
  • CVE-2026-72854: 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.
Created: 2026-08-21 Last update: 2026-08-24 11:30
news
[rss feed]
  • [2026-11-13] msgpack-c 7.0.2-2 MIGRATED to testing (Debian testing watch)
  • [2026-11-10] Accepted msgpack-c 7.0.2-2 (source) into unstable (James McCoy)
  • [2026-10-15] msgpack-c 7.0.2-1 MIGRATED to testing (Debian testing watch)
  • [2026-10-12] Accepted msgpack-c 7.0.2-1 (source) into unstable (James McCoy)
  • [2026-07-17] msgpack-c 7.0.1-1 MIGRATED to testing (Debian testing watch)
  • [2026-07-15] Accepted msgpack-c 7.0.1-1 (source) into unstable (James McCoy)
  • [2025-10-04] msgpack-c 6.1.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-10-01] Accepted msgpack-c 6.1.0-2 (source) into unstable (James McCoy)
  • [2025-10-01] Accepted msgpack-c 6.1.0-1 (source) into unstable (James McCoy)
  • [2024-06-06] msgpack-c 6.0.1-3 MIGRATED to testing (Debian testing watch)
  • [2024-06-04] Accepted msgpack-c 6.0.1-3 (source) into unstable (James McCoy)
  • [2024-06-02] Accepted msgpack-c 6.0.1-2 (source) into unstable (James McCoy)
  • [2024-05-25] Accepted msgpack-c 6.0.1-1 (source) into experimental (James McCoy)
  • [2024-02-06] Accepted msgpack-c 6.0.0-5 (source) into experimental (James McCoy)
  • [2023-09-04] Accepted msgpack-c 6.0.0-4 (source) into experimental (James McCoy)
  • [2023-06-24] Accepted msgpack-c 6.0.0-3 (source) into experimental (James McCoy)
  • [2023-06-24] Accepted msgpack-c 6.0.0-2 (source) into experimental (James McCoy)
  • [2023-06-12] Accepted msgpack-c 6.0.0-1 (all amd64 source) into experimental (Debian FTP Masters) (signed by: James McCoy)
  • [2023-01-10] msgpack-c 4.0.0-3 MIGRATED to testing (Debian testing watch)
  • [2023-01-04] Accepted msgpack-c 4.0.0-3 (source) into unstable (James McCoy)
  • [2023-01-03] Accepted msgpack-c 4.0.0-2 (source) into unstable (James McCoy)
  • [2022-07-31] msgpack-c 4.0.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-26] Accepted msgpack-c 4.0.0-1 (source) into unstable (James McCoy)
  • [2020-07-23] msgpack-c 3.3.0-4 MIGRATED to testing (Debian testing watch)
  • [2020-07-20] Accepted msgpack-c 3.3.0-4 (source) into unstable (James McCoy)
  • [2020-07-18] msgpack-c 3.3.0-3 MIGRATED to testing (Debian testing watch)
  • [2020-07-15] Accepted msgpack-c 3.3.0-3 (source) into unstable (James McCoy)
  • [2020-07-15] Accepted msgpack-c 3.3.0-2 (source) into unstable (James McCoy)
  • [2020-06-06] Accepted msgpack-c 3.3.0-1 (source) into unstable (James McCoy)
  • [2020-01-02] Accepted msgpack-c 3.2.1-1 (source) into experimental (James McCoy)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 7.0.2-1
  • 1 bug

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing