VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

asyncmy: vulnerability history, versions and safety

asyncmy is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 30 releases, from Dec 2025 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all asyncmy vulnerabilities

Vulert verdict on asyncmy 0.2.17 i

Updated on 23 Oct 2026

Careful: 0.2.17 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.2.17 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 70 packages i
  • Stars 391 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for asyncmy, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.2.17 22 Oct 2026 C1 U1 Apache-2.0 No Details →
0.2.16 06 Oct 2026 C1 U1 Apache-2.0 No Details →
0.2.15 21 Sep 2026 C1 U1 Apache-2.0 No Details →
0.2.14 12 Aug 2026 C1 U1 Apache-2.0 No Details →
0.2.13 06 Aug 2026 C1 U1 Apache-2.0 No Details →
0.2.12 06 Aug 2026 C1 U1 Apache-2.0 No Details →
0.2.11 15 Jan 2026 U1 Apache-2.0 No Details →
0.2.10 13 Dec 2024 U1 Apache-2.0 No Details →
0.2.10rc1 24 Apr 2024 U1 Apache-2.0 No Details →
0.2.9 29 Nov 2023 U1 Apache-2.0 No Details →
0.2.8 01 Jun 2023 U1 Apache-2.0 No Details →
0.2.8rc2 17 May 2023 U1 Apache-2.0 No Details →
0.2.8rc1 11 Apr 2023 U1 Apache-2.0 No Details →
0.2.7 15 Feb 2023 U1 Apache-2.0 No Details →
0.2.7rc6 03 Feb 2023 U1 Apache-2.0 No Details →
0.2.5 30 Mar 2022 U1 Apache-2.0 No Details →
0.2.4 27 Mar 2022 U1 Apache-2.0 No Details →
0.2.3 15 Oct 2021 U1 Apache-2.0 No Details →
0.2.2 11 Oct 2021 U1 Apache-2.0 No Details →
0.2.1 08 Oct 2021 U1 Apache-2.0 No Details →
0.2.0 18 Sep 2021 U1 Apache-2.0 No Details →
0.1.9 07 Sep 2021 U1 Apache-2.0 No Details →
0.1.8 20 Aug 2021 U1 Apache-2.0 No Details →
0.1.7 09 Jun 2021 U1 Apache-2.0 No Details →
0.1.6 21 May 2021 U1 Apache-2.0 No Details →
0.1.5 12 Apr 2021 U1 Apache-2.0 No Details →
0.1.4 17 Mar 2021 U1 Apache-2.0 No Details →
0.1.3 11 Mar 2021 U1 Apache-2.0 No Details →
0.1.2 10 Mar 2021 U1 Apache-2.0 No Details →
0.1.1 09 Mar 2021 U1 Apache-2.0 No Details →

All 30 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for asyncmy

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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 02 Dec 2025
CVE-2025-65896: asyncmy SQL Injection Vulnerability via Crafted Dict Keys 9.8 critical No fix published 29 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About asyncmy

Is asyncmy safe to use?

Vulert records 2 vulnerabilities for asyncmy in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is asyncmy's Vulert package health score?

Vulert scores asyncmy 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of asyncmy affected?

Yes. 0.2.17, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does asyncmy have?

2 vulnerabilities are recorded for asyncmy in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new asyncmy vulnerabilities disclosed?

2 vulnerabilities were recorded for asyncmy in the last 12 months, and the oldest entry in this database dates to 02 Dec 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of asyncmy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.