VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aim: vulnerability history, versions and safety

aim is a package in the PyPI ecosystem. Vulert records 40 vulnerabilities for it across 120 releases, from Nov 2021 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
40 vulnerabilities recorded C4 H9 M6 L1 U20
i
38 with no fix published

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

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

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aim vulnerabilities

Vulert verdict on aim 4.0.3 i

Updated on 23 Oct 2026

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

Package health score 32/100
  • Security Unfixed issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Not enough data

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 4.0.3 — affected i
  • Vulnerabilities on record 40 over 4 years · 19 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 38 i
  • Depended on by 18 packages i
  • Last release 36 months ago i
  • Licence non-standard 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 aim, 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
3.30.0.dev20250611 11 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250610 10 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250609 09 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250608 08 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250607 07 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250606 06 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250605 05 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250604 04 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250603 03 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250602 02 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250601 01 Jun 2025 M1 U1 non-standard No Details →
3.30.0.dev20250531 31 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250530 30 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250529 29 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250528 28 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250527 27 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250526 26 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250525 25 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250524 24 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250523 23 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250522 22 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250521 21 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250520 20 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250519 19 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250518 18 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250517 17 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250516 16 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250515 15 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250513 13 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250512 12 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250511 11 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250510 10 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250509 09 May 2025 M1 U1 non-standard No Details →
3.30.0.dev20250508 08 May 2025 M1 U1 non-standard No Details →
3.29.1 08 May 2025 M1 L1 U2 non-standard No Details →
3.29.0 08 May 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250419 19 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250418 18 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250417 17 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250416 16 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250415 15 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250413 13 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250412 12 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250411 11 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250410 10 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250409 09 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250408 08 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250407 07 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250406 06 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250405 05 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250404 04 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250403 03 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250402 02 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250401 01 Apr 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250331 31 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250330 30 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250329 29 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250328 28 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250327 28 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250323 23 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250322 22 Mar 2025 M1 L1 U2 non-standard No Details →
3.29.0.dev20250321 21 Mar 2025 M1 L1 U2 non-standard No Details →
3.28.0 21 Mar 2025 M1 L1 U2 non-standard No Details →
3.27.0 18 Dec 2024 C1 M1 L1 U3 Apache-2.0 No Details →
3.26.1 03 Dec 2024 C1 M1 L1 U3 Apache-2.0 No Details →
3.25.1 06 Nov 2024 C1 M1 L1 U3 Apache-2.0 No Details →
3.26.0.dev1 05 Nov 2024 C1 M1 L1 U3 Apache-2.0 No Details →
3.25.0 02 Oct 2024 C2 H3 M2 L1 U8 Apache-2.0 No Details →
3.24.0 14 Aug 2024 C2 H3 M3 L1 U9 Apache-2.0 No Details →
3.23.0 15 Jul 2024 C2 H5 M3 L1 U11 Apache-2.0 No Details →
3.22.0 20 Jun 2024 C2 H7 M4 L1 U14 Apache-2.0 No Details →
3.21.0 17 Jun 2024 C2 H7 M4 L1 U14 Apache-2.0 No Details →
3.20.1 03 Jun 2024 C2 H7 M4 L1 U14 Apache-2.0 No Details →
3.19.3 17 Apr 2024 C3 H8 M6 L1 U18 Apache-2.0 No Details →
3.19.2 22 Mar 2024 C3 H8 M6 L1 U18 Apache-2.0 No Details →
3.19.1 14 Mar 2024 C3 H8 M6 L1 U18 Apache-2.0 No Details →
3.19.0 13 Mar 2024 C3 H8 M6 L1 U18 Apache-2.0 No Details →
3.18.1 07 Feb 2024 C3 H8 M6 L1 U18 Apache-2.0 No Details →
3.18.0 06 Feb 2024 C3 H8 M6 L1 U18 Apache-2.0 No Details →
3.17.5rc4 10 Jan 2024 C3 H9 M6 L1 U19 Apache-2.0 No Details →
3.17.5rc3 09 Jan 2024 C3 H9 M6 L1 U19 Apache-2.0 No Details →
3.17.5rc2 09 Jan 2024 C3 H9 M6 L1 U19 Apache-2.0 No Details →
3.17.5rc1 08 Jan 2024 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.3 04 Oct 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.2 03 Oct 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.1 03 Oct 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0 27 Sep 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0b1 27 Sep 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a18 12 Sep 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a17 15 Aug 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a16 02 Aug 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a15 25 Jul 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a14 14 Jul 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a13 12 Jul 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0.dev6 12 Jul 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a12 21 Jun 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a10 19 Jun 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a9 16 Jun 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
4.0.0a7 05 Jun 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
3.17.5 02 Jun 2023 C3 H9 M6 L1 U19 Apache-2.0 No Details →
3.18.0.dev5 23 May 2023 C3 H8 M6 L1 U18 — No Details →
3.17.4 04 May 2023 C3 H9 M6 L1 U19 — No Details →
3.18.0.dev4 03 May 2023 C3 H8 M6 L1 U18 — No Details →
3.18.0.dev3 02 May 2023 C3 H8 M6 L1 U18 — No Details →
3.18.0.dev2 02 May 2023 C3 H8 M6 L1 U18 — No Details →
3.17.3 06 Apr 2023 C3 H9 M6 L1 U19 — No Details →
3.17.2 28 Mar 2023 C3 H9 M6 L1 U19 — No Details →
3.17.1 24 Mar 2023 C3 H9 M6 L1 U19 — No Details →
3.17.0 24 Mar 2023 C3 H9 M6 L1 U19 — No Details →
3.16.2 02 Mar 2023 C3 H9 M6 L1 U19 — No Details →
3.16.1 27 Feb 2023 C3 H9 M6 L1 U19 — No Details →
3.16.0 03 Feb 2023 C3 H9 M6 L1 U19 — No Details →
3.15.2 23 Dec 2022 C3 H9 M6 L1 U19 — No Details →
3.15.1 01 Dec 2022 C3 H9 M6 L1 U19 — No Details →
3.15.0 26 Nov 2022 C3 H9 M6 L1 U19 — No Details →
3.14.4 11 Nov 2022 C2 H8 M6 L1 U17 — No Details →
3.14.3 29 Oct 2022 C2 H8 M6 L1 U17 — No Details →
3.14.2 28 Oct 2022 C2 H8 M6 L1 U17 — No Details →
3.14.1 07 Oct 2022 C2 H8 M6 L1 U17 — No Details →
3.14.0 06 Oct 2022 C2 H8 M6 L1 U17 — No Details →

The newest 120 of 210 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2024 5
  • 2025 14
  • 2026 19

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

03 Vulnerabilities

Recorded vulnerabilities for aim

The 5 most severe of 40 vulnerabilities recorded for this package

Search all 40 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-2195: Aim Package Remote Code Execution Vulnerability 9.8 critical No fix published 29 Jun 2026
Aim Web API Remote Code Execution Vulnerability 9.8 critical No fix published 10 Apr 2024
CVE-2024-6829: Aim Package Vulnerability Allows Arbitrary File Extraction 9.1 critical No fix published 20 Mar 2025
CVE-2024-8769: Aim Package Path Traversal Vulnerability Leading to Arbitrary File Deletion 9.1 critical No fix published 20 Mar 2025
CVE-2024-8769: Aim Package Arbitrary File Deletion via Path Traversal 9.1 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 aim

Is aim safe to use?

Vulert records 40 vulnerabilities for aim in PyPI: 4 critical, 9 high, 6 medium and 1 low, plus 20 not yet rated. 38 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is aim's Vulert package health score?

Vulert scores aim 32/100, which reads as risky. 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 aim affected?

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

Which version of aim should I use?

4.0.0.dev6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does aim have?

40 vulnerabilities are recorded for aim in the PyPI ecosystem: 4 critical, 9 high, 6 medium and 1 low, plus 20 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 aim vulnerabilities disclosed?

19 vulnerabilities were recorded for aim in the last 12 months, and the oldest entry in this database dates to 23 Nov 2021. 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 aim 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 aim for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the aim version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.