# GHSA-647h-p824-99w7: @grackle-ai/mcp has a workspace authorization bypass in its knowledge_search MCP tool

> A scoped agent can bypass workspace isolation to read knowledge graph data from other workspaces by supplying an arbitrary workspace ID.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2026

## What is GHSA-647h-p824-99w7?

GHSA-647h-p824-99w7 is a missing authorization vulnerability in @grackle-ai/mcp, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Impact

The `knowledge_search` and `knowledge_get_node` MCP tools are included in `SCOPED_TOOLS` (visible to scoped agents) but their handlers do not receive `authContext` and do not enforce workspace scoping. A scoped agent in Workspace A can supply an arbitrary `workspaceId` parameter to search or retrieve knowledge graph nodes from Workspace B, bypassing workspace isolation boundaries.

This is a **cross-workspace data leakage** vulnerability affecting any deployment where multiple workspaces contain sensitive knowledge graph data and scoped agents are used.

**Affected code:**
- `packages/mcp/src/tools/knowledge.ts:146-169` (knowledge_search handler)
- `packages/mcp/src/tools/knowledge.ts:244-283` (knowledge_get_node handler)
- `packages/mcp/src/tool-scoping.ts:11` (both tools listed in SCOPED_TOOLS)

**Contrast with correct implementation:** `knowledge_create_node` (same file, lines 334-357) properly receives `authContext` and overrides the user-supplied `workspaceId` for scoped callers.

### Design Note

Cross-workspace knowledge sharing is a legitimate future feature — agents working across different repos may need to collaborate and share knowledge. However, this access should be **opt-in with explicit grants**, not an implicit bypass. The immediate fix locks scoped agents to their own workspace. A future design could introduce:
- Workspace-level "share knowledge with" settings
- A `cross_workspace` scope on scoped tokens
- Explicit `workspaceIds` (plural) in the auth context

### Patches

**Fix:** Add `authContext` parameter to `knowledge_search` and `knowledge_get_node` handlers and enforce workspace scoping, matching the pattern in `knowledge_create_node`:
```typescript
const resolvedWorkspaceId =
  authContext?.type === "scoped"
    ? authContext.workspaceId ?? ""
    : workspaceId ?? "";
```

When cross-workspace collaboration is designed, this check can be relaxed intentionally with proper access controls.

### Workarounds

Do not use scoped agent tokens in multi-workspace deployments until patched. Alternatively, remove `knowledge_search` and `knowledge_get_node` from the `SCOPED_TOOLS` set in `tool-scoping.ts`.

### References

- CWE-284: Improper Access Control
- File: `packages/mcp/src/tools/knowledge.ts`
- File: `packages/mcp/src/tool-scoping.ts`

## Which versions are affected by GHSA-647h-p824-99w7?

2 open source packages ship an affected version, including @grackle-ai/mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@grackle-ai/mcp` | npm | All versions | 0.70.2 |
| `@grackle-ai/mcp` | npm | All versions | 0.70.2 |

## How do I fix GHSA-647h-p824-99w7?

Upgrade @grackle-ai/mcp to 0.70.2 or later.

## Is GHSA-647h-p824-99w7 being exploited?

There is no known exploitation of GHSA-647h-p824-99w7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-647h-p824-99w7 and fix it if it is affected.

What it is: GHSA-647h-p824-99w7 is a missing authorization vulnerability in @grackle-ai/mcp, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-647h-p824-99w7 in the wild and no public exploit code.

Affected packages and fixed versions:
- @grackle-ai/mcp (npm): affected all versions; fixed in 0.70.2
- @grackle-ai/mcp (npm): affected all versions; fixed in 0.70.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-647h-p824-99w7/ (Markdown: https://insights.sbomify.com/GHSA-647h-p824-99w7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-647h-p824-99w7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-647h-p824-99w7/
Summaries are generated and may contain mistakes; the official description above is the record.