{"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-48772 exists.","fix":"Upgrade proxysql to 3.0.9 or later.","what":"CVE-2026-48772 is a critical authentication bypass 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-48772 and fix it if it is affected.\n\nWhat it is: CVE-2026-48772 is a critical authentication bypass 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-48772 exists.\n\nAffected packages and fixed versions:\n- proxysql (Bitnami): affected from 2.0.0; 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-48772/ (Markdown: https://insights.sbomify.com/CVE-2026-48772/index.md)","id":"CVE-2026-48772","markdown":"https://insights.sbomify.com/CVE-2026-48772/index.md","name":"CVE-2026-48772","record":{"aliases":["BIT-proxysql-2026-48772","GHSA-gw94-85m2-x8v2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL proxy server","requires_auth":"none","summary":"Attackers can spoof source IPs via PROXY protocol headers to bypass client address-based access controls and routing rules in ProxySQL.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"proxysql","vendor":"proxysql"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the `PROXY UNKNOWN \u003caddr\u003e \u003caddr\u003e \u003cport\u003e \u003cport\u003e\\r\\n` PP1 frame as a well-formed PROXY protocol header. The HAProxy PROXY protocol v1 specification says that when the protocol token is `UNKNOWN`, the receiver MUST ignore any address fields that follow it, because the proxy has declared it cannot determine the client identity. ProxySQL parses those address fields anyway via `sscanf` and writes the spoofed source address into the session's `addr.addr` field. From there it flows directly into the query-rule matcher, where the `client_addr` predicate decides routing and ACL. When `mysql-proxy_protocol_networks = '*'` (the default), any TCP peer can send a PP1 frame and choose any source IP claim. With that, any `mysql_query_rules` row pinned to a `client_addr` value is forgeable: the attacker writes the address they want to match into the PP1 line, and ProxySQL routes their query as if it came from that address. In practice this is a routing and ACL bypass. Real deployments use `client_addr` for read-write splitting (internal apps go to the primary, public traffic to read replicas), per-app schema pinning, and query-filter rules (DDL allowed only from admin CIDR, public queries blocked from dangerous patterns). An attacker that can reach the frontend port can forge their way into any of those routes. Version 3.0.9 patches this 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: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL","id":"CVE-2026-48772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"ProxySQL pre-auth heap overflow in MySQL and PostgreSQL first-packet handling","id":"CVE-2026-48773"},"packages":[{"ecosystem":"Bitnami","fixed":["3.0.9"],"introduced":["2.0.0"],"last_affected":[],"package":"proxysql","purl":"pkg:bitnami/proxysql","source":"BIT-proxysql-2026-48772"}],"prev":{"headline":"ishankportfolio: Stored Contact Form Submission Exposure via Public Client-Side Database Configuration","id":"CVE-2026-48771"},"products":["proxysql"],"published":"2026-06-19","related":[{"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"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["sysown"]},"summary":"Attackers can spoof source IPs via PROXY protocol headers to bypass client address-based access controls and routing rules in ProxySQL.","url":"https://insights.sbomify.com/CVE-2026-48772/"}