dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-41490

HIGH · 8.3 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dagster is an orchestration platform for the development, production, and observation of data assets. Prior to Dagster Core version 1.13.1 and prior to Dagster libraries version 0.29.1, 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. This issue has been patched in Dagster Core version 1.13.1 and Dagster libraries version 0.29.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Dagster's DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers where dynamic partition key values are interpolated into SQL WHERE clauses without proper escaping or parameterization. A user with Add Dynamic Partitions permission can inject arbitrary SQL that executes against the target database under the I/O manager's credentials.

MitigationUpgrade to Dagster Core 1.13.1 or Dagster libraries 0.29.1 or later. As an interim measure, restrict the Add Dynamic Partitions permission to highly trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify configured I/O managers
    Review your Dagster deployment configuration (typically in workspace.yaml, dagster.yaml, or code definitions) for I/O manager definitions using DuckDB, Snowflake, BigQuery, or DeltaLake
    Affected if Any of these four I/O managers are configured and in use
  2. Check for dynamic partition usage
    Search your repository definitions for assets or jobs using dynamic partitions - look for DynamicPartitionsDefinition or calls to add_dynamic_partitions
    Affected if Dynamic partitions are defined on any assets that use the affected I/O managers
  3. Verify Dagster version
    Run 'pip show dagster' or check your lock file (requirements.txt, poetry.lock, etc.) to determine installed Dagster Core or library version
    Affected if Version is below 1.13.1 for Dagster Core or below 0.29.1 for Dagster libraries
  4. Review Add Dynamic Partitions permission
    Check your deployment's permissions configuration (in dagster.yaml or your authentication backend) for users or roles granted the Add Dynamic Partitions permission
    Affected if Users beyond highly trusted administrators have Add Dynamic Partitions permission

Environment is affected if any of DuckDB/Snowflake/BigQuery/DeltaLake I/O managers are in use with dynamic partitions on a Dagster version below 1.13.1 (or libraries below 0.29.1) and untrusted users have Add Dynamic Partitions permission.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Dagster Core 1.13.1 or Dagster libraries 0.29.1 or later. As an interim measure, restrict the Add Dynamic Partitions permission to highly trusted users only.

Recommended fix High confidence

Dagster Core 1.13.1 or later / Dagster libraries 0.29.1 or later

  1. Identify if your deployment uses dynamic partitions with DuckDB, Snowflake, BigQuery, or DeltaLake I/O managers (only these configurations are vulnerable)
  2. Upgrade Dagster Core to version 1.13.1 or later
  3. Upgrade Dagster libraries to version 0.29.1 or later
  4. Verify the fix by testing dynamic partition functionality to ensure partition keys are properly escaped

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41490 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41490 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data