VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mako: vulnerability history, versions and safety

mako is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 83 releases, from Jul 2010 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H2 M3 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mako vulnerabilities

Vulert verdict on mako 1.4.3 i

Updated on 23 Oct 2026

Action needed: 1.4.3 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.4.3 — affected i
  • Vulnerabilities on record 10 over 16 years · 6 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 9,200 packages i
  • Stars 461 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT 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 mako, 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
1.4.3 22 Sep 2026 U1 MIT Yes Details →
1.4.2 22 Sep 2026 U1 MIT Yes Details →
1.4.1 05 Aug 2026 M1 U1 MIT Yes Details →
1.4.0 04 Aug 2026 M1 U1 MIT Yes Details →
1.3.12 28 Apr 2026 M1 U1 MIT Yes Details →
1.3.11 14 Apr 2026 H1 M1 U2 MIT Yes Details →
1.3.10 10 Apr 2025 H1 M2 U3 MIT Yes Details →
1.3.9 04 Feb 2025 H1 M2 U3 MIT Yes Details →
1.3.8 07 Dec 2024 H1 M2 U3 MIT Yes Details →
1.3.7 03 Dec 2024 H1 M2 U3 MIT Yes Details →
1.3.6 21 Oct 2024 H1 M2 U3 MIT Yes Details →
1.3.5 14 May 2024 H1 M2 U3 MIT Yes Details →
1.3.4 14 May 2024 H1 M2 U3 MIT Yes Details →
1.3.3 10 Apr 2024 H1 M2 U3 MIT Yes Details →
1.3.2 30 Jan 2024 H1 M2 U3 MIT Yes Details →
1.3.1 22 Jan 2024 H1 M2 U3 MIT Yes Details →
1.3.0 08 Nov 2023 H1 M2 U3 MIT Yes Details →
1.2.4 15 Nov 2022 H1 M2 U3 MIT Yes Details →
1.2.3 22 Sep 2022 H1 M2 U3 MIT Yes Details →
1.2.2 29 Aug 2022 H1 M2 U3 MIT Yes Details →
1.2.1 30 Jun 2022 H2 M2 U4 MIT Yes Details →
1.2.0 10 Mar 2022 H2 M2 U4 MIT Yes Details →
1.1.6 17 Nov 2021 H2 M2 U4 MIT Yes Details →
1.1.5 20 Aug 2021 H2 M2 U4 MIT Yes Details →
1.1.4 07 Mar 2021 H2 M2 U4 MIT Yes Details →
1.1.3 30 May 2020 H2 M2 U4 MIT Yes Details →
1.1.2 01 Mar 2020 H2 M2 U4 MIT Yes Details →
1.1.1 20 Jan 2020 H2 M2 U4 MIT Yes Details →
1.1.0 01 Aug 2019 H2 M2 U4 MIT Yes Details →
1.0.14 20 Jul 2019 H2 M2 U4 MIT Yes Details →
1.0.13 01 Jul 2019 H2 M2 U4 MIT Yes Details →
1.0.12 06 Jun 2019 H2 M2 U4 MIT Yes Details →
1.0.11 31 May 2019 H2 M2 U4 MIT Yes Details →
1.0.10 10 May 2019 H2 M2 U4 MIT Yes Details →
1.0.9 15 Apr 2019 H2 M2 U4 MIT Yes Details →
1.0.8 20 Mar 2019 H2 M2 U4 MIT Yes Details →
1.0.7 13 Jul 2017 H2 M2 U4 MIT Yes Details →
1.0.6 09 Nov 2016 H2 M2 U4 MIT Yes Details →
1.0.5 03 Nov 2016 H2 M2 U4 MIT Yes Details →
1.0.4 10 Mar 2016 H2 M2 U4 MIT Yes Details →
1.0.3 27 Oct 2015 H2 M2 U4 MIT Yes Details →
1.0.2 26 Aug 2015 H2 M2 U4 MIT Yes Details →
1.0.1 22 Jan 2015 H2 M2 U4 MIT Yes Details →
1.0.0 08 Jun 2014 H2 M2 U4 MIT Yes Details →
0.9.1 26 Dec 2013 H2 M2 U4 MIT Yes Details →
0.9.0 27 Aug 2013 H2 M2 U4 MIT Yes Details →
0.8.1 24 May 2013 H2 M2 U4 MIT Yes Details →
0.8.0 10 Apr 2013 H2 M2 U4 MIT Yes Details →
0.7.3 07 Nov 2012 H2 M2 U4 MIT Yes Details →
0.7.2 20 Jul 2012 H2 M2 U4 MIT Yes Details →
0.7.1 09 Jul 2012 H2 M2 U4 MIT Yes Details →
0.7.0 31 Mar 2012 H2 M2 U4 MIT Yes Details →
0.6.2 02 Feb 2012 H2 M2 U4 MIT Yes Details →
0.6.1 28 Jan 2012 H2 M2 U4 MIT Yes Details →
0.6.0 22 Jan 2012 H2 M2 U4 MIT Yes Details →
0.5.0 28 Sep 2011 H2 M2 U4 MIT Yes Details →
0.4.2 05 Aug 2011 H2 M2 U4 MIT Yes Details →
0.4.1 07 Apr 2011 H2 M2 U4 MIT Yes Details →
0.4.0 21 Feb 2011 H2 M2 U4 MIT Yes Details →
0.3.6 13 Nov 2010 H2 M2 U4 MIT Yes Details →
0.3.5 20 Oct 2010 H2 M2 U4 MIT Yes Details →
0.3.4 22 Jun 2010 H2 M2 U4 MIT Yes Details →
0.3.3 31 May 2010 H2 M3 U5 MIT Yes Details →
0.3.2 11 Mar 2010 H2 M3 U5 MIT Yes Details →
0.3.1 07 Mar 2010 H2 M3 U5 MIT Yes Details →
0.3.0 05 Mar 2010 H2 M3 U5 MIT Yes Details →
0.2.5 07 Sep 2009 H2 M3 U5 MIT Yes Details →
0.2.4 23 Dec 2008 H2 M3 U5 MIT Yes Details →
0.2.3 23 Nov 2008 H2 M3 U5 MIT Yes Details →
0.2.2 23 Jun 2008 H2 M3 U5 MIT Yes Details →
0.2.1 16 Jun 2008 H2 M3 U5 MIT Yes Details →
0.2.0 03 Jun 2008 H2 M3 U5 MIT Yes Details →
0.1.10 27 Dec 2007 H2 M3 U5 MIT Yes Details →
0.1.9 25 Sep 2007 H2 M3 U5 MIT Yes Details →
0.1.8 26 Jun 2007 H2 M3 U5 MIT Yes Details →
0.1.7 13 Jun 2007 H2 M3 U5 MIT Yes Details →
0.1.6 18 May 2007 H2 M3 U5 MIT Yes Details →
0.1.5 31 Mar 2007 H2 M3 U5 MIT Yes Details →
0.1.4 10 Mar 2007 H2 M3 U5 MIT Yes Details →
0.1.3 21 Feb 2007 H2 M3 U5 MIT Yes Details →
0.1.2 01 Feb 2007 H2 M3 U5 MIT Yes Details →
0.1.1 14 Jan 2007 H2 M3 U5 MIT Yes Details →
0.1.0 31 Dec 2006 H2 M3 U5 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2010 1
  • 2022 3
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for mako

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-44307: Mako Path Traversal Vulnerability on Windows 8.7 high 1.3.12 06 May 2026
CVE-2026-44307: Mako Path Traversal Vulnerability on Windows 8.7 high 1.3.12 13 Jul 2026
CVE-2022-40023: Regular Expression Denial of Service in mako 7.5 high 1.2.2 16 Sep 2022
CVE-2026-41205: Mako Template Library Path Traversal Vulnerability 7.5 high 1.3.11 23 Apr 2026
CVE-2026-102991: Mako Path Traversal Vulnerability on Windows 6.5 medium 1.4.2 05 Oct 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 mako

Is mako safe to use?

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

Vulert scores mako 67/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).

Is the latest version of mako affected?

Yes. 1.4.3, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of mako should I use?

1.4.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 mako have?

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

6 vulnerabilities were recorded for mako in the last 12 months, and the oldest entry in this database dates to 02 Jul 2010. 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 mako 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 mako for upcoming vulnerabilities?

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