EUVD-2021-32071

Malicious code in bioql PyPI...

EUVD-2021-32479

Malicious code in bioql PyPI...

EUVD-2023-24881

Malicious code in bioql PyPI...

EUVD-2025-22621

Malicious code in bioql PyPI...

EUVD-2024-30781

Malicious code in bioql PyPI...

EUVD-2024-21873

Malicious code in bioql PyPI...

EUVD-2021-33021

Malicious code in bioql PyPI...

EUVD-2021-32073

Malicious code in bioql PyPI...

EUVD-2022-36078

Malicious code in bioql PyPI...

EUVD-2025-2628

Malicious code in bioql PyPI...

EUVD-2024-21874

Malicious code in bioql PyPI...

EUVD-2025-5979

Malicious code in bioql PyPI...

EUVD-2023-27557

Malicious code in bioql PyPI...

EUVD-2021-7710

Malicious code in bioql PyPI...

EUVD-2022-52384

Malicious code in bioql PyPI...

PT-2025-49055

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw within the mm/damon/sysfs interface. This interface dynamically allocates a damon ctx object for testing the validity of inputs for online DAMON...

CVE-2025-60019

glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location...

CVE-2025-60019

glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location...

CVE-2025-60019 Glib-networking: uninitialized memory dereferences on glib-networking through glib-networking/tls/openssl/gtlsbio.c via g_tls_bio_new_from_iostream() and g_tls_bio_new_from_datagram_based()

glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location...

CVE-2025-60019

glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location...