CriticalCVE-2026-48772

Sysown Proxysql: Use of Less Trusted Source (CVE-2026-48772)

Published 19.06.2026Last modified 25.10.2026Sources: CVE.org, OSV

Public exploit

What is affected, what to do

An exploit is publicly available. Update proxysql to version 3.0.9.

Affected: Sysown Proxysql gte 2.0.0, < 3.0.9..*

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

10.0

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: NVD, CVSS v3

10.0

CVSS v3

Severity Critical on the scale from 0 to 10.

Source: CVE.org, OSV

0.2 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 13.6

Show all metrics

Severity: Critical
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 70.69 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: PoC (publicly reported)
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 10.0 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 10.0
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.2 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 13.6; Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 19.06.2026
CISA assessment (SSVC): Exploitation: proof of concept · automatable · Technical impact: partial; Source: CISA Vulnrichment, as of 22 June 2026
CWE CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect. Read in glossary: CWE-348, CWE-863

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

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 <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: NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5, CVE.org (MITRE)

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
sysown	proxysql	`≥ 2.0.0, < 3.0.9`	—
proxysql	proxysql	`2.0.0 – < 3.0.9`	`3.0.9`

Distribution and container packages (1)

Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

Distribution and container packages
		Affected versions	Fixed in
bitnami	proxysql	`2.0.0`	—

Vendors and products

Weakness classes (CWE)

CWE-348Use of Less Trusted Source
Base
The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.
Entry at MITRE CWE-348
CWE-863Incorrect Authorization
Class
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Entry at MITRE CWE-863

Public exploit references

Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

Public exploit references

Reference tagged as exploit	github.com (opens in a new tab)	PoC (publicly reported)reported, not verified	—

References & sources

github.comsysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2x_refsource_CONFIRM, Vendor advisory, Exploit
github.comsysown/proxysql/releases/tag/v3.0.9x_refsource_MISC, Release notes
NVD (NIST)vuln/detail/CVE-2026-48772web

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

10.08.2026Initial analysis by NVDNVD

Newly listed as affected:

ProxySQL (2.0.0 – before 3.0.9)

New references:

Show 4 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Product configuration	added	—	OR cpe:2.3:a:proxysql:proxysql::::::::* versions from (including) 2.0.0 up to (excluding) 3.0.9
Reference type	added	—	GitHub, Inc.: https://github.com/sysown/proxysql/releases/tag/v3.0.9 Types: Release Notes
Reference type	added	—	GitHub, Inc.: https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2 Types: Exploit, Vendor Advisory
Reference type	added	—	CISA-ADP: https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2 Types: Exploit, Vendor Advisory

Source identifier: nvd@nist.gov

19.06.2026ReceivedGitHub

CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Weakness type: CWE-348, CWE-863

Description added or changed

New references:

Show 7 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Affected versions (publisher)	added	—	proxysql
Description	added	—	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.
CVSS	added	—	AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Weakness type (CWE)	added	—	CWE-348
Weakness type (CWE)	added	—	CWE-863
Reference	added	—	https://github.com/sysown/proxysql/releases/tag/v3.0.9
Reference	added	—	https://github.com/sysown/proxysql/security/advisories/GHSA-gw94-85m2-x8v2

Source identifier: security-advisories@github.com

One NVD translation into another language is hidden.

Linked advisories

@RISK®: The Consensus Security Vulnerability Alert: Vol. 26, Num. 25SANS @RISK25.06.2026

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2026-48772"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-48772.svg?lang=en" alt="CVE-2026-48772 – NEOSEC Intel" height="20"></a>