How severe is GHSA-9g5x-mm39-wg9r?

No CVSS score has been assigned to GHSA-9g5x-mm39-wg9r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9g5x-mm39-wg9r?

GHSA-9g5x-mm39-wg9r affects the following packages: apache-superset (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-9g5x-mm39-wg9r?

Update apache-superset to 4.1.3.post1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g5x-mm39-wg9r is resolved across your whole dependency graph.

How do I detect GHSA-9g5x-mm39-wg9r in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-superset, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9g5x-mm39-wg9r if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-9g5x-mm39-wg9r actively exploited in the wild?

No public exploit code has been indexed for GHSA-9g5x-mm39-wg9r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9g5x-mm39-wg9r?

GHSA-9g5x-mm39-wg9r has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9g5x-mm39-wg9r?

GHSA-9g5x-mm39-wg9r is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9g5x-mm39-wg9r published, and has it been updated?

GHSA-9g5x-mm39-wg9r was published on August 14, 2025 and was last updated on August 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Apache Superset data query improperly discloses…

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9g5x-mm39-wg9r.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍apache-superset

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

When a guest user accesses a chart in Apache Superset, the API response from the /chart/data endpoint includes a query field in its payload. This field contains the underlying query, which improperly discloses database schema information, such as table names, to the low-privileged guest user.

This issue affects Apache Superset: before 4.1.3.

Users are recommended to upgrade to version 4.1.3, which fixes the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`apache-superset`	all versions	4.1.3.post1`pip install --upgrade 'apache-superset==4.1.3.post1'`

Affected Products

1 product · 1 configurations

Application

supersetapache

< 4.1.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-superset, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apache-superset to 4.1.3.post1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g5x-mm39-wg9r is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

When a guest user accesses a chart in Apache Superset, the API response from the /chart/data endpoint includes a query field in its payload. This field contains the underlying query, which improperly discloses database schema information, such as table names, to the low-privileged guest user. This issue affects Apache Superset: before 4.1.3. Users are recommended to upgrade to version 4.1.3, which fixes the issue.

O3 Security · Impact-Aware SCA

Is GHSA-9g5x-mm39-wg9r in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

Apache Superset data query improperly discloses database schema information to low-privileged guest userGHSA-9g5x-mm39-wg9r