dagster-snowflake-polars
An orchestration platform for the development, production, and observation of data assets.
View on Github
Activity
- Latest release
- 15h ago
- Total releases
- 64
- Cadence
- ~6 days
- Last 12 months
- 61
Reach
- Stars
- 15.9k
Details
- License
- Apache-2.0
- First release
- Jul 10, 2025
| Version | Released | |
|---|---|---|
0.29.16
patch
| ||
0.29.15
patch
| ||
0.29.14
patch
| ||
0.29.13
patch
| ||
0.29.12
patch
| ||
0.29.11
patch
| ||
0.29.10
patch
| ||
0.29.9
patch
| ||
0.29.8
patch
| ||
0.29.7
patch
| ||
0.29.6
patch
| ||
0.29.5
patch
| ||
0.29.5rc0
pre
| ||
0.29.4
patch
| ||
0.29.3
patch
| ||
0.29.2
patch
| ||
0.29.1
patch
| ||
0.29.0
minor
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.22
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.21
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.20
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.19
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.18
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.17
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.17rc0
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.16
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.16rc1
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.15
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.15rc4
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.15rc3
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.14
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.14rc4
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.14rc3
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.14rc2
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.13
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.13rc0
pre
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.12
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.11
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.10
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.9
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.8
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.7
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.6
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.5
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.4
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.3
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.2
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.1
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.28.0
minor
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
0.27.16
patch
1 CVE
CVE-2026-41490
PYSEC-2026-2437
GHSA-mjw2-v2hm-wj34
PYSEC-2026-2432
PYSEC-2026-2433
PYSEC-2026-2434
PYSEC-2026-2435
PYSEC-2026-2436
Jul 13, 2026
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
8.3
/ 10
High
Network
Low
Low
None
Unchanged
High
High
Low
SummaryThe DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. ImpactDagster OSS: Any user with access to the Dagster API can create dynamic partition keys. Organizations should assess exposure based on who has API access in their deployment. Dagster is typically deployed in trusted environments where users who can manage partitions already have equivalent database access through other means. Dagster+: In most Dagster+ deployments using default permission sets, the The vulnerability is most relevant in deployments where this permission has been granted independently of broader database access, such as certain multi-tenant or custom RBAC configurations. In those cases, an affected user could read or modify data within the databases accessible to the I/O manager, beyond what their role would otherwise permit. Organizations should review which users hold this permission and assess their exposure accordingly. RemediationUpdate to the patched versions listed above. No configuration changes or workarounds are required alongside the update. Only your Dagster code version needs to be updated; the Dagster+ agent/Dagster OSS daemon/webserver do not need to be updated. The fix ensures that partition key values are properly escaped before inclusion in SQL queries across all affected I/O managers. If you are unable to apply the update, manual workarounds are described here. Affected versions
0.27.10
0.27.11
0.27.12
0.27.13
0.27.14
0.27.15
0.27.16
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
+ 35 more Show less
0.27.7
0.27.8
0.27.9
0.28.0
0.28.1
0.28.10
0.28.11
0.28.12
0.28.13
0.28.13rc0
0.28.14
0.28.14rc2
0.28.14rc3
0.28.14rc4
0.28.15
0.28.15rc3
0.28.15rc4
0.28.16
0.28.16rc1
0.28.17
0.28.17rc0
0.28.18
0.28.19
0.28.2
0.28.20
0.28.21
0.28.22
0.28.3
0.28.4
0.28.5
0.28.6
0.28.7
0.28.8
0.28.9
0.29.0
Fixed in
0.29.1
References
Updated Jul 13, 2026 · Source: OSV.dev |