CVE-2026-41490 — dagster-duckdb
HIGHCVE-2026-41490 is a high-severity (CVSS 8.3) SQL Injection vulnerability in dagster-duckdb. A fix is available for dagster-duckdb — see the affected versions and patch details below.
Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41490.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
dagster-duckdb🐍dagster-snowflake🐍dagster-gcp🐍dagster🐍dagster-deltalake🐍dagster-snowflake-polarsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The 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 Add Dynamic Partitions permission could create a partition key that injects arbitrary SQL, which would execute against the target database backend under the I/O manager's credentials.
Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted.
Impact
Dagster 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 Add Dynamic Partitions permission is granted to users with an Editor role or above, who typically already have the ability to modify the affected tables and the asset code that accesses them.
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.
Remediation
Update 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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | dagster-duckdb | all versions | 0.29.1pip install --upgrade 'dagster-duckdb==0.29.1' |
| 🐍PyPI | dagster-snowflake | all versions | 0.29.1pip install --upgrade 'dagster-snowflake==0.29.1' |
| 🐍PyPI | dagster-gcp | all versions | 0.29.1pip install --upgrade 'dagster-gcp==0.29.1' |
| 🐍PyPI | dagster | all versions | 1.13.1pip install --upgrade 'dagster==1.13.1' |
| 🐍PyPI | dagster-deltalake | all versions | 0.29.1pip install --upgrade 'dagster-deltalake==0.29.1' |
| 🐍PyPI | dagster-snowflake-polars | all versions | 0.29.1pip install --upgrade 'dagster-snowflake-polars==0.29.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dagster-duckdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dagster-duckdb to 0.29.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41490 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is CVE-2026-41490 in your dependencies?
Find it across PyPI, including transitive dependencies.