VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aleksis-core: vulnerability history, versions and safety

aleksis-core is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 37 releases, from Jun 2022 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
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 06 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aleksis-core vulnerabilities

Vulert verdict on aleksis-core 4.1.0.dev2 i

Updated on 23 Oct 2026

Good news: 4.1.0.dev2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 84/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

What to do: Stay on 4.1.0.dev2 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.1.0.dev2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.1.0.dev2 — unaffected i
  • Vulnerabilities on record 2 over 4 years · 1 in the last year i
  • Latest disclosure 06 Jul 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Last release 12 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 aleksis-core, 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
4.1.0.dev2 11 Oct 2025 none non-standard — Details →
4.0.4 29 Jul 2025 none non-standard — Details →
4.1.0.dev1 27 Jul 2025 none non-standard — Details →
4.1.0.dev0 22 Jun 2025 none non-standard — Details →
4.0.3 11 Jun 2025 none non-standard — Details →
4.0.2 21 May 2025 none non-standard — Details →
4.0.1 16 Apr 2025 none non-standard — Details →
4.0.0 30 Mar 2025 none non-standard — Details →
3.2.2 18 Jan 2025 none non-standard — Details →
3.1.7 18 Jan 2025 none non-standard — Details →
4.0.0.dev15 01 Dec 2024 none non-standard — Details →
4.0.0.dev13 01 Sep 2024 none non-standard — Details →
4.0.0.dev12 29 Aug 2024 none non-standard — Details →
4.0.0.dev11 14 Aug 2024 none non-standard — Details →
3.2.1 27 Jun 2024 none non-standard — Details →
3.1.6 27 Jun 2024 none non-standard — Details →
4.0.0.dev10 10 Jun 2024 none non-standard — Details →
4.0.0.dev9 22 May 2024 none non-standard — Details →
4.0.0.dev8 07 May 2024 none non-standard — Details →
4.0.0.dev7 23 Apr 2024 none non-standard — Details →
4.0.0.dev6 04 Apr 2024 none non-standard — Details →
4.0.0.dev5 29 Feb 2024 none non-standard — Details →
4.0.0.dev4 17 Feb 2024 none non-standard — Details →
4.0.0.dev3 26 Jan 2024 none non-standard — Details →
4.0.0.dev2 10 Jan 2024 none non-standard — Details →
4.0.0.dev1 02 Jan 2024 none non-standard — Details →
3.2.0 29 Dec 2023 none non-standard — Details →
3.1.5 02 Sep 2023 none non-standard — Details →
3.1.4 20 Jul 2023 none non-standard — Details →
3.1.3 18 Jul 2023 none non-standard — Details →
3.1.2 05 Jul 2023 none non-standard — Details →
3.1.1 02 Jul 2023 none non-standard — Details →
3.1.0 31 May 2023 none non-standard — Details →
3.0.0 12 May 2023 none non-standard — Details →
2.12.4 19 Mar 2023 none non-standard — Details →
3.0.0b3 19 Mar 2023 none non-standard — Details →
3.0.0b2 09 Mar 2023 none non-standard — Details →
2.11.2 07 Mar 2023 none non-standard — Details →
2.10.3 07 Mar 2023 none non-standard — Details →
2.12.3 07 Mar 2023 none non-standard — Details →
3.0.0b1 27 Feb 2023 none non-standard — Details →
3.0.0b0 15 Feb 2023 none non-standard — Details →
3.0.0.dev3 23 Jan 2023 none non-standard — Details →
2.12.2 18 Dec 2022 none non-standard — Details →
3.0.0.dev2 12 Nov 2022 none non-standard — Details →
2.12.1 06 Nov 2022 none non-standard — Details →
2.12.0 04 Nov 2022 none non-standard — Details →
2.11.1 31 Aug 2022 none non-standard — Details →
2.11.0 27 Aug 2022 none non-standard — Details →
2.10.2 25 Aug 2022 none non-standard — Details →
3.0.0.dev1 18 Aug 2022 none non-standard — Details →
3.0.0.dev0 06 Aug 2022 none non-standard — Details →
2.10.1 24 Jul 2022 none non-standard — Details →
2.10.0 25 Jun 2022 none non-standard — Details →
2.7.6 22 Jun 2022 M1 U1 non-standard Yes Details →
2.7.5 05 Jun 2022 M1 U1 non-standard Yes Details →
2.9.0 25 May 2022 none non-standard — Details →
2.8.2.dev1 29 Mar 2022 M1 U1 non-standard Yes Details →
2.8.2.dev0 24 Mar 2022 M1 U1 non-standard Yes Details →
2.8.1 13 Mar 2022 M1 U1 non-standard Yes Details →
2.8.1.dev0 12 Mar 2022 M1 U1 non-standard Yes Details →
2.8.0 11 Mar 2022 M1 U1 non-standard Yes Details →
2.7.4 08 Feb 2022 M1 U1 non-standard Yes Details →
2.7.3 03 Feb 2022 M1 U1 non-standard Yes Details →
2.7.2 31 Jan 2022 M1 U1 non-standard Yes Details →
2.7.1 28 Jan 2022 M1 U1 non-standard Yes Details →
2.7.0 24 Jan 2022 M1 U1 non-standard Yes Details →
2.3.2 24 Jan 2022 M1 U1 non-standard Yes Details →
2.6.0 10 Jan 2022 M1 U1 non-standard Yes Details →
2.5.0 02 Jan 2022 M1 U1 non-standard Yes Details →
2.4.0 24 Dec 2021 M1 U1 non-standard Yes Details →
2.3.1 17 Dec 2021 M1 U1 non-standard Yes Details →
2.3.0 15 Dec 2021 M1 U1 non-standard Yes Details →
2.2.1 02 Dec 2021 M1 U1 non-standard Yes Details →
2.2.0 29 Nov 2021 M1 U1 non-standard Yes Details →
2.1.1 15 Nov 2021 M1 U1 non-standard Yes Details →
2.1.0 05 Nov 2021 M1 U1 non-standard Yes Details →
2.1.0.dev0 02 Nov 2021 M1 U1 non-standard Yes Details →
2.0.0 29 Oct 2021 M1 U1 non-standard Yes Details →
2.0.0rc7 18 Oct 2021 M1 U1 non-standard Yes Details →
2.0.0rc6 11 Oct 2021 M1 U1 non-standard Yes Details →
2.0.0rc5 01 Sep 2021 M1 U1 non-standard Yes Details →
2.0.0rc4 01 Aug 2021 M1 U1 non-standard Yes Details →
2.0.0rc3 29 Jul 2021 M1 U1 non-standard Yes Details →
2.0.0rc2 24 Jun 2021 M1 U1 non-standard Yes Details →
2.0.0rc1 23 Jun 2021 M1 U1 non-standard Yes Details →
2.0.0b2 15 Jun 2021 M1 U1 non-standard Yes Details →
2.0.0b1 02 Jun 2021 M1 U1 non-standard Yes Details →
2.0.0b0 21 May 2021 M1 U1 non-standard Yes Details →
2.0.0a4 13 Feb 2021 M1 U1 non-standard Yes Details →
2.0.0a3 10 Jan 2021 M1 U1 non-standard Yes Details →
2.0.0a3.dev0 17 Nov 2020 M1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for aleksis-core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-29773: Access control issue in AlekSIS-Core 6.5 medium 2.9 04 Jun 2022
CVE-2022-29773: AlekSIS-Core Access Control Vulnerability 6.5 medium 2.9 06 Jul 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 aleksis-core

Is aleksis-core safe to use?

Vulert records 2 vulnerabilities for aleksis-core in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is aleksis-core's Vulert package health score?

Vulert scores aleksis-core 84/100, which reads as in good shape. 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).

Is the latest version of aleksis-core affected?

No. 4.1.0.dev2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of aleksis-core should I use?

4.1.0.dev2 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 aleksis-core have?

2 vulnerabilities are recorded for aleksis-core in the PyPI ecosystem: 0 critical, 0 high, 1 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 aleksis-core vulnerabilities disclosed?

1 vulnerability was recorded for aleksis-core in the last 12 months, and the oldest entry in this database dates to 04 Jun 2022. 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 aleksis-core 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 aleksis-core for upcoming vulnerabilities?

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