NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
27 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.6 CVE-2026-121925 A stack-based buffer overflow in libsnowflakeclient and the Snowflake PHP PDO Driver could, under specific conditions, result in memory corruption during SAML-… 17 days ago medium6.5 CVE-2026-114456 Multiple Snowflake client drivers implementing the `authenticator=externalbrowser` single sign-on flow could have allowed an attacker to interfere with a user'… 17 days ago medium6.3 CVE-2026-81930 Apache Airflow's Snowflake provider did not validate the connection's `account` and `region` fields before interpolating them into request URLs. apache · apache-airflow-providers-snowflake 53 days ago medium6.5 GHSA-5cwm-p7pj-gqp2 Duplicate Advisory: Sensitive information written to logs by Snowflake drivers npm · snowflake-sdk 2026-09-08 medium6.5 CVE-2026-86597 Insertion of sensitive information into log files in the Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers allowed authentication tokens, query-re… npm · snowflake-sdk, pip · snowflake-connector-python, go · github.com/snowflakedb/gosnowflake +4 2026-09-08 medium5.3 CVE-2026-85528 Improper input validation of the auto-configuration account identifier in Snowflake JDBC Driver versions 4.2.0 through 4.3.3 allowed a credential-bearing login… Snowflake JDBC Driver 2026-09-04 medium5.3 GHSA-652q-gvq3-74qv n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation npm · n8n, npm · n8n, npm · n8n 2026-07-22 medium6.0 CVE-2026-13752 Improper neutralization of parameters in Snowflake CLI versions prior to 3.19 allowed unintended SQL execution. snowflake · snowflake_cli 2026-06-29 medium4.1 CVE-2026-13751 Improper handling of untrusted remote references in Snowflake CLI versions prior to 3.19 allowed server-side request forgery. snowflake · snowflake_cli 2026-06-29 medium5.5 CVE-2026-13750 Insertion of sensitive information into log files in Snowflake CLI versions prior to 3.19 allowed plaintext credentials to be written to persistent local debug… snowflake · snowflake_cli 2026-06-29 medium6.3 CVE-2026-13748 Improper restriction of file path resolution in Snowflake CLI versions prior to 3.19 allowed arbitrary local file content to be read and transmitted to Snowfla… snowflake · snowflake_cli 2026-06-29 medium4.7 CVE-2026-33682 Unauthenticated SSRF Vulnerability in Streamlit on Windows (NTLM Credential Exposure) pip · Streamlit 2026-03-25 medium5.0 CVE-2025-24788 Snowflake.Data has weak temporary files permissions nuget · Snowflake.Data 2025-01-29 medium6.7 CVE-2025-24794 snowflake-connector-python vulnerable to insecure deserialization of the OCSP response cache pip · snowflake-connector-python 2025-01-29 medium4.4 CVE-2025-24795 snowflake-connector-python vulnerable to insecure cache files permissions pip · snowflake-connector-python 2025-01-29 medium4.4 CVE-2025-24790 Snowflake JDBC uses insecure temporary credential cache file permissions maven · net.snowflake:snowflake-jdbc 2025-01-29 medium4.4 CVE-2025-24791 snowflake-sdk may incorrectly validate temporary credential cache file permissions npm · snowflake-sdk 2025-01-29 medium4.4 CVE-2025-24792 Snowflake PHP PDO Driver is a driver that uses the PHP Data Objects (PDO) extension to connect to the Snowflake database. versions 2025-01-29 medium5.9 CVE-2024-43382 Snowflake JDBC Security Advisory maven · net.snowflake:snowflake-jdbc 2024-10-30 medium5.5 CVE-2024-49750 The Snowflake Connector for Python stores sensitive data in logs pip · snowflake-connector-python 2024-10-24 medium5.9 CVE-2024-42474 Path traveral in Streamlit on windows pip · streamlit 2024-08-12 medium4.0 CVE-2024-28851 The Snowflake Hive metastore connector provides an easy way to query Hive-managed data via Snowflake. snowflake · snowflake_hive_metastore_connector 2024-03-15 medium6.0 CVE-2023-51662 Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL) nuget · Snowflake.Data 2023-12-22 medium5.9 CVE-2023-27494 Streamlit publishes previously-patched Cross-site Scripting vulnerability pip · streamlit 2023-03-16 medium5.9 CVE-2022-42965 snowflake-connector-python is vulnerable to Regular Expression Denial of Service (ReDoS) pip · snowflake-connector-python 2022-11-09 medium6.5 CVE-2022-35918 Streamlit directory traversal vulnerability pip · streamlit 2022-08-01 medium4.3 CVE-2010-0797 Cross-site scripting (XSS) vulnerability in the T3BLOG extension 0.6.2 and earlier for TYPO3 allows remote attackers to inject arbitrary web script or HTML via… snowflake · t3blog 2010-03-02

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.