VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

anki: vulnerability history, versions and safety

anki is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 55 releases, from Jul 2024 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
6 vulnerabilities recorded H1 M1 L1 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 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 anki vulnerabilities

Vulert verdict on anki 26.9.3 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 26.9.3 — unaffected i
  • Vulnerabilities on record 6 over 1 year · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.6 i
  • With no published fix 0 i
  • Depended on by 15 packages i
  • Stars 32,113 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence AGPL-3.0-or-later 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 anki, 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
26.9.3 23 Sep 2026 none AGPL-3.0-or-later — Details →
26.9.2 15 Sep 2026 none AGPL-3.0-or-later — Details →
26.9.1 15 Sep 2026 none AGPL-3.0-or-later — Details →
26.9.0 14 Sep 2026 none AGPL-3.0-or-later — Details →
26.9.0b3 10 Sep 2026 none AGPL-3.0-or-later — Details →
26.9.0b2 04 Sep 2026 none AGPL-3.0-or-later — Details →
26.9.0b1 25 Aug 2026 none AGPL-3.0-or-later — Details →
26.8.1 05 Aug 2026 none AGPL-3.0-or-later — Details →
26.8.0 01 Aug 2026 none AGPL-3.0-or-later — Details →
26.8.0b2 25 Jul 2026 none AGPL-3.0-or-later — Details →
26.8.0b1 13 Jul 2026 none AGPL-3.0-or-later — Details →
25.9.5 18 Jun 2026 none AGPL-3.0-or-later — Details →
26.5.0 16 Jun 2026 none AGPL-3.0-or-later — Details →
26.5.0b2 30 May 2026 none AGPL-3.0-or-later — Details →
26.5.0b1 11 May 2026 none AGPL-3.0-or-later — Details →
25.9.4 08 May 2026 none AGPL-3.0-or-later — Details →
25.9.3 07 May 2026 none AGPL-3.0-or-later — Details →
25.9.2 17 Sep 2025 none AGPL-3.0-or-later — Details →
25.9.1 17 Sep 2025 none AGPL-3.0-or-later — Details →
25.9.0 06 Sep 2025 none AGPL-3.0-or-later — Details →
25.9.0rc1 04 Sep 2025 none AGPL-3.0-or-later — Details →
25.8.0b5 08 Aug 2025 none AGPL-3.0-or-later — Details →
25.8.0b4 28 Jul 2025 none AGPL-3.0-or-later — Details →
25.8.0b3 28 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.5 25 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.4 24 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.3 21 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.3rc1 18 Jul 2025 none AGPL-3.0-or-later — Details →
25.8.0b2 15 Jul 2025 none AGPL-3.0-or-later — Details →
25.8.0b1 07 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.2 07 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.1 04 Jul 2025 none AGPL-3.0-or-later — Details →
25.7.0 04 Jul 2025 none AGPL-3.0-or-later — Details →
25.6.0b7 29 Jun 2025 none AGPL-3.0-or-later — Details →
25.6.0b6 27 Jun 2025 none AGPL-3.0-or-later — Details →
25.6.0b5 21 Jun 2025 none AGPL-3.0-or-later — Details →
25.6.0b4 20 Jun 2025 none AGPL-3.0-or-later — Details →
25.6.0b3 20 Jun 2025 none AGPL-3.0-or-later — Details →
25.6.0b1 06 Jun 2025 none AGPL-3.0 — Details →
25.2.7 06 Jun 2025 none AGPL-3.0 — Details →
25.2.6 01 Jun 2025 none AGPL-3.0 — Details →
25.2.5 15 May 2025 none AGPL-3.0 — Details →
25.5.0b2 27 Apr 2025 none AGPL-3.0 — Details →
25.5.0b1 25 Apr 2025 none AGPL-3.0 — Details →
25.2.4 24 Apr 2025 none AGPL-3.0 — Details →
25.2.3 23 Apr 2025 none AGPL-3.0 — Details →
25.2.2 23 Apr 2025 none AGPL-3.0 — Details →
25.2.1 17 Apr 2025 none AGPL-3.0 — Details →
25.2.0 11 Feb 2025 none AGPL-3.0 — Details →
25.2.0rc1 07 Feb 2025 none AGPL-3.0 — Details →
25.1.0rc1 26 Jan 2025 none AGPL-3.0 — Details →
25.1.0b1 17 Jan 2025 none AGPL-3.0 — Details →
24.11.0 29 Nov 2024 none AGPL-3.0 — Details →
24.11.0rc2 26 Nov 2024 none AGPL-3.0 — Details →
24.11.0rc1 08 Nov 2024 none AGPL-3.0 — Details →
24.10.0rc2 05 Nov 2024 none AGPL-3.0 — Details →
24.10.0rc1 26 Oct 2024 none AGPL-3.0 — Details →
24.10.0b4 21 Oct 2024 none AGPL-3.0 — Details →
24.10.0b3 11 Oct 2024 none AGPL-3.0 — Details →
24.10.0b2 04 Oct 2024 none AGPL-3.0 — Details →
24.10.0b1 27 Sep 2024 none AGPL-3.0 — Details →
24.6.3 03 Jul 2024 none AGPL-3.0 — Details →
24.6.2 09 Jun 2024 none AGPL-3.0 — Details →
24.6.1 08 Jun 2024 none AGPL-3.0 — Details →
24.6.0 07 Jun 2024 none AGPL-3.0 — Details →
24.4.1 19 Apr 2024 H1 M1 L1 U3 AGPL-3.0 Yes Details →
24.4.0 31 Mar 2024 H1 M1 L1 U3 AGPL-3.0 Yes Details →
24.4.0rc2 20 Mar 2024 H1 M1 L1 U3 AGPL-3.0 Yes Details →
24.4.0rc1 09 Mar 2024 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.12.1 28 Dec 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.12.0 25 Dec 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.12.0rc1 22 Dec 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.12.0b3 13 Dec 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.12.0b2 08 Dec 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.12.0b1 29 Nov 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.1 10 Nov 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.1rc2 07 Nov 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.1rc1 04 Nov 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0 31 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0rc3 28 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0rc2 26 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0rc1 20 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0b6 14 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0b5 13 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0b4 03 Oct 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0b3 27 Sep 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0b2 25 Sep 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
23.10.0b1 24 Sep 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.66 24 Aug 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.66rc1 19 Aug 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.66b1 26 Jul 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.65 04 Jun 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.64 24 May 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.63 15 May 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.62 01 May 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.62rc1 28 Apr 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.62b1 12 Apr 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.61 31 Mar 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.61b2 19 Mar 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.61b1 11 Mar 2023 H1 M1 L1 U3 AGPL-3.0 Yes Details →
2.1.60 22 Feb 2023 H1 M1 L1 U3 — Yes Details →
2.1.58 17 Feb 2023 H1 M1 L1 U3 — Yes Details →
2.1.57 29 Jan 2023 H1 M1 L1 U3 — Yes Details →
2.1.57rc1 26 Jan 2023 H1 M1 L1 U3 — Yes Details →
2.1.57b1 18 Jan 2023 H1 M1 L1 U3 — Yes Details →
2.1.56 09 Jan 2023 H1 M1 L1 U3 — Yes Details →
2.1.56rc1 04 Jan 2023 H1 M1 L1 U3 — Yes Details →
2.1.55 16 Dec 2022 H1 M1 L1 U3 — Yes Details →
2.1.55rc2 14 Dec 2022 H1 M1 L1 U3 — Yes Details →
2.1.55rc1 09 Dec 2022 H1 M1 L1 U3 — Yes Details →
2.1.55b7 04 Dec 2022 H1 M1 L1 U3 — Yes Details →
2.1.55b6 28 Nov 2022 H1 M1 L1 U3 — Yes Details →
2.1.55b4 05 Nov 2022 H1 M1 L1 U3 — Yes Details →
2.1.55b3 29 Oct 2022 H1 M1 L1 U3 — Yes Details →
2.1.55b2 12 Oct 2022 H1 M1 L1 U3 — Yes Details →
2.1.55b1 28 Sep 2022 H1 M1 L1 U3 — Yes Details →
2.1.54 24 Jun 2022 H1 M1 L1 U3 — Yes Details →
2.1.54rc3 22 Jun 2022 H1 M1 L1 U3 — Yes Details →
2.1.54rc2 21 Jun 2022 H1 M1 L1 U3 — Yes Details →
2.1.54rc1 18 Jun 2022 H1 M1 L1 U3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for anki

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Script Execution Vulnerability in Ankitects Anki 9.6 high 24.06 22 Jul 2024
CVE-2024-26020: Anki Arbitrary Script Execution Vulnerability 9.6 critical 24.06 07 Jul 2026
CVE-2024-29073: Anki Latex Incomplete Blocklist Vulnerability 5.3 medium 24.6 22 Jul 2024
CVE-2024-29073: Anki Package Vulnerability Leading to Arbitrary File Read 5.3 medium 24.6 07 Jul 2026
CVE-2024-32152: Ankitects Anki LaTeX Blocklist Bypass vulnerability 3.1 low 24.6 22 Jul 2024

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 anki

Is anki safe to use?

Vulert records 6 vulnerabilities for anki in PyPI: 0 critical, 1 high, 1 medium and 1 low, plus 3 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 anki's Vulert package health score?

Vulert scores anki 76/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 anki affected?

No. 26.9.3, 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 anki should I use?

26.9.3 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 anki have?

6 vulnerabilities are recorded for anki in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 1 low, plus 3 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 anki vulnerabilities disclosed?

3 vulnerabilities were recorded for anki in the last 12 months, and the oldest entry in this database dates to 22 Jul 2024. 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 anki 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 anki for upcoming vulnerabilities?

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