Summary Authorization for scoped (agent) MCP callers is enforced inline, per tool, and is applied inconsistently — several mutating tools silently omit the ancestry/workspace check that their siblings perform. Because the MCP server authenticates all outbound gRPC with the full s...
Vendor
grackle-ai vulnerabilities
9 published CVES affecting grackle-ai, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 0
- High
- 4
- Medium
- 2
- Low
- 3
- Unscored
- 0
- CISA KEV
- 0
Products
- @grackle-ai/server 5
- @grackle-ai/mcp 2
- @grackle-ai/powerline 2
- @grackle-ai/auth 1
- @grackle-ai/plugin-core 1
- @grackle-ai/runtime-sdk 1
Latest grackle-ai CVEs
Newest publication first
-
HighCVSS 8.7
-
HighCVSS 8.7
Summary The default git executor used for all worktree operations spawns git through a shell, and the untrusted task branch name flows into the command unsanitized. A caller able to reach the PowerLine SpawnSession RPC (a malicious or compromised agent acting through the orchestr...
-
LowCVSS 2.1
Impact JSON.parse(env.adapterConfig) is called without error handling in three locations within the gRPC service. While the data originates from the server's own SQLite database and should always be valid JSON, database corruption, migration errors, or unexpected state could caus...
-
LowCVSS 2.3
Impact The session cookie is set with HttpOnly; SameSite=Lax; Path=/ but does not include the Secure flag. This means the cookie will be sent over plain HTTP connections. Since the server binds to 127.0.0.1 by default and uses HTTP (not HTTPS), this is acceptable for localhost us...
-
MediumCVSS 5.3
Impact The HTTP server does not set Content-Security-Policy, X-Frame-Options, or X-Content-Type-Options headers on any response. This reduces defense-in-depth against XSS, clickjacking, and MIME-sniffing attacks. While the current XSS attack surface is small (React-markdown is co...
-
MediumCVSS 6.3
Impact When --token is not provided and GRACKLE_POWERLINE_TOKEN is not set, the PowerLine gRPC server runs with zero authentication. A warning is logged ("NO AUTH (development only)") but nothing prevents deployment in this state. Any client that can reach the PowerLine port can...
-
HighCVSS 7.1
Impact The WebSocket upgrade handler in the server validates authentication (API key token or session cookie) but does not check the Origin header. A malicious webpage on a different origin could initiate a WebSocket connection to ws://localhost:3000/ws if it can leverage the use...
-
HighCVSS 8.6
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...
-
GHSA-7q9x-8g6p-3x75 @grackle-ai/server: Unescaped Error String in renderPairingPage() HTML Template
PublishedLowCVSS 2.3Impact The renderPairingPage() function embeds the error parameter directly into HTML without escaping: const errorHtml = error ? `<p style="color:#e74c3c">${error}</p>` : ""; All current call sites pass hardcoded strings, so this is not exploitable today. However, the function i...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.