CVE-2026-114495

codebase-memory-mcp artifact decompression could overflow a heap buffer

DeusData · codebase-memory-mcp

First documented disclosure · Review checkpoint

Summary

Automatically importing a malicious repository artifact could corrupt memory.

Severity and exploitation evidence

High · 7.8/10 · CVSS 3.1. Severity source.

Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

64-bit original_size allocation and int-truncated decompression capacity disagree.

Conditions required

Indexing an untrusted repository containing a crafted .codebase-memory artifact.

Potential impact

Reliable crash and potential code execution from attacker-controlled decompressed bytes.

Affected versions and configurations

Before 0.9.0.

Fix and mitigation status

0.9.0; maintainer recommends verified 0.12.1.

Practical next steps

Upgrade to 0.12.1 or later; avoid untrusted repository artifacts on affected releases.

Operating lesson

Use one validated size type for allocation and decompression.

Evidence and limits

Fixed import uses frame size, metadata/cap validation and size_t capacity. Maintainer regression was a size mismatch test, not a direct multi-gigabyte reproduction; not all resource exhaustion is claimed fixed. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 7.8.

Sources