{"answers":{"affected":"1 open source package ship an affected version, including proxysql. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48774 exists.","fix":"Upgrade proxysql to 3.0.9 or later.","what":"CVE-2026-48774 is a high-severity vulnerability in sysown proxysql, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48774 and fix it if it is affected.\n\nWhat it is: CVE-2026-48774 is a high-severity vulnerability in sysown proxysql, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48774 exists.\n\nAffected packages and fixed versions:\n- proxysql (Bitnami): affected from 3.0.6; fixed in 3.0.9\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48774/ (Markdown: https://insights.sbomify.com/CVE-2026-48774/index.md)","id":"CVE-2026-48774","markdown":"https://insights.sbomify.com/CVE-2026-48774/index.md","name":"CVE-2026-48774","record":{"aliases":["BIT-proxysql-2026-48774","GHSA-7wh6-2vcc-gcm4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"MySQL proxy","requires_auth":"none","summary":"ProxySQL's MCP read-only tool allows side-effecting SQL via multi-statements, enabling unauthorized database modifications if MCP is enabled.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"proxysql","vendor":"proxysql"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract","id":"CVE-2026-48774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading","id":"CVE-2026-48775"},"packages":[{"ecosystem":"Bitnami","fixed":["3.0.9"],"introduced":["3.0.6"],"last_affected":[],"package":"proxysql","purl":"pkg:bitnami/proxysql","source":"BIT-proxysql-2026-48774"}],"prev":{"headline":"ProxySQL pre-auth heap overflow in MySQL and PostgreSQL first-packet handling","id":"CVE-2026-48773"},"products":["proxysql"],"published":"2026-06-19","related":[{"cvss_score":10,"headline":"ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL","id":"CVE-2026-48772","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":9.8,"headline":"ProxySQL pre-auth heap overflow in MySQL and PostgreSQL first-packet handling","id":"CVE-2026-48773","kev_date_added":null,"published":"2026-06-19"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["sysown"]},"summary":"ProxySQL's MCP read-only tool allows side-effecting SQL via multi-statements, enabling unauthorized database modifications if MCP is enabled.","url":"https://insights.sbomify.com/CVE-2026-48774/"}