CVE-2026-48774

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-48774", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-05-22T19:39:05.357Z", "datePublished": "2026-06-19T19:34:39.971Z", "dateUpdated": "2026-06-23T02:23:14.975Z"}, "containers": {"cna": {"title": "ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract", "problemTypes": [{"descriptions": [{"cweId": "CWE-20", "lang": "en", "description": "CWE-20: Improper Input Validation", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4"}, {"name": "https://github.com/sysown/proxysql/commit/e32b7fd50c7c234ea628e392e621e09a2a919e08", "tags": ["x_refsource_MISC"], "url": "https://github.com/sysown/proxysql/commit/e32b7fd50c7c234ea628e392e621e09a2a919e08"}], "affected": [{"vendor": "sysown", "product": "proxysql", "versions": [{"version": ">= 3.0.6, < 3.0.9", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-19T19:34:39.971Z"}, "descriptions": [{"lang": "en", "value": "ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 3.0.0 through 3.0.8, ProxySQL's GenAI/MCP `run_sql_readonly` tool violates its documented read-only contract for MySQL targets. The tool validates only the full input string with a substring blacklist and first-keyword allowlist, but then executes the entire SQL string on a backend connection created with `CLIENT_MULTI_STATEMENTS`. As a result, a caller can submit a read-only first statement followed by a side-effecting second statement, such as `SELECT 1; RENAME TABLE ...`. The validator accepts the payload because it starts with `SELECT` and because side-effecting MySQL statements such as `RENAME TABLE`, `SET`, `RESET`, `LOCK TABLES`, and `KILL` are not rejected by the blacklist. In a live MCP runtime test, the `/mcp/query` endpoint accepted a `run_sql_readonly` request. The MCP response reported success for the first `SELECT`, and direct backend verification showed that the table had actually been renamed. This violates the endpoint's read-only security contract and lets an MCP caller perform backend writes or administrative SQL, limited by the configured MCP target account's database privileges. Version 3.0.9 contains a fix. Other operator mitigations include: keeping MCP disabled unless required; setting a non-empty `mcp-query_endpoint_auth` token before exposing `/mcp/query`; restricting MCP listener network exposure; configuring MCP backend target credentials as database-level read-only users; and adding temporary MCP query rules to block obvious multi-statement patterns."}], "source": {"advisory": "GHSA-7wh6-2vcc-gcm4", "discovery": "UNKNOWN"}}, "adp": [{"references": [{"url": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4", "tags": ["exploit"]}], "metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-06-23T02:22:42.341874Z", "id": "CVE-2026-48774", "options": [{"Exploitation": "poc"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-06-23T02:23:14.975Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-48774", "role": "CISA Coordinator", "options": [{"Exploitation": "poc"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-23T02:22:42.341874Z"}}}], "references": [{"url": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4", "tags": ["exploit"]}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-06-23T02:23:08.780Z"}}], "cna": {"title": "ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract", "source": {"advisory": "GHSA-7wh6-2vcc-gcm4", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}}], "affected": [{"vendor": "sysown", "product": "proxysql", "versions": [{"status": "affected", "version": ">= 3.0.6, < 3.0.9"}]}], "references": [{"url": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4", "name": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/sysown/proxysql/commit/e32b7fd50c7c234ea628e392e621e09a2a919e08", "name": "https://github.com/sysown/proxysql/commit/e32b7fd50c7c234ea628e392e621e09a2a919e08", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 3.0.0 through 3.0.8, ProxySQL's GenAI/MCP `run_sql_readonly` tool violates its documented read-only contract for MySQL targets. The tool validates only the full input string with a substring blacklist and first-keyword allowlist, but then executes the entire SQL string on a backend connection created with `CLIENT_MULTI_STATEMENTS`. As a result, a caller can submit a read-only first statement followed by a side-effecting second statement, such as `SELECT 1; RENAME TABLE ...`. The validator accepts the payload because it starts with `SELECT` and because side-effecting MySQL statements such as `RENAME TABLE`, `SET`, `RESET`, `LOCK TABLES`, and `KILL` are not rejected by the blacklist. In a live MCP runtime test, the `/mcp/query` endpoint accepted a `run_sql_readonly` request. The MCP response reported success for the first `SELECT`, and direct backend verification showed that the table had actually been renamed. This violates the endpoint's read-only security contract and lets an MCP caller perform backend writes or administrative SQL, limited by the configured MCP target account's database privileges. Version 3.0.9 contains a fix. Other operator mitigations include: keeping MCP disabled unless required; setting a non-empty `mcp-query_endpoint_auth` token before exposing `/mcp/query`; restricting MCP listener network exposure; configuring MCP backend target credentials as database-level read-only users; and adding temporary MCP query rules to block obvious multi-statement patterns."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-20", "description": "CWE-20: Improper Input Validation"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-19T19:34:39.971Z"}}}, "cveMetadata": {"cveId": "CVE-2026-48774", "state": "PUBLISHED", "dateUpdated": "2026-06-23T02:23:14.975Z", "dateReserved": "2026-05-22T19:39:05.357Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-06-19T19:34:39.971Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "proxysql", "vendor": "sysown", "versions": [{"status": "affected", "version": ">= 3.0.6, < 3.0.9"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:proxysql:proxysql:*:*:*:*:*:*:*:*", "matchCriteriaId": "9277D3D6-2B42-4AB7-AFB4-66D111F1404D", "versionEndExcluding": "4.0.9", "versionStartIncluding": "4.0.6", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 3.0.0 through 3.0.8, ProxySQL's GenAI/MCP `run_sql_readonly` tool violates its documented read-only contract for MySQL targets. The tool validates only the full input string with a substring blacklist and first-keyword allowlist, but then executes the entire SQL string on a backend connection created with `CLIENT_MULTI_STATEMENTS`. As a result, a caller can submit a read-only first statement followed by a side-effecting second statement, such as `SELECT 1; RENAME TABLE ...`. The validator accepts the payload because it starts with `SELECT` and because side-effecting MySQL statements such as `RENAME TABLE`, `SET`, `RESET`, `LOCK TABLES`, and `KILL` are not rejected by the blacklist. In a live MCP runtime test, the `/mcp/query` endpoint accepted a `run_sql_readonly` request. The MCP response reported success for the first `SELECT`, and direct backend verification showed that the table had actually been renamed. This violates the endpoint's read-only security contract and lets an MCP caller perform backend writes or administrative SQL, limited by the configured MCP target account's database privileges. Version 3.0.9 contains a fix. Other operator mitigations include: keeping MCP disabled unless required; setting a non-empty `mcp-query_endpoint_auth` token before exposing `/mcp/query`; restricting MCP listener network exposure; configuring MCP backend target credentials as database-level read-only users; and adding temporary MCP query rules to block obvious multi-statement patterns."}, {"lang": "es", "value": "ProxySQL es un proxy para MySQL y sus bifurcaciones, as\u00ed como PostgreSQL. En las versiones 3.0.0 a 3.0.8, la herramienta \u201crun_sql_readonly\u201d de GenAI/MCP de ProxySQL viola su contrato de solo lectura documentado para objetivos de MySQL. La herramienta valida solo la cadena de entrada completa con una lista negra de subcadenas y una lista blanca de la primera palabra clave, pero luego ejecuta la cadena SQL completa en una conexi\u00f3n de backend creada con \u201cCLIENT_MULTI_STATEMENTS\u201d. Como resultado, un llamador puede enviar una primera declaraci\u00f3n de solo lectura seguida de una segunda declaraci\u00f3n con efectos secundarios, como \u201cSELECT 1; RENAME TABLE ...\u201d. El validador acepta la carga \u00fatil porque comienza con \u201cSELECT\u201d y porque las declaraciones de MySQL con efectos secundarios como \u201cRENAME TABLE\u201d, \u201cSET\u201d, \u201cRESET\u201d, \u201cLOCK TABLES\u201d y \u201cKILL\u201d no son rechazadas por la lista negra. En una prueba de tiempo de ejecuci\u00f3n de MCP en vivo, el endpoint \u201c/mcp/query\u201d acept\u00f3 una solicitud \u201crun_sql_readonly\u201d. La respuesta de MCP inform\u00f3 \u00e9xito para el primer \u201cSELECT\u201d, y la verificaci\u00f3n directa del backend mostr\u00f3 que la tabla hab\u00eda sido realmente renombrada. Esto viola el contrato de seguridad de solo lectura del endpoint y permite a un llamador de MCP realizar escrituras en el backend o SQL administrativo, limitado por los privilegios de base de datos de la cuenta objetivo de MCP configurada. La versi\u00f3n 3.0.9 contiene una correcci\u00f3n. Otras mitigaciones del operador incluyen: mantener MCP deshabilitado a menos que sea necesario; establecer un token \u201cmcp-query_endpoint_auth\u201d no vac\u00edo antes de exponer \u201c/mcp/query\u201d; restringir la exposici\u00f3n de red del oyente de MCP; configurar las credenciales del objetivo de backend de MCP como usuarios de solo lectura a nivel de base de datos; y a\u00f1adir reglas de consulta de MCP temporales para bloquear patrones obvios de m\u00faltiples declaraciones."}], "id": "CVE-2026-48774", "lastModified": "2026-10-25T23:10:00.167", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-48774", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-06-23T02:22:42.341874Z", "version": "2.0.3"}}]}, "published": "2026-06-19T20:16:18.087", "references": [{"source": "security-advisories@github.com", "tags": ["Patch"], "url": "https://github.com/sysown/proxysql/commit/e32b7fd50c7c234ea628e392e621e09a2a919e08"}, {"source": "security-advisories@github.com", "tags": ["Exploit", "Mitigation", "Vendor Advisory"], "url": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4"}, {"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "tags": ["Exploit", "Mitigation", "Vendor Advisory"], "url": "https://github.com/sysown/proxysql/security/advisories/GHSA-7wh6-2vcc-gcm4"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-20"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[3.0.6,3.0.9)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "cna", "scores": [{"score": 100.0, "source": "cna"}]}, "original": {"product": "proxysql", "source": "cna", "vendor": "sysown"}, "product": "proxysql", "vendor": "sysown"}], "created": "2026-06-19T21:30:17.792876+00:00", "updated": "2026-06-20T22:34:30.392589+00:00", "vendors": ["sysown", "sysown$PRODUCT$proxysql"]}