Skip to content
Fencer Intel
medium 5.5

CVE-2026-114499 json

codebase-memory-mcp: Catastrophic backtracking in .gitignore glob matching lets a repository stall the indexer

published 3d ago modified 16h ago also GHSA-cjhf-76h2-4hwg , EUVD-2026-131806

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository DeusData/codebase-memory-mcp. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

codebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.10.0, the indexer's .gitignore matcher implemented * and ** through recursive backtracking without a work bound. A repository containing a pattern with repeated wildcard groups and a long path could make matching work grow exponentially, allowing a single ignore rule to stall discovery indefinitely and, before worker isolation, stall the server. The impact is limited to availability, and the bounded matcher does not claim that every expensive input is eliminated. This issue is fixed in version 0.10.0.

Patch / fix

Is CVE-2026-114499 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm codebase-memory-mcp
<0.10.0
0.10.0

Affected products

  • DeusData codebase-memory-mcp

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-1333 Inefficient Regular Expression Complexity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of DeusData/codebase-memory-mcp published their own advisory on GitHub. Reviewed sources take precedence over it.