{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-86600 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86600 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-86600 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-86600 in the wild and no public exploit code.\n\nAffected product: Snowflake Connector for .NET. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-86600/ (Markdown: https://insights.sbomify.com/CVE-2026-86600/index.md)","id":"CVE-2026-86600","markdown":"https://insights.sbomify.com/CVE-2026-86600/index.md","name":"CVE-2026-86600","record":{"aliases":["GHSA-fhj9-24fm-m53p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Snowflake database drivers","requires_auth":"low_privilege","summary":"Attackers can steal workload identity tokens by manipulating driver connection settings, allowing unauthorized access to Snowflake accounts or Azure resources.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SNOWFLAKE","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-441","name":"Unintended Proxy or Intermediary"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Workload identity attestation generated before login host validation in Snowflake drivers","id":"CVE-2026-86600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"WP Recipe Maker \u003c 10.8.2 - Unauthenticated Arbitrary Shortcode Execution via Comment Content","id":"CVE-2026-86601"},"packages":[],"prev":{"headline":"Sensitive information written to logs by Snowflake drivers","id":"CVE-2026-86597"},"products":["Snowflake Connector for .NET","Snowflake Connector for Python","Snowflake Go Driver","Snowflake JDBC Driver","Snowflake JDBC Driver (FIPS)","Snowflake JDBC Driver (Thin)","Snowflake Libsnowflakeclient","Snowflake Node.js Driver","Snowflake ODBC Driver","Snowflake PHP PDO Driver"],"published":"2026-09-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["Snowflake"]},"summary":"Attackers can steal workload identity tokens by manipulating driver connection settings, allowing unauthorized access to Snowflake accounts or Azure resources.","url":"https://insights.sbomify.com/CVE-2026-86600/"}