CVE-2026-48772
published 2026-06-19CVE-2026-48772: 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…
PriorityP358critical10CVSS 3.1
AVNACLPRNUINSCCHIHAN
EPSS
0.18%
8.3th percentile
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 \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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| sysown | proxysql | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header [epel-all]
bugzilla·2026-06-22·CVSS 10.0
CVE-2026-48772 [CRITICAL] CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header [epel-all]
CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header [epel-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header [fedora-all]
bugzilla·2026-06-22·CVSS 10.0
CVE-2026-48772 [CRITICAL] CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header [fedora-all]
CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header
bugzilla·2026-06-19·CVSS 10.0
CVE-2026-48772 [CRITICAL] CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header
CVE-2026-48772 proxysql: ProxySQL: Routing and Access Control List bypass via spoofed PROXY protocol header
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 \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
2026-06-19
Published