# Apache Superset: Read-Only Bypass via Improper Input Validation on PostgreSQL Connections

Advisory record · `GHSA-mwf2-qr4v-94h2`

- **Identifiers:** `GHSA-mwf2-qr4v-94h2` · `BIT-superset-2026-23984` · `CVE-2026-23984` · `PYSEC-2026-2376`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 24 Feb 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Feb 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-superset` (PyPI): affected `<6.0.0`; fixed in `6.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Superset versions before 6.0.0 are vulnerable. An authenticated user with SQL Lab access can bypass the read-only check on PostgreSQL database connections by using specially crafted SQL statements, which lets them run data-modifying (DML) statements such as INSERT, UPDATE or DELETE. Upgrade to Apache Superset 6.0.0 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0041, the 35th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mwf2-qr4v-94h2)

## Sources

- [GitHub Advisory Database: GHSA-mwf2-qr4v-94h2](https://github.com/advisories/GHSA-mwf2-qr4v-94h2)
- [OSV: GHSA-mwf2-qr4v-94h2](https://osv.dev/vulnerability/GHSA-mwf2-qr4v-94h2)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-23984>
- <https://github.com/apache/superset>
- <https://lists.apache.org/thread/72cmgxtvp9pclto4ln1chbs1227nwd26>
- <http://www.openwall.com/lists/oss-security/2026/02/24/8>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mwf2-qr4v-94h2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mwf2-qr4v-94h2/>. Everything for agents: <https://agentprime.io/llms.txt>.
