Apache Superset SQLLab Flaw Bypasses Read-Only Validation, Exposing Postgres Databases to Unauthorized Writes

A critical authorization weakness in Apache Superset enables users with SQLLab access to bypass read-only query safeguards on Postgres analytic databases. The vulnerability stems from improper validation logic that misidentifies specially crafted SQL DML statements as read-only operations, permitting their execution against database configurations that should block write actions.

The issue is limited to Postgres connections used for analytics—connections using other database systems or Postgres with a dedicated readonly user account remain unaffected. An attacker must already possess valid SQLLab credentials to exploit this flaw. Versions of Superset prior to 4.1.0 are exposed; the vulnerability was addressed in the 4.1.0 release.

Security researchers note that this flaw raises significant concerns for organizations relying on Superset's permission model to isolate analytical workloads. While exploitation requires authenticated access, the ability to circumvent read-only enforcement could allow a compromised or malicious SQLLab user to modify data or schemas in environments where such access should be blocked. The discovery adds to a pattern of query validation vulnerabilities in data visualization platforms, highlighting the complexity of enforcing access controls across diverse database backends. Organizations running older Superset versions should upgrade to 4.1.0 or apply compensating controls such as restricting SQLLab access and using readonly database credentials where feasible.