CVE-2026-48772

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-48772", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-05-22T19:39:05.357Z", "datePublished": "2026-06-19T19:28:46.248Z", "dateUpdated": "2026-06-22T15:16:33.852Z"}, "containers": {"cna": {"title": "ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL", "problemTypes": [{"descriptions": [{"cweId": "CWE-348", "lang": "en", "description": "CWE-348: Use of Less Trusted Source", "type": "CWE"}]}, {"descriptions": [{"cweId": "CWE-863", "lang": "en", "description": "CWE-863: Incorrect Authorization", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 10, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2"}, {"name": "https://github.com/sysown/proxysql/releases/tag/v3.0.9", "tags": ["x_refsource_MISC"], "url": "https://github.com/sysown/proxysql/releases/tag/v3.0.9"}], "affected": [{"vendor": "sysown", "product": "proxysql", "versions": [{"version": ">= 2.0.0, < 3.0.9", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-19T19:28:46.248Z"}, "descriptions": [{"lang": "en", "value": "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 <addr> <addr> <port> <port>\\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."}], "source": {"advisory": "GHSA-gw94-85m2-x8v2", "discovery": "UNKNOWN"}}, "adp": [{"references": [{"url": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2", "tags": ["exploit"]}], "metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-06-22T15:15:18.320420Z", "id": "CVE-2026-48772", "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-22T15:16:33.852Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"cna": {"title": "ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL", "source": {"advisory": "GHSA-gw94-85m2-x8v2", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "CHANGED", "version": "3.1", "baseScore": 10, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}}], "affected": [{"vendor": "sysown", "product": "proxysql", "versions": [{"status": "affected", "version": ">= 2.0.0, < 3.0.9"}]}], "references": [{"url": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2", "name": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/sysown/proxysql/releases/tag/v3.0.9", "name": "https://github.com/sysown/proxysql/releases/tag/v3.0.9", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "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 <addr> <addr> <port> <port>\\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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-348", "description": "CWE-348: Use of Less Trusted Source"}]}, {"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-863", "description": "CWE-863: Incorrect Authorization"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-19T19:28:46.248Z"}}, "adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-48772", "role": "CISA Coordinator", "options": [{"Exploitation": "poc"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-22T15:15:18.320420Z"}}}], "references": [{"url": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2", "tags": ["exploit"]}], "providerMetadata": {"shortName": "CISA-ADP", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "dateUpdated": "2026-06-22T15:14:59.723Z"}}]}, "cveMetadata": {"cveId": "CVE-2026-48772", "state": "PUBLISHED", "dateUpdated": "2026-06-19T19:28:46.248Z", "dateReserved": "2026-05-22T19:39:05.357Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-06-19T19:28:46.248Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "proxysql", "vendor": "sysown", "versions": [{"status": "affected", "version": ">= 2.0.0, < 3.0.9"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:proxysql:proxysql:*:*:*:*:*:*:*:*", "matchCriteriaId": "B4CAF149-E318-46D2-AFFB-E9D9A57B081E", "versionEndExcluding": "3.0.9", "versionStartIncluding": "2.0.0", "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 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the `PROXY UNKNOWN <addr> <addr> <port> <port>\\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."}, {"lang": "es", "value": "ProxySQL es un proxy para MySQL y sus bifurcaciones, as\u00ed como para PostgreSQL. En las versiones 2.0.0 a 3.0.8, el frontend MySQL de ProxySQL acepta la trama PP1 \u2019PROXY UNKNOWN [addr] [addr] [port] [port]\\r\\n\u2019 como una cabecera de protocolo PROXY bien formada. La especificaci\u00f3n del protocolo PROXY v1 de HAProxy establece que cuando el token del protocolo es \u2019UNKNOWN\u2019, el receptor DEBE ignorar cualquier campo de direcci\u00f3n que le siga, porque el proxy ha declarado que no puede determinar la identidad del cliente. ProxySQL analiza esos campos de direcci\u00f3n de todos modos a trav\u00e9s de \u2019sscanf\u2019 y escribe la direcci\u00f3n de origen falsificada en el campo \u2019addr.addr\u2019 de la sesi\u00f3n. Desde all\u00ed fluye directamente al comparador de reglas de consulta, donde el predicado \u2019client_addr\u2019 decide el enrutamiento y la ACL. Cuando \u2019mysql-proxy_protocol_networks = \u2019*\u2019\u2019 (el valor predeterminado), cualquier par TCP puede enviar una trama PP1 y elegir cualquier declaraci\u00f3n de IP de origen. Con eso, cualquier fila de \u2019mysql_query_rules\u2019 fijada a un valor de \u2019client_addr\u2019 es falsificable: el atacante escribe la direcci\u00f3n que quiere que coincida en la l\u00ednea PP1, y ProxySQL enruta su consulta como si viniera de esa direcci\u00f3n. En la pr\u00e1ctica, esto es un bypass de enrutamiento y ACL. Las implementaciones reales usan \u2019client_addr\u2019 para la divisi\u00f3n de lectura-escritura (las aplicaciones internas van al primario, el tr\u00e1fico p\u00fablico a las r\u00e9plicas de lectura), la fijaci\u00f3n de esquema por aplicaci\u00f3n y las reglas de filtro de consulta (DDL permitido solo desde CIDR de administrador, consultas p\u00fablicas bloqueadas de patrones peligrosos). Un atacante que puede alcanzar el puerto del frontend puede falsificar su camino hacia cualquiera de esas rutas. La versi\u00f3n 3.0.9 parchea este problema."}], "id": "CVE-2026-48772", "lastModified": "2026-10-25T23:10:00.167", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 10.0, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 5.8, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-48772", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-06-22T15:15:18.320420Z", "version": "2.0.3"}}]}, "published": "2026-06-19T20:16:17.803", "references": [{"source": "security-advisories@github.com", "tags": ["Release Notes"], "url": "https://github.com/sysown/proxysql/releases/tag/v3.0.9"}, {"source": "security-advisories@github.com", "tags": ["Vendor Advisory", "Exploit"], "url": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2"}, {"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "tags": ["Vendor Advisory", "Exploit"], "url": "https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-348"}, {"lang": "en", "value": "CWE-863"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[2.0.0,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-19T22:00:07.291848+00:00", "updated": "2026-06-20T22:34:31.951140+00:00", "vendors": ["sysown", "sysown$PRODUCT$proxysql"]}