CVE-2025-27496: Snowflake JDBC Driver Client-Side Encryption Key Exposure in DEBUG Logs
Summary
CVE-2025-27496: Snowflake JDBC Driver client-side encryption key in DEBUG logs. Affects net.snowflake:snowflake-jdbc versions >= 3.0.13, < 3.23.1. Fixed in 3.23.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Snowflake JDBC Driver is a Java-based library that allows applications to connect to Snowflake's cloud data platform. It provides functionalities for executing SQL commands, managing connections, and handling data securely. However, a vulnerability was identified in versions 3.0.13 through 3.23.0, where sensitive information could be logged under certain conditions, potentially exposing client-side encryption keys.
Vulnerability Detail
The vulnerability arises when the logging level of the Snowflake JDBC Driver is set to DEBUG. In this state, the driver logs the client-side encryption master key of the target stage during GET/PUT command executions. This key is logged in a JSON object under the 'queryStageMasterKey' key. Although the key does not grant direct access to sensitive data without additional authorizations, its exposure in logs can pose a security risk if logs are accessed by unauthorized users.
How To Fix
Latest published version: 4.4.0 as of 23 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.23.1
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can avoid setting the logging level to DEBUG to prevent the logging of sensitive information until they can upgrade to the patched version.
Conclusion
The Snowflake JDBC Driver vulnerability (CVE-2025-27496) highlights the importance of secure logging practices. Users are strongly encouraged to upgrade to version 3.23.1 to mitigate the risk of exposing sensitive encryption keys in logs.
See every vulnerability recorded for net.snowflake:snowflake-jdbc →
FAQ
The vulnerability can lead to the exposure of client-side encryption keys in DEBUG logs, which may be accessed by unauthorized individuals if proper log management practices are not followed.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
No, the exposed key by itself does not grant access to sensitive data without additional access authorizations.
The vulnerability affects Snowflake JDBC Driver versions from 3.0.13 to 3.23.0.
If immediate upgrading is not possible, avoid using DEBUG logging to minimize the risk of exposing sensitive information.
References
Related vulnerabilities
Recent vulnerabilities recorded for net.snowflake:snowflake-jdbc.
