VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nbgitpuller: vulnerability history, versions and safety

nbgitpuller is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 26 releases, first recorded in Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 U2
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 nbgitpuller vulnerabilities

Vulert verdict on nbgitpuller 1.3.0 i

Updated on 22 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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.3.0 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 30 Aug 2021 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 6 packages i
  • Stars 237 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 months ago i
  • Licence BSD-3-Clause 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 nbgitpuller, 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.3.0 31 Mar 2026 U2 BSD-3-Clause Yes Details →
1.3.0b1 05 Feb 2026 U2 BSD-3-Clause Yes Details →
1.2.2 27 Jan 2025 U2 BSD-3-Clause Yes Details →
1.2.1 29 Mar 2024 U2 BSD-3-Clause Yes Details →
1.2.0 07 Aug 2023 U2 BSD-3-Clause Yes Details →
1.1.1 08 Nov 2022 U2 BSD-3-Clause Yes Details →
1.1.0 19 Mar 2022 U2 BSD-3-Clause Yes Details →
1.0.2 02 Sep 2021 U2 BSD-3-Clause Yes Details →
1.0.1 02 Sep 2021 U2 BSD-3-Clause Yes Details →
1.0.0 01 Sep 2021 U2 BSD-3-Clause Yes Details →
0.10.2 25 Aug 2021 U2 BSD-3-Clause Yes Details →
0.10.1 24 Jun 2021 H1 U2 BSD-3-Clause Yes Details →
0.10.0 09 Jun 2021 H1 U2 BSD-3-Clause Yes Details →
0.9.0 01 Aug 2020 H1 U2 BSD-3-Clause Yes Details →
0.9.0rc1 01 Aug 2020 U2 BSD-3-Clause Yes Details →
0.8.0 24 Nov 2019 U2 BSD-3-Clause Yes Details →
0.7.2 11 Sep 2019 U2 BSD-3-Clause Yes Details →
0.7.1 29 Aug 2019 U2 BSD-3-Clause Yes Details →
0.7.0 31 Jul 2019 U2 BSD-3-Clause Yes Details →
0.6.1 18 Jul 2018 U2 BSD-3-Clause Yes Details →
0.6.0 18 Jul 2018 U2 BSD-3-Clause Yes Details →
0.5.0 26 Jun 2018 U2 BSD-3-Clause Yes Details →
0.4.0 15 Jun 2018 U2 BSD-3-Clause Yes Details →
0.3.0 31 Oct 2017 U2 non-standard Yes Details →
0.2.0 19 Sep 2017 U2 non-standard Yes Details →
0.1.0 14 Sep 2017 U2 non-standard Yes Details →

All 26 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 3

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

03 Vulnerabilities

Recorded vulnerabilities for nbgitpuller

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-39160: Code injection in nbgitpuller 8.8 high 0.10.2 30 Aug 2021
CVE-2021-39160: nbgitpuller Arbitrary Code Execution N/A unrated 07690644f29a566011dd0d7ba14cae3eb0490481 25 Aug 2021
CVE-2021-39160: nbgitpuller Arbitrary Code Execution N/A unrated 07690644f29a566011dd0d7ba14cae3eb0490481 25 Aug 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 nbgitpuller

Is nbgitpuller safe to use?

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

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

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

Which version of nbgitpuller should I use?

1.3.0 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 nbgitpuller have?

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

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

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