# CVE-2026-130065: msgpack-c through 7.0.2 Heap Buffer Overflow via msgpack_vrefbuffer_migrate

> Migrating msgpack-c vrefbuffers of unequal size overflows the heap, corrupting memory or crashing applications using it.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`msgpack_vrefbuffer_migrate`)
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-130065, GHSA-8pq6-mw7r-9f5g, UBUNTU-CVE-2026-130065

## What is CVE-2026-130065?

CVE-2026-130065 is a medium-severity memory corruption vulnerability in msgpack-c, published on 16 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-130065?

1 open source package ship an affected version, including msgpack/msgpack-c.

An affected version is only exploitable if your software calls msgpack_vrefbuffer_migrate. Many projects that include it are not exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `msgpack/msgpack-c` | GitHub | `pkg:github/msgpack/msgpack-c` | All versions to 7.0.2 | None |

## How do I fix CVE-2026-130065?

No fix has been published for CVE-2026-130065 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130065 being exploited?

There is no known exploitation of CVE-2026-130065 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130065 and fix it if it is affected.

What it is: CVE-2026-130065 is a medium-severity memory corruption vulnerability in msgpack-c, published on 16 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-130065 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls msgpack_vrefbuffer_migrate. Many projects that include it are not exposed.

Affected packages and fixed versions:
- msgpack/msgpack-c (GitHub): affected all versions up to 7.0.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to msgpack_vrefbuffer_migrate and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130065/ (Markdown: https://insights.sbomify.com/CVE-2026-130065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130065
- OSV: https://osv.dev/vulnerability/CVE-2026-130065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130065/
Summaries are generated and may contain mistakes; the official description above is the record.
