Apache Airflow Providers SnowflakeWeb server / proxy · Apache
CVE-2025-50213
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 · uneditedFailure to Sanitize Special Elements into a Different Plane (Special Element Injection) vulnerability in Apache Airflow Providers Snowflake. This issue affects Apache Airflow Providers Snowflake: before 6.4.0. Sanitation of table and stage parameters were added in CopyFromExternalStageToSnowflakeOperator to prevent SQL injection Users are recommended to upgrade to version 6.4.0, which fixes the issue.
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 confidenceSQL injection vulnerability in Apache Airflow Providers Snowflake's CopyFromExternalStageToSnowflakeOperator where table and stage parameters were not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code through these parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Apache Airflow Providers SnowflakeWeb server / proxy
< 6.4.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed version of Snowflake providerRun 'pip show apache-airflow-providers-snowflake' or inspect your requirements.txt/pipfile to find the installed versionAffected if Version is lower than 6.4.0 (e.g., 6.3.0, 6.2.0, etc.)
-
Identify use of CopyFromExternalStageToSnowflakeOperatorSearch your DAG files and codebase for imports and usage: 'from airflow.providers.snowflake.operators.copy_from_external_stage import CopyFromExternalStageToSnowflakeOperator' and any instantiation of this operatorAffected if This operator is imported or used in any DAG
-
Inspect table parameter usage in DAGsOpen DAG files using this operator and examine the 'table' parameter passed to CopyFromExternalStageToSnowflakeOperator - check if it contains dynamic values, user input, or variablesAffected if The table parameter accepts variables, user input, or values from untrusted sources without validation
-
Inspect stage parameter usage in DAGsOpen DAG files using this operator and examine the 'stage' parameter passed to CopyFromExternalStageToSnowflakeOperator - check if it contains dynamic values, user input, or variablesAffected if The stage parameter accepts variables, user input, or values from untrusted sources without validation
You are affected if you have apache-airflow-providers-snowflake version < 6.4.0 AND are using CopyFromExternalStageToSnowflakeOperator with table or stage parameters that could contain dynamic or untrusted input.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.4.0
Upgrade Apache Airflow Providers Snowflake to version 6.4.0 or later, which includes proper sanitization of table and stage parameters in the CopyFromExternalStageToSnowflakeOperator.
apache-airflow-providers-snowflake >= 6.4.0
- Check current installed version of apache-airflow-providers-snowflake by running: pip show apache-airflow-providers-snowflake
- Upgrade to version 6.4.0 or later using: pip install --upgrade apache-airflow-providers-snowflake>=6.4.0
- Verify the upgrade was successful by running: pip show apache-airflow-providers-snowflake and confirming the version is 6.4.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Apache Airflow Providers Snowflake
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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