Quick answers
- Is CVE-2024-53948 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-53948 being exploited in the wild.
- How severe is CVE-2024-53948?
- Low severity, with a CVSS score of 3.1, published 7 July 2026.
- Which products and versions are affected?
- Apache Superset before 4.1.0; apache-superset (PyPI) ECOSYSTEM:introduced=0,fixed=4.1.0.
- Is there a fix for CVE-2024-53948?
- Yes. apache-superset (PyPI): upgrade to 4.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-53948 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-53948?
- Check whether you run Apache Superset or apache-superset (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- apache-superset (PyPI): upgrade to 4.1.0 or later
pip install "apache-superset>=4.1.0"
Technical details
The vulnerability is a CWE-209 (Generation of Error Message Containing Sensitive Information) issue where Apache Superset exposes analytics database metadata through overly verbose error messages. The vulnerability affects error handling across all versions before 4.1.0 and is exploitable over the network without authentication or user interaction required. An attacker can trigger errors that reveal database schema, table names, and other sensitive metadata. The fix was released in version 4.1.0, which suppresses metadata disclosure in error messages, particularly for embedded dashboards.
Affected products
- Apache Superset before 4.1.0
Identifiers
- CVE-2024-53948
- GHSA-2cx9-54hp-r698
- PYSEC-2026-1154
Timeline
- 2024-12-09: disclosed