CVE-2026-15067
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 · uneditedSnowflake Terraform Provider versions prior to 2.18.0 contain several security vulnerabilities, including SQL injection via an unsanitized data source input could result in arbitrary SQL execution under the provider's privileged Snowflake session, potentially enabling sensitive data exfiltration and minting of long-lived access credentials. Exploitation requires the ability for an attacker to influence a workspace variable in a pipeline where this data source was enabled. Improper neutralization of identifier content in user resource inputs could allow DDL injection into user management statements, potentially causing accounts to be created with attacker-controlled credentials and without the security controls configured by the operator. The fix is available in Snowflake Terraform Provider version 2.18.0. Users must manually upgrade.
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 confidenceThe Snowflake Terraform Provider versions before 2.18.0 contain SQL injection vulnerabilities in data source handling that allow arbitrary SQL execution under the provider's privileged Snowflake session. Additionally, improper neutralization of identifier content in user resource inputs enables DDL injection for creating unauthorized accounts with attacker-controlled credentials. Exploitation requires the attacker to influence a workspace variable in a pipeline using the affected data source.
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
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Snowflake Terraform Provider versionInspect your Terraform lock file (.terraform.lock.hcl) or provider configuration for the snowflake-labs/snowflake provider entry. Run 'terraform providers' to list all providers and their versions in use.Affected if The provider version is lower than 2.18.0 (e.g., 2.17.0, 2.16.0, etc.)
-
Locate data source usage in Terraform configurationsSearch your Terraform code for 'data "snowflake_' blocks. Identify which Snowflake data sources are referenced (e.g., data.snowflake_database, data.snowflake_schema, data.snowflake_table).Affected if Any snowflake_* data sources are present in your Terraform configurations.
-
Check for workspace variable influence on data sourcesExamine whether workspace variables (TF_WORKSPACE or variables passed via -var or environment) are used as arguments in snowflake_* data source blocks. Look at the query or filter arguments.Affected if Workspace variables or external variables flow into query/filter arguments of Snowflake data sources without sanitization.
-
Audit user resource inputs for injection vectorsReview all snowflake_user resource definitions for dynamic or variable-based values in fields like name, comment, or default_warehouse that could be attacker-controlled.Affected if User resource arguments contain interpolated variables from pipeline workspace or external sources without validation.
-
Review pipeline workspace variable sourcesInspect your CI/CD pipeline configuration for how workspace variables are set and whether they can be influenced by external contributors, pull requests, or untrusted inputs.Affected if Workspace variables can be modified by non-privileged users or external parties who could inject malicious values.
You are affected if the Snowflake Terraform Provider version is below 2.18.0 AND your configurations use Snowflake data sources with workspace-controlled variables, or user resources with unvalidated dynamic inputs that could be influenced by an attacker.
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 · scopedUpgrade Snowflake Terraform Provider to version 2.18.0 or later, and audit Terraform configurations and pipeline workspace variables for signs of compromise or unauthorized modifications.
Snowflake Terraform Provider version 2.18.0
- 1. Identify all Terraform configurations using the Snowflake Terraform Provider
- 2. Locate the provider block specifying the Snowflake Terraform Provider version
- 3. Update the version constraint to specify version 2.18.0 or later (e.g., version = ">= 2.18.0")
- 4. Run `terraform init -upgrade` to download the updated provider version
- 5. Run `terraform plan` to verify the upgrade does not introduce unintended changes
- 6. Apply the changes with `terraform apply` to complete the upgrade
- 7. Review any workspace variables that could be influenced by external parties to ensure they are properly validated before use
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15067 — 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-2026-15067 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