CyberSecBulletin
CVE-2026-86600NVD status: Awaiting Analysis

Snowflake Connector for Python: Unintended Proxy or Intermediary

Published Updated By the CyberSecBulletin desk

CVE-2026-86600 is a high-severity unintended proxy or intermediary vulnerability in Snowflake Connector for Python from Snowflake, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 4.7.3 as the first without the flaw, so updating Snowflake Connector for Python to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Snowflake Connector for Python to 4.7.3 or a later version.
  2. Update Snowflake Go Driver to 2.2.0 or a later version.
  3. Update Snowflake JDBC Driver to 4.3.4 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
SnowflakeSnowflake Connector for Python3.14.1 up to, but not including, 4.7.34.7.3
SnowflakeSnowflake Go Driver1.15.0 through 1.19.1; 2.0.0 up to, but not including, 2.2.02.2.0
SnowflakeSnowflake JDBC Driver3.24.0 up to, but not including, 4.3.44.3.4
SnowflakeSnowflake JDBC Driver (FIPS)3.24.0 up to, but not including, 4.3.44.3.4
SnowflakeSnowflake JDBC Driver (Thin)3.24.0 up to, but not including, 4.3.44.3.4
SnowflakeSnowflake Node.js Driver2.1.1 up to, but not including, 3.3.03.3.0
SnowflakeSnowflake Connector for .NET4.7.0 up to, but not including, 6.1.06.1.0
SnowflakeSnowflake ODBC Driver3.9.0 up to, but not including, 3.20.03.20.0
SnowflakeSnowflake PHP PDO Driver3.6.0 up to, but not including, 4.2.04.2.0
SnowflakeSnowflake Libsnowflakeclient2.2.0 up to, but not including, 2.10.02.10.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N. Scored by CNA.

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Unintended Proxy or Intermediary

The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere.

How developers prevent this class of flaw

  • Enforce the use of strong mutual authentication mechanism between the two parties.
  • Whenever a product is an intermediary or proxy for transactions between two other components, the proxy core should not drop the identity of the initiator of the transaction. The immutability of the identity of the initiator must be maintained and should be forwarded all the way to the target.

More Unintended Proxy or Intermediary vulnerabilities (CWE-441)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Snowflake Connector for Python

All Snowflake Connector for Python vulnerabilities

Recent Unintended Proxy or Intermediary vulnerabilities

Spotted an error? Tell us.