CVE-2026-41490

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.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-41490 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.29.1, 1.13.1); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-41490? CVE-2026-41490 is a high-severity SQL injection vulnerability in dagster-duckdb (pip), affecting versions <= 0.29.0. It is fixed in 0.29.1, 1.13.1. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-41490? CVE-2026-41490 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-41490?
   • dagster-duckdb (pip) (versions <= 0.29.0)
   • dagster-snowflake (pip) (versions <= 0.29.0)
   • dagster-gcp (pip) (versions <= 0.29.0)
   • dagster (pip) (versions <= 1.13.0)
   • dagster-deltalake (pip) (versions <= 0.29.0)
   • dagster-snowflake-polars (pip) (versions <= 0.29.0)
4. Is there a fix for CVE-2026-41490? Yes. CVE-2026-41490 is fixed in 0.29.1, 1.13.1. Upgrade to this version or later.
5. Is CVE-2026-41490 exploitable, and should I be worried? Whether CVE-2026-41490 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41490 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41490?
   • Upgrade dagster-duckdb to 0.29.1 or later
   • Upgrade dagster-snowflake to 0.29.1 or later
   • Upgrade dagster-gcp to 0.29.1 or later
   • Upgrade dagster to 1.13.1 or later
   • Upgrade dagster-deltalake to 0.29.1 or later
   • Upgrade dagster-snowflake-polars to 0.29.1 or later