Quick answers
- Is CVE-2026-16870 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16870 being exploited in the wild.
- How severe is CVE-2026-16870?
- High severity, with a CVSS score of 8.8, published 24 July 2026.
- Which products and versions are affected?
- Snowflake Libsnowflakeclient 0.1.1 to < 2.9.2.
- Is there a fix for CVE-2026-16870?
- A patch was published on 2026-07-17: Version 2.9.2 released on GitHub Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16870 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16870?
- Check whether you run Snowflake Libsnowflakeclient at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Snowflake libsnowflakeclient versions prior to 2.9.2 contain multiple vulnerabilities: a stack-based buffer overflow (CWE-121) and an out-of-bounds write (CWE-787) in the file download path, and improper validation of connection parameters (CWE-918). The memory corruption issues can be triggered by uploading files with malicious encryption metadata or initialization vectors to a shared internal stage; when a victim process downloads these files, an attacker can achieve remote code execution or memory corruption. Additionally, the lack of connection parameter validation allows attackers to redirect outbound authentication requests to malicious endpoints, potentially capturing service credentials. These exploits require network access and, in some cases, low-privileged authenticated access to a shared stage. The vulnerabilities are resolved in version 2.9.2.
Affected products
- Snowflake libsnowflakeclient 0.1.1 to < 2.9.2
Timeline
- 2026-07-17: patched: Version 2.9.2 released on GitHub
- 2026-07-24: disclosed: CVE-2026-16870 published