AI Stack Alert Medium CVE-2026-114499 For AI Eng, AppSec, SOC / IR AI-assisted
CVE-2026-114499: codebase-memory-mcp .gitignore matcher ReDoS-style stall before 0.10.0
codebase-memory-mcp versions prior to 0.10.0 have a .gitignore matcher that implements * and ** through recursive backtracking without a work bound. A repository with a crafted pattern of repeated wildcard groups and a long path can make matching work grow exponentially, stalling discovery indefinitely. The issue is fixed in version 0.10.0.
Why it matters
Developers and AI agents indexing an untrusted repository could have discovery stalled, and before worker isolation the server itself could stall. The stated impact is limited to availability.
Do this
- Upgrade codebase-memory-mcp to version 0.10.0 or later.
- Until patched, avoid indexing untrusted repositories that contain .gitignore files with repeated wildcard groups.
- Monitor indexer processes for unusually long CPU-bound runs during repository discovery.
- Run the MCP indexer under worker isolation or with timeouts so a stalled ignore rule cannot block the server.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 5.5CVSS
- NoPublic PoC
- 26/100Priority
- 70%Confidence
Evidence
“Prior to 0.10.0, the indexer's .gitignore matcher implemented * and ** through recursive backtracking without a work bound.”
“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.”
Sources
Affected / related
codebase-memory-mcp, codebase-memory-mcp
Published 2026-11-20 20:17 UTC · updated 2026-11-20 22:35 UTC · AI-assisted summary, checked against quoted sources · How we score