codebase-memory-mcp stack buffer overflow in query_graph Cypher parsing
Affects codebase-memory-mcp before 0.9.0 when a query_graph query has more than 32 projection items in a RETURN or WITH clause. Fixed in 0.9.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.9.0
- Who is exposed
- Specific setups only
Summary
DeusData's codebase-memory-mcp has a stack out-of-bounds write in its query_graph tool, triggered by a Cypher query with more than 32 items in a RETURN or WITH clause. A local user with low privileges and no user action needed can use it to crash the software and potentially compromise its confidentiality and integrity.
Written by a model
Original description
codebase-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.
Who should check
Teams running codebase-memory-mcp before 0.9.0, including agent setups that call its query_graph tool.
“Before 0.9.0 the Cypher parser did not bound the number of projection items”
What to do
Check whether your setup matches what the bug needs.
codebase-memory-mcp before 0.9.0 A query_graph query with more than 32 projection items in a RETURN or WITH clauseUpgrade to a fixed version: 0.9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-114494 (codebase-memory-mcp: Stack out-of-bounds write in query_graph via a RETURN or WITH clause with more than 32 items), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-114494 (entry last updated 2026-11-20):
Affected:
- DeusData codebase-memory-mcp: fixed in 0.9.0
Fixed versions: 0.9.0.
Conditions (all must be true for the bug to be hit):
- codebase-memory-mcp before 0.9.0 (source: https://github.com/DeusData/codebase-memory-mcp/security/advisories/GHSA-vpgh-g3jg-ggx9)
- A query_graph query with more than 32 projection items in a RETURN or WITH clause (source: https://github.com/DeusData/codebase-memory-mcp/security/advisories/GHSA-vpgh-g3jg-ggx9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-114494 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114494 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DeusData/codebase-memory-mcp/security/advisories/GHSA-vpgh-g3jg-ggx9
- https://github.com/DeusData/codebase-memory-mcp/pull/941
- https://github.com/DeusData/codebase-memory-mcp/commit/e69e0844dbc1c737ebd3d17e97007d0f5cf16beb
- https://github.com/DeusData/codebase-memory-mcp/releases/tag/v0.9.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-114494
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114494"}.Affected versions
- DeusData codebase-memory-mcpfixed in 0.9.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.8/10CVSS 7.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · DeusData/codebase-memory-mcp · Advisory GHSA-vpgh-g3jg-ggx9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-114494 |
| Record | NVD · CVE-2026-114494 |
| Other links 3 | |
| Repository | GitHub · DeusData/codebase-memory-mcp · Pull request #941 |
| Repository | GitHub · DeusData/codebase-memory-mcp · Commit e69e0844 |
| Repository | GitHub · DeusData/codebase-memory-mcp · Release v0.9.0 |
Questions about CVE-2026-114494
Is CVE-2026-114494 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Cypher parser did not limit the number of projection items, so a RETURN or WITH clause with more than 32 items writes past its stack arrays. This corrupts stack memory in the server process, causing a reliable crash and potentially worse outcomes depending on memory layout.
Source: github.com
Which versions are affected by CVE-2026-114494?
codebase-memory-mcp: before 0.9.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions before 0.9.0 are affected, in the setup where a query_graph query has more than 32 projection items in a RETURN or WITH clause. To check the version, look at the installed codebase-memory-mcp version.
Source: github.com
How do I fix CVE-2026-114494?
Upgrade codebase-memory-mcp to 0.9.0 or later, which is the fixed version.
Source: github.com
Related
- CVE-2026-114495codebase-memory-mcp: Heap buffer overflow on artifact import via int-truncated decompression capacity
- CVE-2026-114499codebase-memory-mcp: Catastrophic backtracking in .gitignore glob matching lets a repository stall the indexer
- CVE-2026-114496codebase-memory-mcp: git option injection through base_branch in detect_changes allows writing a file outside the project
- CVE-2026-114497codebase-memory-mcp: UI process-kill route skipped the ownership check on Windows, allowing termination of arbitrary processes
- CVE-2026-129713Stack-based buffer overflow in Danfoss AK-SM8xxA unauthenticated CGI handler
- CVE-2026-133528BeamNG.drive before 0.40.6 LuaJIT FFI Sandbox Escape via JIT Bounds-Check Bypass
No corrections so far. Something wrong on this page? Report an error.