# CVE-2026-86600: Workload identity attestation generated before login host validation in Snowflake drivers

> Attackers can steal workload identity tokens by manipulating driver connection settings, allowing unauthorized access to Snowflake accounts or Azure resources.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-fhj9-24fm-m53p

## What is CVE-2026-86600?

CVE-2026-86600 is a high-severity vulnerability in Snowflake Connector for .NET, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In affected Snowflake drivers, WORKLOAD_IDENTITY authentication requests a cloud workload-identity token and attaches it to the login request without verifying that the configured host is a Snowflake endpoint. An attacker who can modify the connection configuration can cause the driver to mint a fresh attestation and send it to a host they control. The captured token can be replayed to Snowflake for its remaining lifetime in accounts where that workload identity is already registered. On Azure, the token audience is also taken from connection configuration. Combined with an attacker-controlled host, the driver can request a Managed Identity access token scoped to a non-Snowflake Azure resource and deliver it to the attacker. That path is the only case in which impact extends beyond Snowflake; it is bounded by the token lifetime and the managed identity’s permissions. Successful exploitation requires WORKLOAD_IDENTITY authentication on a workload that already has an ambient cloud identity. Patched driver versions restrict this authenticator to recognized Snowflake hosts. Users must manually upgrade.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-86600?


## How do I fix CVE-2026-86600?

No fix has been published for CVE-2026-86600 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86600 being exploited?

There is no known exploitation of CVE-2026-86600 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86600 and fix it if it is affected.

What it is: CVE-2026-86600 is a high-severity vulnerability in Snowflake Connector for .NET, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86600 in the wild and no public exploit code.

Affected product: Snowflake Connector for .NET. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86600/ (Markdown: https://insights.sbomify.com/CVE-2026-86600/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86600
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86600
- OSV: https://osv.dev/vulnerability/CVE-2026-86600

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86600/
Summaries are generated and may contain mistakes; the official description above is the record.