VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nameko: vulnerability history, versions and safety

nameko is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 96 releases, first recorded in Oct 2021. 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 C1 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.

See all nameko vulnerabilities

Vulert verdict on nameko 2.14.1 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.14.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 26 Oct 2021 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 45 packages i
  • Stars 4,744 i
  • OpenSSF scorecard 2/10 i
  • Last release 58 months ago i
  • Licence Apache-2.0 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 nameko, 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.0.0rc11 05 Dec 2021 none Apache-2.0 — Details →
2.14.1 05 Dec 2021 none Apache-2.0 — Details →
2.14.0 19 Oct 2021 none Apache-2.0 — Details →
3.0.0rc10 19 Oct 2021 none Apache-2.0 — Details →
3.0.0rc9 10 Oct 2020 none Apache-2.0 — Details →
2.13.0 11 Sep 2020 C1 U1 Apache-2.0 Yes Details →
3.0.0rc8 26 Jul 2019 none Apache-2.0 — Details →
3.0.0rc7 27 Jun 2019 none Apache-2.0 — Details →
3.0.0rc6 19 Mar 2019 none Apache-2.0 — Details →
2.12.0 18 Mar 2019 C1 U1 Apache-2.0 Yes Details →
3.0.0rc5 14 Jan 2019 none Apache-2.0 — Details →
3.0.0rc4 11 Jan 2019 none Apache-2.0 — Details →
3.0.0rc3 05 Jan 2019 none Apache-2.0 — Details →
3.0.0rc2 22 Nov 2018 none Apache-2.0 — Details →
3.0.0rc1 19 Nov 2018 none Apache-2.0 — Details →
3.0.0rc0 02 Oct 2018 none Apache-2.0 — Details →
2.11.0 09 Aug 2018 C1 U1 Apache-2.0 Yes Details →
2.10.0 06 Aug 2018 C1 U1 Apache-2.0 Yes Details →
2.9.1 20 Jul 2018 C1 U1 Apache-2.0 Yes Details →
2.9.1rc0 30 May 2018 C1 U1 Apache-2.0 Yes Details →
2.9.0 30 May 2018 C1 U1 Apache-2.0 Yes Details →
2.9.0rc0 04 May 2018 C1 U1 Apache-2.0 Yes Details →
2.8.5 15 Mar 2018 C1 U1 Apache-2.0 Yes Details →
2.8.4 18 Feb 2018 C1 U1 Apache-2.0 Yes Details →
2.8.3 12 Jan 2018 C1 U1 Apache-2.0 Yes Details →
2.8.2 11 Dec 2017 C1 U1 Apache-2.0 Yes Details →
2.8.1 29 Nov 2017 C1 U1 Apache-2.0 Yes Details →
2.8.0 31 Oct 2017 C1 U1 Apache-2.0 Yes Details →
2.7.0 07 Oct 2017 C1 U1 Apache-2.0 Yes Details →
2.6.0 30 Apr 2017 C1 U1 Apache-2.0 Yes Details →
2.5.4 20 Apr 2017 C1 U1 Apache-2.0 Yes Details →
2.5.3 16 Mar 2017 C1 U1 Apache-2.0 Yes Details →
2.5.2 28 Feb 2017 C1 U1 Apache-2.0 Yes Details →
2.5.1 19 Jan 2017 C1 U1 Apache-2.0 Yes Details →
2.5.0 20 Dec 2016 C1 U1 Apache-2.0 Yes Details →
2.4.4 28 Nov 2016 C1 U1 Apache-2.0 Yes Details →
2.4.3 17 Nov 2016 C1 U1 Apache-2.0 Yes Details →
2.4.2 10 Oct 2016 C1 U1 Apache-2.0 Yes Details →
2.4.1 14 Sep 2016 C1 U1 Apache-2.0 Yes Details →
2.4.0 30 Aug 2016 C1 U1 Apache-2.0 Yes Details →
2.3.1 11 May 2016 C1 U1 Apache-2.0 Yes Details →
2.3.0 05 Apr 2016 C1 U1 Apache-2.0 Yes Details →
2.2.0 04 Oct 2015 C1 U1 Apache-2.0 Yes Details →
2.1.2 26 May 2015 C1 U1 Apache-2.0 Yes Details →
2.1.1 11 May 2015 C1 U1 Apache-2.0 Yes Details →
2.1.0 13 Apr 2015 C1 U1 Apache-2.0 Yes Details →
2.0.0 31 Mar 2015 C1 U1 Apache-2.0 Yes Details →
1.14.0 19 Dec 2014 C1 U1 Apache-2.0 Yes Details →
1.13.0 02 Dec 2014 C1 U1 Apache-2.0 Yes Details →
1.12.0 25 Nov 2014 C1 U1 Apache-2.0 Yes Details →
1.11.5 18 Nov 2014 C1 U1 Apache-2.0 Yes Details →
1.11.4 10 Nov 2014 C1 U1 Apache-2.0 Yes Details →
1.11.3 10 Oct 2014 C1 U1 Apache-2.0 Yes Details →
1.11.2 18 Sep 2014 C1 U1 Apache-2.0 Yes Details →
1.11.1 15 Sep 2014 C1 U1 Apache-2.0 Yes Details →
1.11.0 01 Sep 2014 C1 U1 Apache-2.0 Yes Details →
1.10.1 27 Aug 2014 C1 U1 Apache-2.0 Yes Details →
1.10.0 14 Aug 2014 C1 U1 Apache-2.0 Yes Details →
1.9.1 12 Aug 2014 C1 U1 Apache-2.0 Yes Details →
1.9.0 15 Jul 2014 C1 U1 Apache-2.0 Yes Details →
1.8.2 07 Jul 2014 C1 U1 Apache-2.0 Yes Details →
1.8.1 23 Jun 2014 C1 U1 Apache-2.0 Yes Details →
1.8.0 13 Jun 2014 C1 U1 Apache-2.0 Yes Details →
1.7.2 10 Jun 2014 C1 U1 Apache-2.0 Yes Details →
1.7.1 20 May 2014 C1 U1 Apache-2.0 Yes Details →
1.7.0 07 May 2014 C1 U1 Apache-2.0 Yes Details →
1.6.1 03 Apr 2014 C1 U1 Apache-2.0 Yes Details →
1.6.0 31 Mar 2014 C1 U1 Apache-2.0 Yes Details →
1.5.0 27 Mar 2014 C1 U1 Apache-2.0 Yes Details →
1.4.1 26 Mar 2014 C1 U1 Apache-2.0 Yes Details →
1.4.0 20 Mar 2014 C1 U1 Apache-2.0 Yes Details →
1.3.5 05 Mar 2014 C1 U1 Apache-2.0 Yes Details →
1.3.4 05 Mar 2014 C1 U1 Apache-2.0 Yes Details →
1.3.3 25 Feb 2014 C1 U1 Apache-2.0 Yes Details →
1.3.2 13 Feb 2014 C1 U1 Apache-2.0 Yes Details →
1.3.1 28 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.3.0 23 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.2.5 22 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.2.4 20 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.2.3 15 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.2.2 09 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.2.1 09 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.2.0 03 Jan 2014 C1 U1 Apache-2.0 Yes Details →
1.1.4 30 Dec 2013 C1 U1 Apache-2.0 Yes Details →
1.1.3 12 Dec 2013 C1 U1 Apache-2.0 Yes Details →
1.1.2 21 Nov 2013 C1 U1 Apache-2.0 Yes Details →
1.1.1 20 Nov 2013 C1 U1 Apache-2.0 Yes Details →
1.1.0 20 Nov 2013 C1 U1 Apache-2.0 Yes Details →
1.0.1 18 Nov 2013 C1 U1 Apache-2.0 Yes Details →
1.0.0 18 Nov 2013 C1 U1 Apache-2.0 Yes Details →
0.7.0 12 Sep 2013 C1 U1 Apache-2.0 Yes Details →
0.6.0 17 Jul 2013 C1 U1 Apache-2.0 Yes Details →
0.5.3 16 Jul 2013 C1 U1 Apache-2.0 Yes Details →
0.5.2 15 Jul 2013 C1 U1 Apache-2.0 Yes Details →
0.5.1 15 Jul 2013 C1 U1 Apache-2.0 Yes Details →
0.5.0 12 Jul 2013 C1 U1 Apache-2.0 Yes Details →
0.4.1 09 Jul 2013 C1 U1 Apache-2.0 Yes Details →
0.4.0 25 Jun 2013 C1 U1 Apache-2.0 Yes Details →
0.3.0 07 Jun 2013 C1 U1 Apache-2.0 Yes Details →
0.2.1 31 May 2013 C1 U1 Apache-2.0 Yes Details →
0.2.0 28 May 2013 C1 U1 — Yes Details →
0.1.9 21 May 2013 C1 U1 — Yes Details →
0.1.8 13 May 2013 C1 U1 — Yes Details →
0.1.7 03 May 2013 C1 U1 — Yes Details →
0.1.6 30 Apr 2013 C1 U1 — Yes Details →
0.1.5 30 Apr 2013 C1 U1 — Yes Details →
0.1.4 29 Apr 2013 C1 U1 — Yes Details →
0.1.3 29 Apr 2013 C1 U1 — Yes Details →
0.1.2 29 Apr 2013 C1 U1 — Yes Details →
0.1.1 29 Apr 2013 C1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

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 nameko

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-41078: Arbitrary Code Execution in nameko 8.6 critical 2.14.0 19 Oct 2021
CVE-2021-41078: Arbitrary Code Execution in nameko N/A unrated 2.14.0 26 Oct 2021

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 nameko

Is nameko safe to use?

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

Vulert scores nameko 63/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 nameko affected?

No. 2.14.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.

Which version of nameko should I use?

2.14.1 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 nameko have?

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

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

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