2400 matches found
EUVD-2025-14813
Malicious code in bioql PyPI...
EUVD-2021-6848
Malicious code in bioql PyPI...
EUVD-2025-13100
Malicious code in bioql PyPI...
EUVD-2025-0198
Malicious code in bioql PyPI...
EUVD-2025-9409
Malicious code in bioql PyPI...
EUVD-2025-26685
Malicious code in bioql PyPI...
EUVD-2023-57247
Malicious code in bioql PyPI...
EUVD-2022-54898
Malicious code in bioql PyPI...
EUVD-2023-53199
Malicious code in bioql PyPI...
EUVD-2025-7349
Malicious code in bioql PyPI...
EUVD-2023-25670
Malicious code in bioql PyPI...
EUVD-2025-12533
Malicious code in bioql PyPI...
EUVD-2025-2615
Malicious code in bioql PyPI...
EUVD-2025-25555
Malicious code in bioql PyPI...
EUVD-2022-54689
Malicious code in bioql PyPI...
EUVD-2024-2192
Malicious code in bioql PyPI...
CodeQL zero to hero part 5: Debugging queries
When you're first getting started with CodeQL, you may find yourself in a situation where a query doesn't return the results you expect. Debugging these queries can be tricky, because CodeQL is a Prolog-like language with an evaluation model that's quite different from mainstream languages like...
GHSA-54J7-GRVR-9XWG Command Injection in adb-mcp MCP Server
Command Injection in adb-mcp MCP Server The MCP Server at https://github.com/srmorete/adb-mcp is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server is also published publicly to npm at...
CVE-2023-53403
In the Linux kernel, the following vulnerability has been resolved: time/debug: Fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...
DEBIAN-CVE-2023-53403
In the Linux kernel, the following vulnerability has been resolved: time/debug: Fix memory leak with using debugfslookup When calling debugfslookup the result must have dput called on it, otherwise the memory will leak over time. To make things simpler, just call debugfslookupandremove instead...