CVE-2026-114499
codebase-memory-mcp ignore patterns could stall indexing
DeusData · codebase-memory-mcp
First documented disclosure · Review checkpoint
Summary
A malicious repository’s ignore rule could consume unbounded matching work.
Severity and exploitation evidence
Medium · 5.5/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.
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
Recursive wildcard backtracking grows exponentially for repeated wildcards and long paths.
Conditions required
Indexing a repository containing attacker-controlled .gitignore patterns and paths.
Potential impact
Indexer stall; before worker isolation, the MCP server could also stall.
Affected versions and configurations
Before 0.10.0.
Fix and mitigation status
0.10.0; maintainer recommends verified 0.12.1.
Practical next steps
Upgrade to 0.12.1 or later.
Operating lesson
Apply a shared deterministic work budget to recursive matchers.
Evidence and limits
Maintainer verified a20,000-step budget in 0.12.1. Exhaustion gives non-match in the legacy path and explicit exhaustion in the checked matcher; this does not eliminate every expensive input. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 3.1 5.5.
Sources
- GitHub_M CVE authority record
Primary source ·
- codebase-memory-mcp original advisory
Primary source ·
- Public corrective change
Primary source ·