VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

apache-superset: vulnerability history, versions and safety

apache-superset is a package in the PyPI ecosystem. Vulert records 137 vulnerabilities for it across 83 releases, from Dec 2019 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
137 vulnerabilities recorded C3 H16 M50 L2 U66
i
16 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
58 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all apache-superset vulnerabilities

Vulert verdict on apache-superset 6.1.0 i

Updated on 23 Oct 2026

Careful: 6.1.0 has 16 known vulnerabilities, and 16 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 36/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.1.0 — affected i
  • Vulnerabilities on record 137 over 6 years · 58 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 16 i
  • Depended on by 3 packages i
  • Last release 5 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for apache-superset, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.1.0 13 May 2026 H1 M14 U1 non-standard No Details →
6.1.0rc3 01 May 2026 H1 M14 U1 non-standard No Details →
6.1.0rc2 17 Apr 2026 H1 M14 U1 non-standard No Details →
6.1.0rc1 11 Mar 2026 H1 M14 U1 non-standard No Details →
6.0.1rc1 05 Feb 2026 H1 M14 U1 non-standard No Details →
6.0.0 18 Dec 2025 H1 M14 U1 non-standard No Details →
6.0.0rc4 04 Dec 2025 H2 M1 L1 U4 non-standard Yes Details →
6.0.0rc3 20 Nov 2025 H2 M1 L1 U4 non-standard Yes Details →
6.0.0rc2 22 Sep 2025 H2 M1 L1 U4 non-standard Yes Details →
4.1.4 28 Aug 2025 H2 M1 L1 U7 non-standard Yes Details →
4.1.4rc1 23 Aug 2025 H2 M1 L1 U7 non-standard Yes Details →
6.0.0rc1 18 Aug 2025 H2 M1 L1 U4 non-standard Yes Details →
4.1.3.post1 17 Jul 2025 H2 M4 L1 U7 non-standard Yes Details →
4.1.3rc2 27 Jun 2025 H2 M5 L1 U8 non-standard Yes Details →
5.0.0 23 Jun 2025 H2 M1 L1 U4 non-standard Yes Details →
5.0.0rc4 18 Jun 2025 H2 M4 L1 U7 non-standard Yes Details →
5.0.0rc3 29 May 2025 H2 M4 L1 U7 non-standard Yes Details →
4.1.3rc1 06 May 2025 H2 M5 L1 U8 non-standard Yes Details →
5.0.0rc2 01 Apr 2025 H2 M4 L1 U7 non-standard Yes Details →
4.1.2 24 Mar 2025 H2 M5 L1 U8 non-standard Yes Details →
4.1.2rc1 13 Mar 2025 H3 M7 L1 U11 non-standard Yes Details →
5.0.0rc1 04 Feb 2025 H2 M4 L1 U7 non-standard Yes Details →
4.1.1 20 Nov 2024 H3 M7 L1 U11 non-standard Yes Details →
4.1.1rc1 16 Nov 2024 H3 M7 L1 U11 non-standard Yes Details →
4.1.0 13 Nov 2024 H3 M7 L1 U11 non-standard Yes Details →
4.1.0rc4 02 Nov 2024 H5 M8 L2 U15 non-standard Yes Details →
4.1.0rc3 16 Oct 2024 H5 M8 L2 U15 non-standard Yes Details →
4.1.0rc2 26 Aug 2024 H5 M8 L2 U15 non-standard Yes Details →
4.0.2 02 Jul 2024 H5 M8 L2 U15 Apache-2.0 Yes Details →
4.0.1 13 May 2024 H5 M9 L2 U16 Apache-2.0 Yes Details →
3.1.3 09 May 2024 H5 M9 L2 U16 Apache-2.0 Yes Details →
4.0.0 08 Apr 2024 H5 M9 L2 U17 Apache-2.0 Yes Details →
3.1.2 03 Apr 2024 H5 M10 L2 U17 Apache-2.0 Yes Details →
4.0.0rc2 02 Apr 2024 H5 M9 L2 U16 Apache-2.0 Yes Details →
4.0.0rc1 20 Feb 2024 H5 M9 L2 U16 Apache-2.0 Yes Details →
3.1.1 20 Feb 2024 H5 M11 L2 U18 Apache-2.0 Yes Details →
3.0.4 20 Feb 2024 H5 M11 L2 U19 Apache-2.0 Yes Details →
3.1.0 18 Jan 2024 H5 M11 L2 U23 Apache-2.0 Yes Details →
3.0.3 17 Jan 2024 H5 M16 L2 U24 Apache-2.0 Yes Details →
3.1.0rc4 09 Jan 2024 H5 M11 L2 U18 Apache-2.0 Yes Details →
3.1.0rc3 18 Dec 2023 H5 M11 L2 U18 Apache-2.0 Yes Details →
2.1.3 16 Dec 2023 C1 H5 M19 L2 U27 Apache-2.0 Yes Details →
3.1.0rc2 11 Dec 2023 H5 M11 L2 U18 Apache-2.0 Yes Details →
3.1.0rc1 28 Nov 2023 H5 M11 L2 U18 Apache-2.0 Yes Details →
2.1.2 23 Nov 2023 C1 H6 M20 L2 U29 Apache-2.0 Yes Details →
3.0.2 22 Nov 2023 C1 H5 M16 L2 U25 Apache-2.0 Yes Details →
3.0.1 18 Oct 2023 C1 H5 M16 L2 U27 Apache-2.0 Yes Details →
3.0.0 18 Sep 2023 C1 H5 M16 L2 U27 Apache-2.0 Yes Details →
3.0.0rc4 13 Sep 2023 C1 H5 M19 L2 U27 Apache-2.0 Yes Details →
2.1.1 29 Aug 2023 C1 H7 M25 L2 U33 Apache-2.0 Yes Details →
3.0.0rc3 24 Aug 2023 C1 H5 M19 L2 U27 Apache-2.0 Yes Details →
2.1.1rc3 18 Aug 2023 C1 H7 M26 L2 U40 Apache-2.0 Yes Details →
3.0.0rc2 27 Jul 2023 C1 H5 M19 L2 U27 Apache-2.0 Yes Details →
2.1.1rc2 24 Jul 2023 C1 H7 M26 L2 U40 Apache-2.0 Yes Details →
3.0.0rc1 03 Jul 2023 C1 H5 M19 L2 U27 Apache-2.0 Yes Details →
2.1.1rc1 16 Jun 2023 C1 H7 M26 L2 U40 Apache-2.0 Yes Details →
2.1.0 05 Apr 2023 C1 H7 M33 L2 U41 Apache-2.0 No Details →
1.5.3 13 Jan 2023 C1 H7 M36 L2 U44 Apache-2.0 No Details →
2.0.1 20 Dec 2022 C1 H8 M36 L2 U45 Apache-2.0 No Details →
1.5.2 27 Sep 2022 C1 H8 M42 L2 U51 Apache-2.0 No Details →
2.0.0 14 Jul 2022 C1 H8 M36 L2 U52 Apache-2.0 No Details →
1.5.1 08 Jun 2022 C1 H8 M42 L2 U51 Apache-2.0 No Details →
1.5.0 28 Apr 2022 C1 H8 M43 L2 U52 Apache-2.0 No Details →
1.4.2 29 Mar 2022 C1 H8 M42 L2 U51 Apache-2.0 No Details →
1.4.1 09 Feb 2022 C3 H8 M42 L2 U52 Apache-2.0 No Details →
1.4.0 19 Jan 2022 C3 H8 M42 L2 U52 Apache-2.0 No Details →
1.3.2 20 Oct 2021 C3 H9 M42 L2 U53 Apache-2.0 No Details →
1.3.1 28 Sep 2021 C3 H11 M42 L2 U55 Apache-2.0 No Details →
1.3.0 21 Aug 2021 C3 H13 M42 L2 U56 Apache-2.0 No Details →
1.2.0 02 Jul 2021 C3 H13 M41 L2 U55 Apache-2.0 No Details →
1.1.0 13 Apr 2021 C3 H13 M43 L2 U56 Apache-2.0 No Details →
0.38.1 01 Mar 2021 C3 H13 M43 L2 U57 Apache-2.0 No Details →
1.0.1 06 Feb 2021 C3 H13 M43 L2 U57 Apache-2.0 No Details →
1.0.0 21 Jan 2021 C3 H13 M43 L2 U57 Apache-2.0 No Details →
0.38.0 24 Nov 2020 C3 H13 M45 L2 U58 Apache-2.0 No Details →
0.37.2 27 Sep 2020 C3 H13 M45 L2 U58 Apache-2.0 No Details →
0.37.1 15 Sep 2020 C3 H14 M45 L2 U59 Apache-2.0 No Details →
0.37.0 14 Aug 2020 C3 H15 M45 L2 U60 Apache-2.0 No Details →
0.36.0 17 Apr 2020 C3 H15 M45 L2 U60 Apache-2.0 No Details →
0.35.2 15 Jan 2020 C3 H15 M45 L2 U60 Apache-2.0 No Details →
0.35.1 26 Nov 2019 C3 H15 M46 L2 U61 Apache-2.0 No Details →
0.34.1 12 Oct 2019 C3 H15 M46 L2 U61 Apache-2.0 No Details →
0.34.0 18 Sep 2019 C3 H15 M46 L2 U61 Apache-2.0 No Details →

All 83 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2020 6
  • 2021 7
  • 2022 15
  • 2023 29
  • 2024 14
  • 2025 6
  • 2026 58

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 58 of the 137 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for apache-superset

The 5 most severe of 137 vulnerabilities recorded for this package

Search all 137 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-53947: Apache Superset SQL Injection Vulnerability Due to Improper Authorization Checks 9.8 critical 4.1.0 07 Jul 2026
CVE-2022-27479: SQL Injection in Apache Superset 9.8 critical 1.4.2 14 Apr 2022
CVE-2024-53947: Apache Superset SQL Injection Vulnerability Due to Improper Authorization 9.8 low 4.1.0 09 Dec 2024
CVE-2022-27479: SQL injection in apache-superset 9.8 critical 1.4.2 14 Apr 2022
CVE-2023-49657: Apache Superset Stored XSS Vulnerability 9.6 critical 3.0.3 29 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About apache-superset

Is apache-superset safe to use?

Vulert records 137 vulnerabilities for apache-superset in PyPI: 3 critical, 16 high, 50 medium and 2 low, plus 66 not yet rated. 16 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is apache-superset's Vulert package health score?

Vulert scores apache-superset 36/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of apache-superset affected?

Yes. 6.1.0, the version you would install today, has 16 known vulnerabilities, and 16 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of apache-superset should I use?

6.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does apache-superset have?

137 vulnerabilities are recorded for apache-superset in the PyPI ecosystem: 3 critical, 16 high, 50 medium and 2 low, plus 66 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new apache-superset vulnerabilities disclosed?

58 vulnerabilities were recorded for apache-superset in the last 12 months, and the oldest entry in this database dates to 16 Dec 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of apache-superset are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor apache-superset for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the apache-superset version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.