VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pytigergraph: vulnerability history, versions and safety

pytigergraph is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 pytigergraph vulnerabilities

Vulert verdict on pytigergraph 2.0.5 i

Updated on 22 Oct 2026

Careful: 2.0.5 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.0.5 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Sep 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 10 packages i
  • Last release this month 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 pytigergraph, 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
2.0.5 05 Oct 2026 U1 Apache-2.0 No Details →
2.0.4 19 May 2026 U1 Apache-2.0 No Details →
2.0.3 16 Apr 2026 U1 Apache-2.0 No Details →
2.0.2 08 Apr 2026 U1 Apache-2.0 No Details →
2.0.1 23 Mar 2026 U1 Apache-2.0 No Details →
2.0.0 24 Feb 2026 U1 Apache-2.0 No Details →
1.9.1 04 Nov 2025 U1 Apache-2.0 No Details →
1.9.0 06 Jun 2025 U1 Apache-2.0 No Details →
1.8.8 30 May 2025 U1 Apache-2.0 No Details →
1.8.7 02 May 2025 U1 Apache-2.0 No Details →
1.8.6 24 Mar 2025 U1 Apache-2.0 No Details →
1.8.5 17 Mar 2025 U1 Apache-2.0 No Details →
1.8.4 20 Jan 2025 U1 Apache-2.0 No Details →
1.8.3 05 Dec 2024 U1 Apache-2.0 No Details →
1.8.2 05 Dec 2024 U1 Apache-2.0 No Details →
1.8.1 19 Nov 2024 U1 Apache-2.0 No Details →
1.8.0 05 Nov 2024 U1 Apache-2.0 No Details →
1.7.4 16 Oct 2024 U1 Apache-2.0 No Details →
1.7.3 14 Oct 2024 U1 Apache-2.0 No Details →
1.7.2 01 Oct 2024 U1 Apache-2.0 No Details →
1.7.1 23 Sep 2024 U1 Apache-2.0 No Details →
1.7.0 21 Aug 2024 U1 Apache-2.0 No Details →
1.6.5 06 Aug 2024 U1 Apache-2.0 No Details →
1.6.4 01 Aug 2024 U1 Apache-2.0 No Details →
1.6.3 25 Jul 2024 U1 Apache-2.0 No Details →
1.6.2 06 Jun 2024 U1 Apache-2.0 No Details →
1.6.1 25 Apr 2024 U1 Apache-2.0 No Details →
1.6.0 25 Apr 2024 U1 Apache-2.0 No Details →
1.5.2 15 Feb 2024 U1 Apache-2.0 No Details →
1.5.1 12 Dec 2023 U1 Apache-2.0 No Details →
1.5.0 25 Sep 2023 U1 Apache-2.0 No Details →
1.4.2 01 Sep 2023 U1 Apache-2.0 No Details →
1.4.1 05 Jun 2023 U1 Apache-2.0 No Details →
1.4.0 17 May 2023 U1 Apache-2.0 No Details →
1.3.4 13 Apr 2023 U1 Apache-2.0 No Details →
1.3.3 03 Apr 2023 U1 Apache-2.0 No Details →
1.3.2 13 Mar 2023 U1 Apache-2.0 No Details →
1.3.1 17 Feb 2023 U1 Apache-2.0 No Details →
1.3.0 09 Feb 2023 U1 Apache-2.0 No Details →
1.2.6 30 Nov 2022 U1 Apache-2.0 No Details →
1.2.5 15 Nov 2022 U1 Apache-2.0 No Details →
1.2.4 15 Nov 2022 U1 Apache-2.0 No Details →
1.2.3 14 Nov 2022 U1 Apache-2.0 No Details →
1.2.2 12 Nov 2022 U1 Apache-2.0 No Details →
1.2.1 11 Nov 2022 U1 Apache-2.0 No Details →
1.2.0 10 Nov 2022 U1 Apache-2.0 No Details →
1.1.0 06 Sep 2022 U1 Apache-2.0 No Details →
1.0.2 03 Aug 2022 U1 Apache-2.0 No Details →
1.0.1 13 Jul 2022 U1 Apache-2.0 No Details →
1.0.0 11 Jul 2022 U1 Apache-2.0 No Details →
0.9.2 01 Jul 2022 U1 Apache-2.0 No Details →
0.9.1 21 Jun 2022 U1 Apache-2.0 No Details →
0.9.0 17 May 2022 U1 Apache-2.0 No Details →
0.0.9.9.2 22 Feb 2022 U1 MIT No Details →
0.0.9.9.1 22 Feb 2022 U1 MIT No Details →
0.0.9.9.0 10 Feb 2022 U1 MIT No Details →
0.0.9.8.9 10 Feb 2022 U1 MIT No Details →
0.0.9.8.8 09 Feb 2022 U1 MIT No Details →
0.0.9.8.7 31 Jan 2022 U1 MIT No Details →
0.0.9.8.6 20 Dec 2021 U1 MIT No Details →
0.0.9.8.5 28 Oct 2021 U1 MIT No Details →
0.0.9.8.4 30 Sep 2021 U1 MIT No Details →
0.0.9.8.3 30 Sep 2021 U1 MIT No Details →
0.0.9.8.2 30 Sep 2021 U1 MIT No Details →
0.0.9.8.1 30 Sep 2021 U1 MIT No Details →
0.0.9.8.0 30 Sep 2021 U1 MIT No Details →
0.0.9.7.9 30 Sep 2021 U1 MIT No Details →
0.0.9.7.8 27 Sep 2021 U1 MIT No Details →
0.0.9.7.7 20 Sep 2021 U1 MIT No Details →
0.0.9.7.6 01 Sep 2021 U1 MIT No Details →
0.0.9.7.5 01 Sep 2021 U1 MIT No Details →
0.0.9.7.4 01 Sep 2021 U1 MIT No Details →
0.0.9.7.3 30 Jul 2021 U1 MIT No Details →
0.0.9.7.2 28 Jul 2021 U1 MIT No Details →
0.0.9.7.1 27 Jul 2021 U1 MIT No Details →
0.0.9.6.9 29 Jun 2021 U1 MIT No Details →
0.0.9.6.8 03 Jun 2021 U1 MIT No Details →
0.0.9.6.7 03 Jun 2021 U1 MIT No Details →
0.0.9.6.6 27 Apr 2021 U1 MIT No Details →
0.0.9.6.5 27 Apr 2021 U1 MIT No Details →
0.0.9.6.4 18 Apr 2021 U1 MIT No Details →
0.0.9.6.3 14 Dec 2020 U1 MIT No Details →
0.0.9.6.2 08 Oct 2020 U1 MIT No Details →
0.0.9.5 07 Oct 2020 U1 MIT No Details →
0.0.9.4 03 Oct 2020 U1 MIT No Details →
0.0.9.3 29 Sep 2020 U1 MIT No Details →
0.0.9.2 29 Sep 2020 U1 MIT No Details →
0.0.9.1 03 Sep 2020 U1 MIT No Details →
0.0.9 23 Aug 2020 U1 MIT No Details →
0.0.8.5 19 Aug 2020 U1 MIT No Details →
0.0.8.4 19 Aug 2020 U1 MIT No Details →
0.0.8.2 08 Aug 2020 U1 MIT No Details →
0.0.8.1 08 Aug 2020 U1 MIT No Details →
0.0.8 08 Aug 2020 U1 MIT No Details →
0.0.7 27 Jul 2020 U1 MIT No Details →
0.0.6.9 24 Jul 2020 U1 MIT No Details →
0.0.6.8 23 Jul 2020 U1 MIT No Details →
0.0.6.7 21 Jul 2020 U1 MIT No Details →
0.0.6.6 21 Jul 2020 U1 MIT No Details →
0.0.6.5 14 Jul 2020 U1 MIT No Details →
0.0.6.4 07 Jul 2020 U1 — No Details →
0.0.6.3 04 Jul 2020 U1 — No Details →
0.0.6.2 28 Jun 2020 U1 — No Details →
0.0.6.1 26 Jun 2020 U1 — No Details →
0.0.6.0 04 Jun 2020 U1 — No Details →
0.0.5.8 04 Jun 2020 U1 — No Details →
0.0.5.7 04 Jun 2020 U1 — No Details →
0.0.5.6 03 Jun 2020 U1 — No Details →
0.0.5.5 20 May 2020 U1 — No Details →
0.0.5.4 19 May 2020 U1 — No Details →
0.0.5.3 16 May 2020 U1 — No Details →
0.0.5.2 14 May 2020 U1 — No Details →
0.0.5.1 12 May 2020 U1 — No Details →
0.0.5 12 May 2020 U1 — No Details →
0.0.4.7.6 05 Apr 2020 U1 — No Details →
0.0.4.7.5 05 Apr 2020 U1 — No Details →
0.0.4.7.4 05 Apr 2020 U1 — No Details →
0.0.4.7.3 05 Apr 2020 U1 — No Details →
0.0.4.7.2 03 Apr 2020 U1 — No Details →
0.0.4.7.1 31 Mar 2020 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for pytigergraph

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-30331: TigerGraph UDF Arbitrary Code Execution 8.8 high No fix published 05 Sep 2022

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 pytigergraph

Is pytigergraph safe to use?

Vulert records 1 vulnerabilities for pytigergraph in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is pytigergraph's Vulert package health score?

Vulert scores pytigergraph 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of pytigergraph affected?

Yes. 2.0.5, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of pytigergraph should I use?

2.0.5 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 pytigergraph have?

1 vulnerability is recorded for pytigergraph in the PyPI ecosystem: 0 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 pytigergraph vulnerabilities disclosed?

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

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