Vulnerability Database · PyPI · asyncmy · Version
asyncmy 0.2.10rc1
0.2.10rc1 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 2 High 0 Medium 0 Low 0 Unrated 0
-
Released 24 Apr 2024
Licence Apache-2.0
Also known from other sources 2
Newer releases 30
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
asyncmy 0.2.10rc1 vulnerabilities
2 vulnerabilities cover asyncmy 0.2.10rc1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2025-65896: asyncmy SQL Injection Vulnerability via Crafted Dict Keys | 9.8 critical | No fix published | 29 Jun 2026 |
| CVE-2025-65896: asyncmy SQL Injection Vulnerability via Crafted Dict Keys | 9.8 critical | No fix published | 02 Dec 2025 |
Looking for another version, or everything Vulert holds for asyncmy?
Questions
About asyncmy 0.2.10rc1
Is asyncmy 0.2.10rc1 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover asyncmy 0.2.10rc1: 2 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.2.10rc1 the latest release of asyncmy?
No. 0.2.10rc1 was published 24 Apr 2024, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor asyncmy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the asyncmy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.