aiopogo (>=2.0.1, <=2.1.0b0), aiosparql (>=0.0.0, <=0.10.0a3) +6 more potentially affected by CVE-2025-69223 via aiohttp (2.1.0)

aiohttp PYPI version 2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - aiopogo =2.0.1, =0.0.0, =0.46.0, =0.4.0, =0.0.2, =0.4.4 Source cves: CVE-2025-69223 Source advisory: OSV:PYSEC-2026-1101...

aiopogo (>=2.0.1, <=2.1.0b0), aiosparql (>=0.0.0, <=0.10.0a3) +6 more potentially affected by CVE-2026-54279 via aiohttp (2.1.0)

aiohttp PYPI version 2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - aiopogo =2.0.1, =0.0.0, =0.46.0, =0.4.0, =0.0.2, =0.4.4 Source cves: CVE-2026-54279 Source advisory: OSV:PYSEC-2026-2112...

aiopogo (>=2.0.1, <=2.1.0b0), aiosparql (>=0.0.0, <=0.10.0a3) +6 more potentially affected by CVE-2026-54273 via aiohttp (2.1.0)

aiohttp PYPI version 2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - aiopogo =2.0.1, =0.0.0, =0.46.0, =0.4.0, =0.0.2, =0.4.4 Source cves: CVE-2026-54273 Source advisory: OSV:PYSEC-2026-2107...

aiopogo (>=2.0.1, <=2.1.0b0), aiosparql (>=0.0.0, <=0.10.0a3) +6 more potentially affected by CVE-2026-34993 via aiohttp (2.1.0)

aiohttp PYPI version 2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - aiopogo =2.0.1, =0.0.0, =0.46.0, =0.4.0, =0.0.2, =0.4.4 Source cves: CVE-2026-34993 Source advisory: OSV:PYSEC-2026-2104...

aiopogo (>=2.0.1, <=2.1.0b0), aiosparql (>=0.0.0, <=0.10.0a3) +6 more potentially affected by CVE-2026-34514 via aiohttp (2.1.0)

aiohttp PYPI version 2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - aiopogo =2.0.1, =0.0.0, =0.46.0, =0.4.0, =0.0.2, =0.4.4 Source cves: CVE-2026-34514 Source advisory: OSV:GHSA-2VRM-GR82-F7M5...

aiopogo (>=2.0.1, <=2.1.0b0), aiosparql (>=0.0.0, <=0.10.0a3) +6 more potentially affected by CVE-2026-34519 via aiohttp (2.1.0)

aiohttp PYPI version 2.1.0 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - aiopogo =2.0.1, =0.0.0, =0.46.0, =0.4.0, =0.0.2, =0.4.4 Source cves: CVE-2026-34519 Source advisory: OSV:PYSEC-2026-2101...

MAL-2025-8996 Malicious code in @malware-test-teens-satyr-rigor-esker/test-mlw3-teens-satyr-rigor-esker (npm)

The package @malware-test-teens-satyr-rigor-esker/test-mlw3-teens-satyr-rigor-esker was found to contain malicious code...

Malicious code in @malware-test-teens-satyr-rigor-esker/test-mlw3-teens-satyr-rigor-esker (npm)

The package @malware-test-teens-satyr-rigor-esker/test-mlw3-teens-satyr-rigor-esker was found to contain malicious code...

MAL-2025-36420 Malicious code in test-mlw2-teens-satyr-rigor-esker (npm)

The package test-mlw2-teens-satyr-rigor-esker was found to contain malicious code...

MAL-2025-34810 Malicious code in test-mlw1-teens-satyr-rigor-esker (npm)

The package test-mlw1-teens-satyr-rigor-esker was found to contain malicious code...

Malicious code in test-mlw1-teens-satyr-rigor-esker (npm)

The package test-mlw1-teens-satyr-rigor-esker was found to contain malicious code...

Malicious code in test-mlw2-teens-satyr-rigor-esker (npm)

The package test-mlw2-teens-satyr-rigor-esker was found to contain malicious code...

CVE-2023-3652

creationtimestamp| type| source ---|---|--- 2023-08-08 18:14:14+00:00| seen| https://t.me/cibsecurity/67998...

Owner of project NFT has no purpose

Lines of code Vulnerability details Owner of project NFT has no purpose Impact Creating a new project mints a NFT to the sender builder. The builder of a project has special permissions and is required to perform various tasks. However, if the minted NFT is transferred to a different address, the...

On Isogenies Verifiable Delay Functions (VDF)

This continues the post frompart 1. In the previous post we discussed about Verifiable Delay Functions. Here is a quick summary of what we discussed in the first part: We covered the definition of Verifiable Delay Functions VDF. We have seen a short history of how this idea slowly developed. We...

Medical Devices Should Withstand Rigor, Expert Says

CAMBRIDGE, Ma.—When it comes to managing medical device security risk, hospital administrators should focus on weathering the storm and not necessarily prevention, Dr. Kevin Fu, a noted medical device security expert, encouraged this week. “How do you fail gracefully when things go wrong? Will yo...