VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

bigflow: vulnerability history, versions and safety

bigflow is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 108 releases, from Apr 2023 to Jul 2026. 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 M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bigflow vulnerabilities

Vulert verdict on bigflow 1.11.3 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 1.11.3 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Stars 120 i
  • OpenSSF scorecard 2/10 i
  • Last release 18 months ago 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 bigflow, 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.11.3 09 Apr 2025 none — — Details →
1.11.1 11 Mar 2025 none Apache-2.0 — Details →
1.11.0 06 Mar 2025 none Apache-2.0 — Details →
1.10.0 29 May 2024 none Apache-2.0 — Details →
1.9.0 20 May 2024 none Apache-2.0 — Details →
1.9.0.dev1 16 May 2024 none Apache-2.0 — Details →
1.8.0 13 Jul 2023 none Apache-2.0 — Details →
1.7.2 17 May 2023 none Apache-2.0 — Details →
1.7.1 09 May 2023 none Apache-2.0 — Details →
1.7.0 14 Mar 2023 none Apache-2.0 — Details →
1.7.0.dev1 23 Feb 2023 none Apache-2.0 — Details →
1.6.0 23 Feb 2023 none Apache-2.0 — Details →
1.6.0.dev1 23 Feb 2023 M1 U1 Apache-2.0 Yes Details →
1.5.5.dev2 19 Jan 2023 M1 U1 Apache-2.0 Yes Details →
1.5.5.dev1 17 Jan 2023 M1 U1 Apache-2.0 Yes Details →
1.5.4 16 Jan 2023 M1 U1 Apache-2.0 Yes Details →
1.5.4.dev1 16 Jan 2023 M1 U1 Apache-2.0 Yes Details →
1.5.3 28 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.3.dev1 21 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.2 17 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.2.dev2 16 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.2.dev1 16 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.1 15 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.1.dev1 15 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.0 08 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.0.dev2 08 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.5.0.dev1 07 Nov 2022 M1 U1 Apache-2.0 Yes Details →
1.4.2 05 Apr 2022 M1 U1 — Yes Details →
1.4.2rc6 22 Mar 2022 M1 U1 — Yes Details →
1.4.2rc5 22 Mar 2022 M1 U1 — Yes Details →
1.4.2.dev5 16 Mar 2022 M1 U1 — Yes Details →
1.4.2rc4 12 Mar 2022 M1 U1 — Yes Details →
1.4.2rc3 12 Mar 2022 M1 U1 — Yes Details →
1.4.2rc2 28 Feb 2022 M1 U1 — Yes Details →
1.4.2rc1 17 Feb 2022 M1 U1 — Yes Details →
1.4.2.dev4 15 Feb 2022 M1 U1 — Yes Details →
1.4.2.dev3 01 Feb 2022 M1 U1 — Yes Details →
1.4.2.dev2 31 Jan 2022 M1 U1 — Yes Details →
1.4.2.dev1 19 Jan 2022 M1 U1 — Yes Details →
1.4.1 10 Jan 2022 M1 U1 — Yes Details →
1.4.1.dev7 28 Dec 2021 M1 U1 — Yes Details →
1.4.1.dev6 28 Dec 2021 M1 U1 — Yes Details →
1.4.1.dev5 10 Dec 2021 M1 U1 — Yes Details →
1.4.1.dev4 08 Dec 2021 M1 U1 — Yes Details →
1.4.1.dev3 08 Dec 2021 M1 U1 — Yes Details →
1.4.1.dev2 26 Nov 2021 M1 U1 — Yes Details →
1.4.1.dev0 26 Nov 2021 M1 U1 — Yes Details →
1.4.0 26 Nov 2021 M1 U1 — Yes Details →
1.4.0.dev1 25 Nov 2021 M1 U1 — Yes Details →
1.3.6.dev4 26 Oct 2021 M1 U1 — Yes Details →
1.3.6.dev3 22 Oct 2021 M1 U1 — Yes Details →
1.3.6.dev2 17 Sep 2021 M1 U1 — Yes Details →
1.3.6.dev1 13 Sep 2021 M1 U1 — Yes Details →
1.3.5 08 Sep 2021 M1 U1 — Yes Details →
1.3.4 02 Sep 2021 M1 U1 — Yes Details →
1.3.3 19 Aug 2021 M1 U1 — Yes Details →
1.3.2 13 Aug 2021 M1 U1 — Yes Details →
1.3.1 28 Jul 2021 M1 U1 — Yes Details →
1.3.0 13 Jul 2021 M1 U1 — Yes Details →
1.3.0.dev10 13 Jul 2021 M1 U1 — Yes Details →
1.3.0.dev8 24 Jun 2021 M1 U1 — Yes Details →
1.3.0.dev7 31 May 2021 M1 U1 — Yes Details →
1.3.0.dev6 17 May 2021 M1 U1 — Yes Details →
1.3.0.dev5 04 May 2021 M1 U1 — Yes Details →
1.3.0.dev4 27 Apr 2021 M1 U1 — Yes Details →
1.3.0.dev3 27 Apr 2021 M1 U1 — Yes Details →
1.2.1 16 Apr 2021 M1 U1 — Yes Details →
1.3.0.dev2 15 Apr 2021 M1 U1 — Yes Details →
1.3.0.dev1 14 Apr 2021 M1 U1 — Yes Details →
1.2.0 30 Mar 2021 M1 U1 — Yes Details →
1.2.0rc1 25 Mar 2021 M1 U1 — Yes Details →
1.2.0b2 25 Mar 2021 M1 U1 — Yes Details →
1.2.0b1 19 Mar 2021 M1 U1 — Yes Details →
1.1.4 05 Feb 2021 M1 U1 — Yes Details →
1.1.3 08 Jan 2021 M1 U1 — Yes Details →
1.1.2 08 Jan 2021 M1 U1 — Yes Details →
1.1.1 08 Jan 2021 M1 U1 — Yes Details →
1.1.0 08 Jan 2021 M1 U1 — Yes Details →
1.1.0a3 29 Dec 2020 M1 U1 — Yes Details →
1.1.0a2 29 Dec 2020 M1 U1 — Yes Details →
1.1.0a1 28 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev9 21 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev8 21 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev7 21 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev6 18 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev5 18 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev4 16 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev3 15 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev2 15 Dec 2020 M1 U1 — Yes Details →
1.1.0.dev1 11 Dec 2020 M1 U1 — Yes Details →
1.0.4 08 Dec 2020 M1 U1 — Yes Details →
1.0.3 03 Dec 2020 M1 U1 — Yes Details →
1.0.2 19 Nov 2020 M1 U1 — Yes Details →
1.0.2.dev2 18 Nov 2020 M1 U1 — Yes Details →
1.0.2.dev1 18 Nov 2020 M1 U1 — Yes Details →
1.0.1 18 Nov 2020 M1 U1 — Yes Details →
1.0.1.dev1 13 Nov 2020 M1 U1 — Yes Details →
1.0.0 04 Nov 2020 M1 U1 — Yes Details →
1.0.0rc1 03 Nov 2020 M1 U1 — Yes Details →
1.0.0b6 02 Nov 2020 M1 U1 — Yes Details →
1.0.0b5 30 Oct 2020 M1 U1 — Yes Details →
1.0.0b4 30 Oct 2020 M1 U1 — Yes Details →
1.0.0b3 30 Oct 2020 M1 U1 — Yes Details →
1.0.0b2 29 Oct 2020 M1 U1 — Yes Details →
1.0.0b1 29 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev91 29 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev90 27 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev89 27 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev88 26 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev87 26 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev86 22 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev85 22 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev84 22 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev83 22 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev82 22 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev81 21 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev80 21 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev79 21 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev78 21 Oct 2020 M1 U1 — Yes Details →
1.0.0.dev77 20 Oct 2020 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for bigflow

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-25392: Allegro Tech BigFlow Missing SSL Certificate Validation 5.9 medium 1.6.0 10 Apr 2023
CVE-2023-25392: BigFlow Package Vulnerable to Missing SSL Certificate Validation 5.9 medium 1.6.0 07 Jul 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 bigflow

Is bigflow safe to use?

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

Vulert scores bigflow 61/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 bigflow affected?

No. 1.11.3, 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 bigflow should I use?

1.11.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 bigflow have?

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

1 vulnerability was recorded for bigflow in the last 12 months, and the oldest entry in this database dates to 10 Apr 2023. 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 bigflow 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 bigflow for upcoming vulnerabilities?

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