Vulnerability Database · PyPI · Package report

manila: vulnerability history, versions and safety

manila is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 19 releases, from Mar 2020 to May 2022. 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 H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on manila 23.0.1 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 23.0.1 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Last release this month 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 manila, 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
20.0.3 21 Oct 2026 none non-standard — Details →
22.0.2 21 Oct 2026 none Apache-2.0 — Details →
21.0.3 21 Oct 2026 none non-standard — Details →
23.0.1 21 Oct 2026 none Apache-2.0 — Details →
23.0.0 30 Sep 2026 none Apache-2.0 — Details →
23.0.0.0rc1 11 Sep 2026 none Apache-2.0 — Details →
20.0.2 03 Sep 2026 none non-standard — Details →
22.0.1 03 Sep 2026 none Apache-2.0 — Details →
21.0.2 03 Sep 2026 none non-standard — Details →
22.0.0 01 Apr 2026 none Apache-2.0 — Details →
22.0.0.0rc2 18 Mar 2026 none Apache-2.0 — Details →
19.1.1 19 Feb 2026 none non-standard — Details →
20.0.1 16 Feb 2026 none non-standard — Details →
21.0.1 16 Feb 2026 none non-standard — Details →
21.0.0 01 Oct 2025 none Apache-2.0 — Details →
21.0.0.0rc2 26 Sep 2025 none Apache-2.0 — Details →
21.0.0.0rc1 15 Sep 2025 none Apache-2.0 — Details →
19.1.0 01 May 2025 none Apache-2.0 — Details →
17.4.0 01 May 2025 none Apache-2.0 — Details →
18.3.0 01 May 2025 none Apache-2.0 — Details →
20.0.0 02 Apr 2025 none Apache-2.0 — Details →
20.0.0.0rc2 28 Mar 2025 none Apache-2.0 — Details →
20.0.0.0rc1 14 Mar 2025 none Apache-2.0 — Details →
16.3.0 12 Dec 2024 none non-standard — Details →
18.2.1 12 Nov 2024 none non-standard — Details →
17.3.1 12 Nov 2024 none non-standard — Details →
17.3.0 08 Nov 2024 none non-standard — Details →
18.2.0 17 Oct 2024 none non-standard — Details →
19.0.1 17 Oct 2024 none non-standard — Details →
19.0.0 02 Oct 2024 none non-standard — Details →
19.0.0.0rc2 27 Sep 2024 none non-standard — Details →
19.0.0.0rc1 13 Sep 2024 none non-standard — Details →
16.2.1 01 Aug 2024 none non-standard — Details →
15.4.1 06 May 2024 none non-standard — Details →
18.1.0 18 Apr 2024 none non-standard — Details →
18.0.1 03 Apr 2024 none non-standard — Details →
18.0.0 03 Apr 2024 none non-standard — Details →
18.0.0.0rc1 14 Mar 2024 none non-standard — Details →
14.2.0 12 Feb 2024 none non-standard — Details →
15.4.0 08 Feb 2024 none non-standard — Details →
16.2.0 01 Feb 2024 none non-standard — Details →
17.2.0 01 Feb 2024 none non-standard — Details →
15.3.0 09 Nov 2023 none non-standard — Details →
17.1.0 19 Oct 2023 none non-standard — Details →
16.1.0 12 Oct 2023 none non-standard — Details →
17.0.0 04 Oct 2023 none non-standard — Details →
17.0.0.0rc1 15 Sep 2023 none non-standard — Details →
14.1.1 28 Jul 2023 none non-standard — Details →
14.1.0 13 Apr 2023 none non-standard — Details →
13.2.0 13 Apr 2023 none non-standard — Details →
15.2.0 13 Apr 2023 none non-standard — Details →
16.0.0 22 Mar 2023 none non-standard — Details →
16.0.0.0rc1 03 Mar 2023 none non-standard — Details →
13.1.0 19 Jan 2023 none non-standard — Details →
13.0.4 05 Dec 2022 none non-standard — Details →
14.0.1 05 Dec 2022 none non-standard — Details →
15.1.0 07 Nov 2022 none non-standard — Details →
15.0.0 05 Oct 2022 none non-standard — Details →
15.0.0.0rc1 16 Sep 2022 none non-standard — Details →
11.1.2 18 Apr 2022 none non-standard — Details →
13.0.3 18 Apr 2022 none non-standard — Details →
12.1.2 18 Apr 2022 none non-standard — Details →
14.0.0 30 Mar 2022 none non-standard — Details →
14.0.0.0rc1 11 Mar 2022 none non-standard — Details →
11.1.1 10 Feb 2022 none non-standard — Details →
12.1.1 31 Jan 2022 none non-standard — Details →
13.0.2 31 Jan 2022 none non-standard — Details →
10.2.0 15 Nov 2021 none non-standard — Details →
11.1.0 12 Nov 2021 none non-standard — Details →
12.1.0 09 Nov 2021 none non-standard — Details →
13.0.1 04 Nov 2021 none non-standard — Details →
13.0.0 06 Oct 2021 none non-standard — Details →
13.0.0.0rc1 17 Sep 2021 none non-standard — Details →
10.1.0 26 Jul 2021 none non-standard — Details →
12.0.0 14 Apr 2021 none non-standard — Details →
12.0.0.0rc1 26 Mar 2021 none non-standard — Details →
10.0.2 01 Feb 2021 none non-standard — Details →
11.0.1 01 Feb 2021 none non-standard — Details →
9.1.5 01 Feb 2021 none non-standard — Details →
8.1.4 19 Nov 2020 none non-standard — Details →
11.0.0 14 Oct 2020 none non-standard — Details →
11.0.0.0rc1 25 Sep 2020 none non-standard — Details →
9.1.4 31 Jul 2020 none non-standard — Details →
10.0.1 29 Jul 2020 none non-standard — Details →
8.1.3 20 Jul 2020 none non-standard — Details →
9.1.3 15 Jun 2020 none non-standard — Details →
10.0.0 13 May 2020 none non-standard — Details →
10.0.0.0rc2 07 May 2020 none non-standard — Details →
8.1.2 30 Apr 2020 none non-standard — Details →
9.1.2 28 Apr 2020 none non-standard — Details →
10.0.0.0rc1 23 Apr 2020 none non-standard — Details →
8.1.1 26 Mar 2020 none non-standard — Details →
9.1.1 26 Mar 2020 none non-standard — Details →
7.4.1 12 Mar 2020 none non-standard — Details →
7.4.0 12 Nov 2019 H1 U1 non-standard Yes Details →
8.1.0 12 Nov 2019 U1 non-standard Yes Details →
9.1.0 12 Nov 2019 U1 non-standard Yes Details →
6.3.2 25 Oct 2019 H1 U1 non-standard Yes Details →
9.0.0 16 Oct 2019 U1 non-standard Yes Details →
9.0.0.0rc1 26 Sep 2019 none non-standard — Details →
6.3.1 22 Jul 2019 H1 U1 — Yes Details →
8.0.1 22 Jul 2019 U1 — Yes Details →
6.3.0 16 Apr 2019 H1 U1 — Yes Details →
7.3.0 16 Apr 2019 H1 U1 — Yes Details →
5.1.0 12 Apr 2019 H1 U1 — Yes Details →
8.0.0 10 Apr 2019 U1 — Yes Details →
7.2.0 26 Mar 2019 H1 U1 — Yes Details →
6.2.0 25 Mar 2019 H1 U1 — Yes Details →
8.0.0.0rc1 22 Mar 2019 none — — Details →
6.1.0 31 Jan 2019 H1 U1 — Yes Details →
7.1.0 31 Jan 2019 H1 U1 — Yes Details →
5.0.3 29 Jan 2019 H1 U1 — Yes Details →
5.0.2 08 Oct 2018 H1 U1 — Yes Details →
4.0.2 08 Oct 2018 H1 U1 — Yes Details →
7.0.0 27 Sep 2018 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for manila

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 manila

Is manila safe to use?

Vulert records 2 vulnerabilities for manila in PyPI: 0 critical, 1 high, 0 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 manila's Vulert package health score?

Vulert scores manila 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 manila affected?

No. 23.0.1, 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.

How many vulnerabilities does manila have?

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

0 vulnerabilities were recorded for manila in the last 12 months, and the oldest entry in this database dates to 12 Mar 2020. 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 manila 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 manila for upcoming vulnerabilities?

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