CVEs.
Vulnerabilities published in the last two years in software made by the companies on the wall: clients, SDKs, agents and self-hosted editions. A CVE here does not mean the hosted service was affected or breached.
NVD data refreshed 25 min ago
Severity of matching CVEs
CVSS base severity, as scored in NVD
- Critical
- 00%
- High
- 00%
- Medium
- 00%
- Low or not scored
- 5100%
- Matching CVEs
- 5
- Last two years
- Critical
- 0
- CVSS 9.0 and above
- High
- 0
- CVSS 7.0 to 8.9
- Known exploited
- 0
- On CISA's KEV list
Matching CVEs published
By month, last two years
Peak 2 · April 2025
- Total: 5
- December 2024: 0
- January 2025: 0
- February 2025: 0
- March 2025: 1
- April 2025: 2
- May 2025: 0
- June 2025: 0
- July 2025: 0
- August 2025: 0
- September 2025: 0
- October 2025: 0
- November 2025: 0
- December 2025: 0
- January 2026: 0
- February 2026: 1
- March 2026: 0
- April 2026: 0
- May 2026: 0
- June 2026: 1
- July 2026: 0
- August 2026: 0
- September 2026: 0
- October 2026: 0
- November 2026: 0
Most CVEs
In each company's software, last two years
Matching CVEs
- 1.1Low
CVE-2026-10804 (opens in a new tab)
A vulnerability has been found in Streamlit up to 1.53.0. Impacted is an unknown function in the library lib/streamlit/runtime/caching/hashing.py of the component Palette Handler. Such manipulation leads to use of weak hash. Local access is required to approach this attack. The attack requires a high level of complexity. The exploitability is considered difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
Snowflake· Jun 4, 2026
- 1.9Low
CVE-2026-3293 (opens in a new tab)
A weakness has been identified in snowflakedb snowflake-jdbc up to 4.0.1. Impacted is the function SdkProxyRoutePlanner of the file src/main/java/net/snowflake/client/internal/core/SdkProxyRoutePlanner.java of the component JDBC URL Handler. Executing a manipulation of the argument nonProxyHosts can lead to inefficient regular expression complexity. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 5fb0a8a318a2ed87f4022a1f56e742424ba94052. A patch should be applied to remediate this issue.
Snowflake· Feb 27, 2026
- 3.3Low
CVE-2025-46330 (opens in a new tab)
libsnowflakeclient is the Snowflake Connector for C/C++. Versions starting from 0.5.0 to before 2.2.0, incorrectly treat malformed requests that caused the HTTP response status code 400, as able to be retried. This could hang the application until SF_CON_MAX_RETRY requests were sent. This issue has been patched in version 2.2.0.
Snowflake· Apr 29, 2025
- 3.3Low
CVE-2025-46329 (opens in a new tab)
libsnowflakeclient is the Snowflake Connector for C/C++. Versions starting from 0.5.0 to before 2.2.0, are vulnerable to local logging of sensitive information. When the logging level was set to DEBUG, the Connector would log locally the client-side encryption master key of the target stage during the execution of GET/PUT commands. This key by itself does not grant access to any sensitive data without additional access authorizations, and is not logged server-side by Snowflake. This issue has been patched in version 2.2.0.
Snowflake· Apr 29, 2025
- 3.3Low
CVE-2025-27496 (opens in a new tab)
Snowflake, a platform for using artificial intelligence in the context of cloud computing, has a vulnerability in the Snowflake JDBC driver ("Driver") in versions 3.0.13 through 3.23.0 of the driver. When the logging level was set to DEBUG, the Driver would log locally the client-side encryption master key of the target stage during the execution of GET/PUT commands. This key by itself does not grant access to any sensitive data without additional access authorizations, and is not logged server-side by Snowflake. Snowflake fixed the issue in version 3.23.1.
Snowflake· Mar 13, 2025
Public information only
Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.
Sources
- National Vulnerability Database (opens in a new tab): CVE IDs, descriptions, publication dates and CVSS severity, published by the U.S. government (NIST)
- CISA Known Exploited Vulnerabilities catalog (opens in a new tab): the "Known exploited" flag
How fresh it is
- New and changed CVEs: pulled from NVD every two hours; last run 25 min ago
- Known-exploited flags: updated from CISA in the same run
- Window: the last two years; older entries drop off automatically
Source: the U.S. National Vulnerability Database, refreshed daily, with the known-exploited flag from CISA's KEV catalog. Descriptions are NVD's. A CVE is listed under a company when NVD names that company's product as affected, or when the company's own CVE authority assigned it; companies whose names are common words are matched only by explicit rules, so some CVEs will be missing. This product uses NVD data but is not endorsed or certified by the NVD. CVE is a registered trademark of The MITRE Corporation.
statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.