Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@grackle-ai/mcp

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.6npmAmendedPublished

    @grackle-ai/mcp has a workspace authorization bypass in its knowledge_search MCP tool

    GHSA-647h-p824-99w7

    Affected
    • npm @grackle-ai/mcp <= 0.70.1
    Fixed in
    0.70.2· Vendor fix available
    Issue
    Impact The knowledgesearch and knowledgegetnode MCP tools are included in SCOPEDTOOLS (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 (knowledgesearch handler) - packages/mcp/src/tools/knowledge.ts:244-283 (knowledgegetnode handler) - packages/mcp/src/tool-scoping.ts:11 (both tools listed in SCOPEDTOOLS) Contrast with correct implementation: knowledgecreatenode (same file, lines 334-357) properly receives authContext and overrides the user-supplied workspaceId for scoped callers. Design Note Cross-workspace knowledge…

    Recommended action: Upgrade to 0.70.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →