Deusdata vulnerabilities

Known vulnerabilities in Deusdata products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 1 product.

Products

1
RoutineCVE-2026-114499deusdata · codebase-memory-mcpcodebase-memory-mcp: Catastrophic backtracking in .gitignore glob matching lets a repository stall the indexercodebase-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.CVSS5.5MediumRoutineCVE-2026-114495deusdata · codebase-memory-mcpcodebase-memory-mcp: Heap buffer overflow on artifact import via int-truncated decompression capacitycodebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.0, automatic import of a repository's .codebase-memory/ artifact allocated a decompression buffer using the attacker-controlled 64-bit original_size value from artifact.json but truncated that value to int when passing the destination capacity to the Zstandard decompressor. A value with bit 31 set became negative and was sign-extended to a large size_t, allowing the decompressor to write frame content beyond the actual allocation. Indexing a malicious repository containing the crafted artifact could corrupt heap memory with attacker-controlled bytes, causing a reliable crash and potentially code execution. This issue is fixed in version 0.9.0.CVSS7.8HighRoutineCVE-2026-114494deusdata · codebase-memory-mcpcodebase-memory-mcp: Stack out-of-bounds write in query_graph via a RETURN or WITH clause with more than 32 itemscodebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.0, the Cypher parser accepted an unbounded number of projection items in RETURN and WITH clauses while projection executors indexed fixed 32-element stack arrays using the parsed count. A query_graph query with more than 32 projection items could therefore write beyond those arrays, and a related result-column path could read uninitialized stack slots even when no node matched. Any caller of query_graph, including an agent whose query is influenced by untrusted content, could cause a reliable server crash and potentially compromise process confidentiality and integrity. This issue is fixed in version 0.9.0.CVSS7.8HighRoutineCVE-2026-114496deusdata · codebase-memory-mcpcodebase-memory-mcp: git option injection through base_branch in detect_changes allows writing a file outside the projectcodebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.0, the detect_changes tool validated the base_branch argument for shell metacharacters but omitted the leading-dash check before placing the value in the revision position of a git diff command. Git therefore interpreted an option-shaped base_branch value, including --output, as a command option instead of a revision, allowing a caller to create or overwrite a caller-chosen file with Git diff output under the server process's permissions. Arbitrary code execution was not demonstrated. This issue is fixed in version 0.9.0.CVSS5.5MediumRoutineCVE-2026-114497deusdata · codebase-memory-mcpcodebase-memory-mcp: UI process-kill route skipped the ownership check on Windows, allowing termination of arbitrary processescodebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.1-rc.1, the optional graph UI's POST /api/process-kill route omitted the indexing-job ownership check on Windows while retaining that check on POSIX systems. A requester able to reach the optional UI could supply an arbitrary process identifier, causing TerminateProcess to stop any process that the server user was permitted to terminate. The flaw affects the Windows-specific process termination path and can cause a high availability impact without disclosing or modifying data. This issue is fixed in version 0.9.1-rc.1.CVSS5.5Medium