New from Wiz Research: Critical NGINX flaw. Understand the risk and impact.
Vulnerability DatabaseGHSA-fg36-9vq2-6v57

GHSA-fg36-9vq2-6v57: 
Python vulnerability analysis and mitigation

Summary

The fix for CVE-2026-41490 in dagster 1.13.1 / I/O manager package version 0.29.1 did not fully address SQL injection in the BigQuery and Snowflake I/O managers. The fix escaped single quotes by doubling them but did not escape backslashes, which both warehouses interpret as escape characters inside string literals. Exploitation requires the ability to control values that are used as dynamic partition keys. This can occur through direct permission to create keys, or through control of external data that custom code (such as a sensor or script) turns into partition keys, such as file names in object storage, customer IDs, or API values. Injected SQL executes under the I/O manager’s database credentials and could read or modify data accessible to those credentials. Only deployments using dynamic partitions with the BigQuery (dagster-gcp) or Snowflake (dagster-snowflake, dagster-snowflake-polars) I/O managers are affected. Static and time-window partitions are not affected. The DuckDB, DeltaLake and ClickHouse I/O managers are not affected.

Details

The earlier fix escaped single quotes by doubling them but did not escape backslashes. Because BigQuery and Snowflake interpret backslashes as escape characters inside string literals, a crafted dynamic partition key can break out of its SQL string literal and inject SQL into the WHERE clause. The injected SQL executes under the I/O manager’s database credentials when a downstream asset loads the affected partitions or when a partition is overwritten. The BigQuery I/O manager also had a separate bug that caused query errors for valid partition keys containing apostrophes: GoogleSQL does not accept doubled single quotes inside a string literal. Legitimate partition keys containing apostrophes therefore caused query syntax errors.

Exposure and impact

The preconditions and SQL injection impact are the same as CVE-2026-41490. The exposure paths below also applied to that vulnerability; the earlier advisory did not explicitly describe the external-data path. 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. Dagster+: Direct creation of dynamic partition keys requires an authenticated user with the Add Dynamic Partitions permission. In default permission sets, this 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. This direct-access path creates an additional access risk where the permission is granted without equivalent database access, such as certain multi-tenant or custom RBAC configurations. External data: In both Dagster OSS and Dagster+, someone who controls external data that custom code (such as a sensor or script) turns into dynamic partition keys may be able to introduce malicious keys without direct access to Dagster. Organizations should assess who can influence those values and whether they already have equivalent access to the underlying database. Through either path, an attacker could read or modify data accessible through the I/O manager’s database credentials beyond what their existing access would otherwise permit.

Remediation

Update dagster to 1.13.31 and your affected I/O manager package (dagster-gcp, dagster-snowflake or dagster-snowflake-polars) to 0.29.31. Upgrade both packages, even if you previously applied the fix for CVE-2026-41490 in dagster 1.13.1 / I/O manager package version 0.29.1. Only your Dagster code and I/O manager packages need to be updated. The Dagster+ agent, Dagster OSS daemon and webserver do not need to be updated. The BigQuery and Snowflake I/O managers now escape partition keys using each warehouse’s backslash escaping rules, covering backslashes, single quotes and control characters. The update also fixes BigQuery query errors for partition keys containing apostrophes. If you cannot update right away:

  • On Dagster+, restrict the Add Dynamic Partitions permission to users who already have equivalent access to the underlying database.
  • Review code that creates dynamic partition keys from external data. Sanitize those inputs to remove backslashes from generated partition keys.
  • Review existing dynamic partition keys for backslashes, and remove any you did not expect. Address both direct creation of partition keys and creation from external data; restricting the Dagster permission alone does not address the external-data path.

Credits

We thank @qypxqnyf for responsibly disclosing this vulnerability and providing detailed analysis and proof-of-concept examples that helped us investigate and address it.


Source: NVD

Related Python vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-132275HIGH7.5
  • Python logoPython
  • svglib
NoYesNov 20, 2026
CVE-2026-132276MEDIUM5.9
  • Python logoPython
  • wcmatch
NoYesNov 20, 2026
CVE-2026-132277MEDIUM5.3
  • Python logoPython
  • inscriptis
NoYesNov 20, 2026
CVE-2026-77332LOW2.3
  • Python logoPython
  • memtomem-stm
NoYesNov 20, 2026
CVE-2026-77331LOW2
  • Python logoPython
  • memtomem-stm
NoYesNov 20, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management