VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

dagster: vulnerability history, versions and safety

dagster is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 93 releases, from Jul 2025 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
5 vulnerabilities recorded M2 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 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 dagster vulnerabilities

Vulert verdict on dagster 1.13.26 i

Updated on 23 Oct 2026

Good news: 1.13.26, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 1.13.26 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.13.26 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.13.26 — unaffected i
  • Vulnerabilities on record 5 over 1 year · 3 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Depended on by 200 packages i
  • Stars 16,308 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 dagster, 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
1.13.26 09 Oct 2026 none Apache-2.0 — Details →
1.13.25 01 Oct 2026 none Apache-2.0 — Details →
1.13.24 21 Sep 2026 none Apache-2.0 — Details →
1.13.23 16 Sep 2026 none Apache-2.0 — Details →
1.13.22 11 Sep 2026 none Apache-2.0 — Details →
1.13.21 03 Sep 2026 none Apache-2.0 — Details →
1.13.20 27 Aug 2026 none Apache-2.0 — Details →
1.13.19 21 Aug 2026 none Apache-2.0 — Details →
1.13.18 14 Aug 2026 none Apache-2.0 — Details →
1.13.17 07 Aug 2026 none Apache-2.0 — Details →
1.13.16 30 Jul 2026 none Apache-2.0 — Details →
1.13.15 23 Jul 2026 none Apache-2.0 — Details →
1.13.14 16 Jul 2026 none Apache-2.0 — Details →
1.13.13 09 Jul 2026 none Apache-2.0 — Details →
1.13.12 02 Jul 2026 none Apache-2.0 — Details →
1.13.11 25 Jun 2026 none Apache-2.0 — Details →
1.13.10 18 Jun 2026 none Apache-2.0 — Details →
1.13.9 11 Jun 2026 none Apache-2.0 — Details →
1.13.8 04 Jun 2026 none Apache-2.0 — Details →
1.13.7 28 May 2026 none Apache-2.0 — Details →
1.13.6 22 May 2026 none Apache-2.0 — Details →
1.13.5 15 May 2026 none Apache-2.0 — Details →
1.13.5rc0 15 May 2026 none Apache-2.0 — Details →
1.13.4 07 May 2026 none Apache-2.0 — Details →
1.13.3 30 Apr 2026 none Apache-2.0 — Details →
1.13.2 23 Apr 2026 none Apache-2.0 — Details →
1.13.1 17 Apr 2026 none Apache-2.0 — Details →
1.13.0 09 Apr 2026 U1 Apache-2.0 Yes Details →
1.12.22 02 Apr 2026 U1 Apache-2.0 Yes Details →
1.12.21 26 Mar 2026 U1 Apache-2.0 Yes Details →
1.12.20 19 Mar 2026 U1 Apache-2.0 Yes Details →
1.12.19 12 Mar 2026 U1 Apache-2.0 Yes Details →
1.12.18 05 Mar 2026 U1 Apache-2.0 Yes Details →
1.12.17 27 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.17rc0 26 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.16 26 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.16rc1 26 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.15 20 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.15rc4 20 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.15rc3 20 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.15rc2 20 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.15rc1 19 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.15rc0 19 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.14 05 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.14rc4 05 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.14rc3 05 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.14rc2 05 Feb 2026 U1 Apache-2.0 Yes Details →
1.12.13 30 Jan 2026 U1 Apache-2.0 Yes Details →
1.12.13rc0 30 Jan 2026 U1 Apache-2.0 Yes Details →
1.12.12 22 Jan 2026 U1 Apache-2.0 Yes Details →
1.12.11 15 Jan 2026 U1 Apache-2.0 Yes Details →
1.12.10 09 Jan 2026 U1 Apache-2.0 Yes Details →
1.12.9 08 Jan 2026 U1 Apache-2.0 Yes Details →
1.12.8 29 Dec 2025 U1 Apache-2.0 Yes Details →
1.12.7 19 Dec 2025 U1 Apache-2.0 Yes Details →
1.12.6 11 Dec 2025 U1 Apache-2.0 Yes Details →
1.12.5 09 Dec 2025 U1 Apache-2.0 Yes Details →
1.12.4 04 Dec 2025 U1 Apache-2.0 Yes Details →
1.12.3 20 Nov 2025 U1 Apache-2.0 Yes Details →
1.12.2 13 Nov 2025 U1 Apache-2.0 Yes Details →
1.12.1 07 Nov 2025 U1 Apache-2.0 Yes Details →
1.12.0 30 Oct 2025 U1 Apache-2.0 Yes Details →
1.11.16 23 Oct 2025 U1 Apache-2.0 Yes Details →
1.11.15 16 Oct 2025 U1 Apache-2.0 Yes Details →
1.11.14 09 Oct 2025 U1 Apache-2.0 Yes Details →
1.11.13 02 Oct 2025 U1 Apache-2.0 Yes Details →
1.11.12 25 Sep 2025 U1 Apache-2.0 Yes Details →
1.11.11 18 Sep 2025 U1 Apache-2.0 Yes Details →
1.11.10 11 Sep 2025 U1 Apache-2.0 Yes Details →
1.11.9 04 Sep 2025 U1 Apache-2.0 Yes Details →
1.11.8 28 Aug 2025 U1 Apache-2.0 Yes Details →
1.11.7 22 Aug 2025 U1 Apache-2.0 Yes Details →
1.11.6 14 Aug 2025 U1 Apache-2.0 Yes Details →
1.11.5 07 Aug 2025 U1 Apache-2.0 Yes Details →
1.11.4 31 Jul 2025 U1 Apache-2.0 Yes Details →
1.11.3 24 Jul 2025 U1 Apache-2.0 Yes Details →
1.11.2 10 Jul 2025 U1 Apache-2.0 Yes Details →
1.11.1 03 Jul 2025 U1 Apache-2.0 Yes Details →
1.11.0 26 Jun 2025 U1 Apache-2.0 Yes Details →
1.10.21 20 Jun 2025 U1 Apache-2.0 Yes Details →
1.10.20 13 Jun 2025 U1 Apache-2.0 Yes Details →
1.10.19 05 Jun 2025 U1 Apache-2.0 Yes Details →
1.10.18 29 May 2025 U1 Apache-2.0 Yes Details →
1.10.18rc2 29 May 2025 U1 Apache-2.0 Yes Details →
1.10.18rc1 29 May 2025 U1 Apache-2.0 Yes Details →
1.10.18rc0 29 May 2025 U1 Apache-2.0 Yes Details →
1.10.17 23 May 2025 U1 Apache-2.0 Yes Details →
1.10.16 22 May 2025 U1 Apache-2.0 Yes Details →
1.10.15 15 May 2025 M1 U2 Apache-2.0 Yes Details →
1.10.14 08 May 2025 M1 U2 Apache-2.0 Yes Details →
1.10.13 01 May 2025 M1 U2 Apache-2.0 Yes Details →
1.10.12 24 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.11 18 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.11rc1 17 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.11rc0 17 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.10 11 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.9 04 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.8 03 Apr 2025 M1 U2 Apache-2.0 Yes Details →
1.10.7 28 Mar 2025 M1 U2 Apache-2.0 Yes Details →
1.10.7rc0 27 Mar 2025 M1 U2 Apache-2.0 Yes Details →
1.10.6 20 Mar 2025 M1 U2 — Yes Details →
1.10.6rc0 20 Mar 2025 M1 U2 — Yes Details →
1.10.5 13 Mar 2025 M1 U2 — Yes Details →
1.10.4 06 Mar 2025 M1 U2 — Yes Details →
1.10.3 28 Feb 2025 M1 U2 — Yes Details →
1.10.2 20 Feb 2025 M1 U2 — Yes Details →
1.10.1 14 Feb 2025 M1 U2 — Yes Details →
1.10.0 13 Feb 2025 M1 U2 — Yes Details →
1.9.13 11 Feb 2025 M1 U2 — Yes Details →
1.9.12 10 Feb 2025 M1 U2 — Yes Details →
1.9.11 29 Jan 2025 M1 U2 — Yes Details →
1.9.10 23 Jan 2025 M1 U2 — Yes Details →
1.9.9 17 Jan 2025 M1 U2 — Yes Details →
1.9.8 10 Jan 2025 M1 U2 — Yes Details →
1.9.7 09 Jan 2025 M1 U2 — Yes Details →
1.9.6 19 Dec 2024 M1 U2 — Yes Details →
1.9.5 12 Dec 2024 M1 U2 — Yes Details →
1.9.4 06 Dec 2024 M1 U2 — Yes Details →
1.9.4rc0 06 Dec 2024 M1 U2 — Yes Details →
1.9.3 21 Nov 2024 M1 U2 — Yes Details →

The newest 120 of 746 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for dagster

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-41490: Dagster SQL Injection Vulnerability via Dynamic Partition Keys 8.3 high 1.13.1 13 Jul 2026
CVE-2023-51232: Dagster Path Traversal Vulnerability in /logs Endpoint 7.5 medium 1.5.11 07 Jul 2025
CVE-2023-51232: Dagster Path Traversal Vulnerability in /logs Endpoint 7.5 high 1.5.11 07 Jul 2026
CVE-2025-51481: Dagster Local File Inclusion Vulnerability 6.6 medium 1.10.16 22 Jul 2025
CVE-2025-51481: Dagster Local File Inclusion Vulnerability 6.6 medium 1.10.16 07 Jul 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 dagster

Is dagster safe to use?

Vulert records 5 vulnerabilities for dagster in PyPI: 0 critical, 0 high, 2 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is dagster's Vulert package health score?

Vulert scores dagster 78/100, which reads as in good shape. 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).

Is the latest version of dagster affected?

No. 1.13.26, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of dagster should I use?

1.13.26 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 dagster have?

5 vulnerabilities are recorded for dagster in the PyPI ecosystem: 0 critical, 0 high, 2 medium and 0 low, plus 3 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 dagster vulnerabilities disclosed?

3 vulnerabilities were recorded for dagster in the last 12 months, and the oldest entry in this database dates to 07 Jul 2025. 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 dagster 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 dagster for upcoming vulnerabilities?

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