{"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-48773 exists.","fix":"Upgrade proxysql to 3.0.9 or later.","what":"CVE-2026-48773 is a critical memory corruption 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-48773 and fix it if it is affected.\n\nWhat it is: CVE-2026-48773 is a critical memory corruption 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-48773 exists.\n\nAffected packages and fixed versions:\n- proxysql (Bitnami): affected from 2.0.18; 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-48773/ (Markdown: https://insights.sbomify.com/CVE-2026-48773/index.md)","id":"CVE-2026-48773","markdown":"https://insights.sbomify.com/CVE-2026-48773/index.md","name":"CVE-2026-48773","record":{"aliases":["BIT-proxysql-2026-48773","GHSA-58ww-865x-grpr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Database proxy","requires_auth":"none","summary":"Remote unauthenticated attackers can trigger heap memory corruption in ProxySQL via oversized first packets, potentially leading to code execution or service disruption.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"proxysql","vendor":"proxysql"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. Versions 2.0.18 through 3.0.8 have a pre-authentication heap memory corruption vulnerability in the MySQL and PostgreSQL protocol first-read paths. A remote unauthenticated client can declare an oversized first packet length, and ProxySQL passes that attacker-controlled length directly to `recv()` while writing into a fixed 32 KB input queue. Version 3.0.9 patches the issue.","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 pre-auth heap overflow in MySQL and PostgreSQL first-packet handling","id":"CVE-2026-48773","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract","id":"CVE-2026-48774"},"packages":[{"ecosystem":"Bitnami","fixed":["3.0.9"],"introduced":["2.0.18"],"last_affected":[],"package":"proxysql","purl":"pkg:bitnami/proxysql","source":"BIT-proxysql-2026-48773"}],"prev":{"headline":"ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL","id":"CVE-2026-48772"},"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":7.5,"headline":"ProxySQL MCP run_sql_readonly executes side-effecting MySQL multi-statements despite read-only contract","id":"CVE-2026-48774","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":"total"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["sysown"]},"summary":"Remote unauthenticated attackers can trigger heap memory corruption in ProxySQL via oversized first packets, potentially leading to code execution or service disruption.","url":"https://insights.sbomify.com/CVE-2026-48773/"}