EUVD-2007-0669

Malware in sbrugna...

EUVD-2003-0994

Malware in sbrugna...

EUVD-2007-0670

Malware in sbrugna...

smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path

...

EUVD-2024-22938

Malicious code in bioql PyPI...

EUVD-2023-44638

Malicious code in bioql PyPI...

EUVD-2025-31881

Malicious code in bioql PyPI...

EUVD-2022-0887

Malicious code in bioql PyPI...

EUVD-2010-0464

Malicious code in bioql PyPI...

EUVD-2025-21876

Malicious code in bioql PyPI...

EUVD-2023-39333

Malicious code in bioql PyPI...

EUVD-2022-2698

Malicious code in bioql PyPI...

EUVD-2021-27699

Malicious code in bioql PyPI...

EUVD-2023-30296

Malicious code in bioql PyPI...

EUVD-2025-27360

Malicious code in bioql PyPI...

EUVD-2024-46962

Malicious code in bioql PyPI...

EUVD-2024-36402

Malicious code in bioql PyPI...

Exploit for Improper Restriction of XML External Entity Reference in Jetbrains Ktor

CVE-2023-45612 - https://nvd.nist.gov/vuln/detail/CVE-2023-456...

SUSE CVE-2023-53517

In the Linux kernel, the following vulnerability has been resolved: tipc: do not update mtu if msgmax is too small in mtu negotiation When doing link mtu negotiation, a malicious peer may send Activate msg with a very small mtu, e.g. 4 in Shuang's testing, without checking for the minimum mtu,...

CVE-2023-53517

Summary: CVE-2023-53517 affects the Linux kernel’s TIPC MTU negotiation logic. A malicious peer could send an Activate message with an extremely small MTU (e.g., 4), causing l->mtu to drop to 4 in tipc_link_proto_rcv() and leading to an overflow when computing MTU-related values (e.g., 4 - INT...