{
  "schema_version": "1.6.0",
  "id": "ACVE-2026-0427",
  "aliases": [],
  "published": "2025-07-08T00:00:00Z",
  "firstReported": {
    "date": "2025-07-08",
    "url": "https://generalanalysis.com/blog/supabase-mcp-blog",
    "publisher": "General Analysis"
  },
  "modified": "2026-09-25T00:00:00Z",
  "summary": "A support ticket's text steers an MCP client such as Cursor into copying a private table into the ticket via a Supabase MCP server with the service_role key and no read-only or project scoping.",
  "details": "## What\n\nA 2025 demonstration. General Analysis (2025-07-08) filed a support ticket containing instructions addressed to the coding assistant. When a developer later reviewed tickets in Cursor through the Supabase MCP server, the assistant followed them, read the `integration_tokens` table with `service_role` privileges, which bypass row-level security, and wrote the contents back into the ticket. The weakness is the MCP server's configuration, not Cursor. Supabase answered on 2025-09-16 with read-only mode, project scoping and wrapped query results.\n\n## Detection\n\nThe lockfile cannot see `read_only` or `project_ref`, so a finding only means: check them by hand.\n\n## Fix\n\nSet `read_only=true` and `project_ref`, point the server at a non-production project and keep manual approval of tool calls.",
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@supabase/mcp-server-supabase",
        "purl": "pkg:npm/@supabase/mcp-server-supabase"
      },
      "ranges": [
        {
          "type": "SEMVER",
          "events": [
            {
              "introduced": "0"
            }
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "type": "REPORT",
      "url": "https://generalanalysis.com/blog/supabase-mcp-blog"
    },
    {
      "type": "ADVISORY",
      "url": "https://supabase.com/blog/defense-in-depth-mcp"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/supabase-community/supabase-mcp"
    }
  ],
  "database_specific": {
    "severity": "CRITICAL",
    "acve": {
      "specVersion": 1,
      "status": "candidate",
      "kind": "code",
      "vulnClasses": [
        "prompt-injection-to-tool",
        "data-exfiltration",
        "over-privileged-combination"
      ],
      "cwe": [
        "CWE-1427"
      ],
      "exposure": {
        "harness": {
          "value": "An MCP client such as Cursor connected to @supabase/mcp-server-supabase (or mcp.supabase.com) against data that contains user-submitted text",
          "any": false,
          "status": "confirmed",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        },
        "model": {
          "value": "Claude, as used inside Cursor in the demonstration; the version is not named",
          "any": false,
          "status": "detected",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        },
        "goal": {
          "value": "Show me the latest open support ticket",
          "stated": true,
          "status": "confirmed",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        },
        "tools": {
          "value": "The Supabase MCP server configured with the service_role key, which bypasses row-level security, and without read_only or project_ref scoping; the integration_tokens table; the support ticket text the server returns",
          "status": "confirmed",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        },
        "approval": {
          "value": "Cursor's agent runs the MCP SQL tool calls automatically, without a manual approval step before each query",
          "mode": "always-allow",
          "status": "detected",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        },
        "inputControl": "content-author",
        "agentAction": "Following text embedded in a support ticket, the assistant reads the integration_tokens table with service_role privileges and writes its contents back into the ticket.",
        "harm": "data-exfiltration",
        "divergence": "goal-hijacked",
        "reach": {
          "value": "The whole database, via the service_role key",
          "kinds": [
            "production-database",
            "api-keys"
          ],
          "status": "confirmed",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        },
        "condition": {
          "value": "When the MCP server runs with the service_role key and without read-only or project scoping",
          "status": "confirmed",
          "source": "https://generalanalysis.com/blog/supabase-mcp-blog"
        }
      },
      "occurrence": {
        "basis": "demonstrated",
        "reportedBy": "researcher",
        "responses": [
          {
            "party": "Supabase",
            "status": "acknowledged",
            "source": "https://supabase.com/blog/defense-in-depth-mcp"
          }
        ]
      },
      "exploitation": {
        "status": "demonstrated",
        "checkedAt": "2026-09-21T00:00:00Z",
        "sources": [
          {
            "url": "https://generalanalysis.com/blog/supabase-mcp-blog",
            "type": "research"
          },
          {
            "url": "https://supabase.com/blog/defense-in-depth-mcp",
            "type": "vendor"
          }
        ],
        "kev": {
          "listed": false
        }
      },
      "taxonomy": {
        "owasp_asi": [
          "ASI01",
          "ASI03",
          "ASI02"
        ],
        "atlas": [
          "AML.T0093",
          "AML.T0051.001",
          "AML.T0086"
        ]
      },
      "cveBoundary": "user-configured",
      "noCveReason": "No CVE was assigned; the vendor treats it as a configuration and design risk.",
      "fix": {
        "summary": "Run the Supabase MCP server read-only, scoped to one non-production project.",
        "actions": [
          {
            "type": "reconfigure",
            "target": "mcpServers: @supabase/mcp-server-supabase",
            "to": "read_only=true, project_ref=<project>",
            "why": "Both options are documented in the server README and the vendor post.",
            "owner": "operator"
          },
          {
            "type": "reconfigure",
            "target": "supabase.mcp-server",
            "to": "read-only mode, project scoping and wrapped query results",
            "why": "Shipped by Supabase (2025-09-16): its answer to the demonstration.",
            "owner": "tool-provider"
          }
        ]
      },
      "reproducibility": {
        "status": "partial",
        "axesComplete": true,
        "componentsObtainable": null,
        "triggerPublished": false,
        "observableStated": true,
        "demonstrated": "researcher-demonstrated",
        "missing": [
          "model availability not checked (no registry reference)",
          "trigger not published"
        ]
      },
      "severityBasis": "harm-reach"
    }
  }
}
