CVE-2026-86600
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 24% of all known CVEs.
References
Related Vulnerabilities
Other CWE-441 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-47269 | High | 8.3 | 43% | - | - |
| CVE-2019-3924 | High | 7.5 | 16% | - | Fix |
| CVE-2020-5412 | Medium | 6.5 | 10% | - | Fix |
| CVE-2019-3996 | Medium | 6.5 | 5.9% | - | - |
| CVE-2026-83548 | Critical | 10.0 | 4.7% | KEV | Fix |
| CVE-2019-1841 | Medium | 6.5 | 2.6% | - | Fix |
Common questions
How do I fix CVE-2026-86600?
No published fix for CVE-2026-86600 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-86600 being actively exploited?
Not that we know of. CVE-2026-86600 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.31% is the estimated probability that it will be exploited in the next 30 days. That is higher than 24% of all scored CVEs.
How severe is CVE-2026-86600?
CVE-2026-86600 has a CVSS v3 base score of 8.2, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-86600
Markdown
[](https://tridentstack.com/cve/CVE-2026-86600)HTML
<a href="https://tridentstack.com/cve/CVE-2026-86600"><img src="https://tridentstack.com/cve/badge/CVE-2026-86600.svg" alt="CVE-2026-86600"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-10.