VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pyrofork: vulnerability history, versions and safety

pyrofork is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 118 releases, from Dec 2025 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
2 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 pyrofork vulnerabilities

Vulert verdict on pyrofork 2.3.69 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 2.3.69 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 9 packages i
  • Stars 290 i
  • Last release 10 months ago i
  • Licence LGPL-3.0-or-later 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 pyrofork, 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.3.69 10 Dec 2025 none LGPL-3.0-or-later — Details →
2.3.69.dev1 02 Dec 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.68.dev1 02 Dec 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.68 10 Jul 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.67 25 Jun 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.66 10 Jun 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.65 10 Jun 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.64 06 Jun 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.63 18 May 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.62 14 May 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.61 03 Apr 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.60 28 Mar 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.59 08 Mar 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.58 03 Feb 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.57 26 Jan 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.56 10 Jan 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.55 10 Jan 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.54 04 Jan 2025 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.53 21 Dec 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.52 29 Nov 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.51 25 Nov 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.50 22 Nov 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.49 22 Nov 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.48.dev1 08 Oct 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.48 08 Oct 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.47 25 Sep 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.46 13 Sep 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.45 07 Sep 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.44 02 Sep 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.43 25 Aug 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.42 21 Aug 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.41 19 Aug 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.40 07 Aug 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.39 02 Aug 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.38 02 Aug 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.37 23 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.36 15 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.35 14 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.34 14 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.33 13 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.32 07 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.31 06 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.30 05 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.29 02 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.28 01 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.27 01 Jul 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.26 23 Jun 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.25 15 Jun 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.24 03 Jun 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.23 02 Jun 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.22 02 Jun 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.21.post3 08 Apr 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.21.post2 08 Apr 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.21.post1 07 Apr 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.21 06 Apr 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.20 23 Mar 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.19.post2 02 Mar 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.19.post1 01 Mar 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.19 29 Feb 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.18 07 Feb 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.4.0rc1 06 Feb 2024 none LGPL-3.0-or-later — Details →
2.3.17.post2 30 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.17.post1 24 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.17 22 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.16.post5 15 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.16.post4 14 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.16.post3 11 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.16.post2 04 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.16.post1 01 Jan 2024 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.16 31 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.15.post5 28 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.15.post4 26 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.15.post3 25 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.15.post2 25 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.15.post1 25 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.15 24 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.14.post2 15 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.14.post1 13 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.14 12 Dec 2023 M1 U1 LGPL-3.0-or-later Yes Details →
2.3.13.post1 07 Dec 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.13 06 Dec 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.12.post1 25 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.12 25 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11.post6 20 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11.post5 20 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11.post4 17 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11.post3 10 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11.post2 02 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11.post1 01 Nov 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.11 31 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.10 29 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.9.post2 28 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.9.post1 26 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.9 26 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.8.post3 14 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.8.post2 13 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.8.post1 12 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.8 11 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.7 05 Oct 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.6.post3 29 Sep 2023 M1 U1 LGPL-3.0 Yes Details →
2.3.6.post2 29 Sep 2023 M1 U1 — Yes Details →
2.3.6.post1 28 Sep 2023 M1 U1 — Yes Details →
2.3.6 28 Sep 2023 M1 U1 — Yes Details →
2.3.5.post2 28 Sep 2023 M1 U1 — Yes Details →
2.3.5.post1 22 Sep 2023 M1 U1 — Yes Details →
2.3.5 22 Sep 2023 M1 U1 — Yes Details →
2.3.4 15 Sep 2023 M1 U1 — Yes Details →
2.3.3 07 Sep 2023 M1 U1 — Yes Details →
2.3.2 02 Sep 2023 M1 U1 — Yes Details →
2.3.1 29 Aug 2023 M1 U1 — Yes Details →
2.3.0 19 Aug 2023 M1 U1 — Yes Details →
2.2.11 17 Aug 2023 M1 U1 — Yes Details →
2.2.10 15 Aug 2023 M1 U1 — Yes Details →
2.2.9 09 Aug 2023 M1 U1 — Yes Details →
2.2.8 03 Aug 2023 M1 U1 — Yes Details →
2.2.7 02 Aug 2023 M1 U1 — Yes Details →
2.2.6 22 Jul 2023 M1 U1 — Yes Details →
2.2.5 04 Jul 2023 M1 U1 — Yes Details →
2.2.4 27 Jun 2023 M1 U1 — Yes Details →
2.2.3 22 Jun 2023 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pyrofork

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Path Traversal Vulnerability in Pyrofork Allows Arbitrary File Writes 6.5 medium 2.3.69 10 Dec 2025
CVE-2025-67720: Pyrofork Path Traversal Vulnerability in download_media Method 6.5 medium 2.3.69 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 pyrofork

Is pyrofork safe to use?

Vulert records 2 vulnerabilities for pyrofork 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 pyrofork's Vulert package health score?

Vulert scores pyrofork 77/100, which reads as in good shape. 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 pyrofork affected?

No. 2.3.69, 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 pyrofork should I use?

2.3.69 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 pyrofork have?

2 vulnerabilities are recorded for pyrofork 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 pyrofork vulnerabilities disclosed?

2 vulnerabilities were recorded for pyrofork in the last 12 months, and the oldest entry in this database dates to 10 Dec 2025. 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 pyrofork 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 pyrofork for upcoming vulnerabilities?

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