6174 matches found
EUVD-2024-52990
Malicious code in bioql PyPI...
EUVD-2024-54050
Malicious code in bioql PyPI...
EUVD-2025-10548
Malicious code in bioql PyPI...
EUVD-2023-34285
Malicious code in bioql PyPI...
EUVD-2022-40014
Malicious code in bioql PyPI...
EUVD-2022-3784
Malicious code in bioql PyPI...
EUVD-2022-7498
Malicious code in bioql PyPI...
EUVD-2022-0378
Malicious code in bioql PyPI...
EUVD-2024-53445
Malicious code in bioql PyPI...
EUVD-2023-59406
Malicious code in bioql PyPI...
EUVD-2024-34300
Malicious code in bioql PyPI...
EUVD-2022-40802
Malicious code in bioql PyPI...
EUVD-2025-32189
Malicious code in bioql PyPI...
EUVD-2023-2792
Malicious code in bioql PyPI...
EUVD-2011-1471
Malicious code in bioql PyPI...
EUVD-2023-12884
Malicious code in bioql PyPI...
@circleci/agents (2.13.2-canary.8150572), @tessl/cli (>=0.21.0, <=0.21.2) +9 more potentially affected by CVE-2025-59536 via @anthropic-ai/claude-code (>=1.0.8, <=1.0.108)
@anthropic-ai/claude-code NPM version =1.0.8, =0.21.0, =0.2.0, =0.1.34, =1.8.0, =0.1.44, =0.0.22, =0.0.11, =0.0.27, =0.0.31 - locadex 0.0.2-alpha.1 Source cves: CVE-2025-59536 Source advisory: OSV:GHSA-4FGQ-FPQ9-MR3G...
MITRE: CVE-2025-59489 Unity Gaming Engine Editor vulnerability
Unity announced a security vulnerability CVE-2025-59489 that is affecting games or applications built with the Unity Gaming Engine Editor version 2017.1 or later. You may be using a Microsoft app or playing a Microsoft game that should be uninstalled until an update is available. We are working t...
Zyxel < 5.38 Directory Traversal
According to its banner, the version of Zyxel running on the remote host is 5.38. It is, therefore, affected by a Directory Traversal that could allow an attacker to download or upload files via a crafted URL. Note that the scanner has not tested for these issues but has instead relied only on th...
CVE-2025-9697 Ajax WooSearch <= 1.0.0 - Unauthenticated SQL Injection
The Ajax WooSearch WordPress plugin through 1.0.0 does not properly sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection...