CVE-2026-114613: MessagePack · Unbounded memory leak in msgpack C extension on strict_map_key validation failure
Affects neovim-remoteSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 2.5.1_6 soon.
Data as of 29 Oct 2026, 19:04 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.1_6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade neovim-remote to 2.5.1_6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewneovim-remotepkg:brew/neovim-remoteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in msgpack-python version 2.5.1_6. Users should upgrade to this version to remediate the memory leak and use-after-free issues. As a temporary workaround, the pure-Python fallback can be used since it does not exhibit the memory leak on this path, though performance and compatibility should be evaluated. Limiting request size and rate may reduce but not eliminate memory leakage.
Description
The msgpack-python C extension has a memory leak vulnerability triggered when deserialization rejects a map key under strict_map_key validation. This causes unbounded memory growth and potential denial of service when processing attacker-controlled MessagePack data. Additionally, the streaming Unpacker API may suffer from a use-after-free due to stale parser-stack references. The issue affects version 1.2.2 and development commits, with a fix available in version 2.5.1_6.
References
- github.com/msgpack/msgpack-python/security/advisories/GHSA-j586-36cw-2gc2 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-114613 (opens in a new tab)
- github.com/msgpack/msgpack-python/commit/620b0eb4c89cd72d4098564537624d9dbb2ce141 (opens in a new tab)
- github.com/msgpack/msgpack-python (opens in a new tab)
- github.com/msgpack/msgpack-python/releases/tag/v1.2.3 (opens in a new tab)