VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

fugue: vulnerability history, versions and safety

fugue is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Nov 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 H1 U1
i
2 with no fix published

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

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

Vulert verdict on fugue 0.9.7 i

Updated on 23 Oct 2026

Careful: 0.9.7 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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 0.9.7 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i
  • Depended on by 71 packages i
  • Stars 2,166 i
  • OpenSSF scorecard 3/10 i
  • Last release 8 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 fugue, 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
0.9.7 20 Feb 2026 H1 U1 Apache-2.0 No Details →
0.9.7.dev2 20 Feb 2026 H1 U1 Apache-2.0 No Details →
0.9.7.dev1 20 Feb 2026 H1 U1 Apache-2.0 No Details →
0.9.7.dev0 05 Feb 2026 H1 U1 Apache-2.0 No Details →
0.9.6 30 Jan 2026 H1 U1 Apache-2.0 No Details →
0.9.5 28 Jan 2026 H1 U1 Apache-2.0 No Details →
0.9.4 30 Dec 2025 H1 U1 Apache-2.0 No Details →
0.9.3 02 Dec 2025 H1 U1 Apache-2.0 No Details →
0.9.2 31 Oct 2025 H1 U1 Apache-2.0 No Details →
0.9.2.dev2 29 Mar 2025 H1 U1 Apache-2.0 No Details →
0.9.2.dev1 28 Jun 2024 H1 U1 Apache-2.0 No Details →
0.9.1 14 Jun 2024 H1 U1 Apache-2.0 No Details →
0.9.0 29 Apr 2024 H1 U1 Apache-2.0 No Details →
0.9.0.dev4 28 Apr 2024 H1 U1 Apache-2.0 No Details →
0.9.0.dev3 21 Jan 2024 H1 U1 Apache-2.0 No Details →
0.9.0.dev2 14 Jan 2024 H1 U1 Apache-2.0 No Details →
0.8.7 09 Nov 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev8 09 Nov 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev7 08 Nov 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev6 27 Oct 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev5 09 Oct 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev4 20 Aug 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev3 17 Aug 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev2 16 Aug 2023 H1 U1 Apache-2.0 No Details →
0.8.7.dev1 07 Aug 2023 H1 U1 Apache-2.0 No Details →
0.8.6 26 Jul 2023 H1 U1 Apache-2.0 No Details →
0.8.6.dev3 24 Jul 2023 H1 U1 Apache-2.0 No Details →
0.8.6.dev2 22 Jul 2023 H1 U1 Apache-2.0 No Details →
0.8.6.dev1 13 Jul 2023 H1 U1 Apache-2.0 No Details →
0.8.5 11 Jun 2023 H1 U1 Apache-2.0 No Details →
0.8.5.dev1 07 Jun 2023 H1 U1 Apache-2.0 No Details →
0.8.4 24 May 2023 H1 U1 Apache-2.0 No Details →
0.8.4.dev2 08 May 2023 H1 U1 Apache-2.0 No Details →
0.8.4.dev1 03 May 2023 H1 U1 Apache-2.0 No Details →
0.8.3 31 Mar 2023 H1 U1 Apache-2.0 No Details →
0.8.3.dev1 29 Mar 2023 H1 U1 Apache-2.0 No Details →
0.8.2 23 Mar 2023 H1 U1 Apache-2.0 No Details →
0.8.2.dev4 20 Mar 2023 H1 U1 Apache-2.0 No Details →
0.8.2.dev3 17 Mar 2023 H1 U1 Apache-2.0 No Details →
0.8.2.dev2 09 Mar 2023 H1 U1 Apache-2.0 No Details →
0.8.2.dev1 24 Feb 2023 H1 U1 Apache-2.0 No Details →
0.8.1 17 Feb 2023 H1 U1 Apache-2.0 No Details →
0.8.1.dev4 15 Feb 2023 H1 U1 Apache-2.0 No Details →
0.8.1.dev3 02 Feb 2023 H1 U1 Apache-2.0 No Details →
0.8.1.dev1 01 Feb 2023 H1 U1 Apache-2.0 No Details →
0.8.0 08 Jan 2023 H1 U1 Apache-2.0 No Details →
0.8.0.dev4 05 Jan 2023 H1 U1 Apache-2.0 No Details →
0.8.0.dev3 30 Dec 2022 H1 U1 Apache-2.0 No Details →
0.8.0.dev2 17 Dec 2022 H1 U1 Apache-2.0 No Details →
0.8.0.dev1 18 Nov 2022 H1 U1 Apache-2.0 No Details →
0.7.4.dev1 18 Oct 2022 H1 U1 Apache-2.0 No Details →
0.7.4.dev0 15 Oct 2022 H1 U1 Apache-2.0 No Details →
0.7.3 03 Oct 2022 H1 U1 Apache-2.0 No Details →
0.7.3.dev1 02 Oct 2022 H1 U1 Apache-2.0 No Details →
0.7.3.dev0 28 Sep 2022 H1 U1 Apache-2.0 No Details →
0.7.2 29 Aug 2022 H1 U1 Apache-2.0 No Details →
0.7.1 02 Aug 2022 H1 U1 Apache-2.0 No Details →
0.7.1.dev1 01 Aug 2022 H1 U1 Apache-2.0 No Details →
0.7.0 16 Jul 2022 H1 U1 Apache-2.0 No Details →
0.7.0.dev5 16 Jul 2022 H1 U1 Apache-2.0 No Details →
0.7.0.dev4 13 Jul 2022 H1 U1 Apache-2.0 No Details →
0.7.0.dev3 11 Jul 2022 H1 U1 Apache-2.0 No Details →
0.7.0.dev2 23 May 2022 H1 U1 Apache-2.0 No Details →
0.7.0.dev1 08 May 2022 H1 U1 Apache-2.0 No Details →
0.6.6 12 Apr 2022 H1 U1 Apache-2.0 No Details →
0.6.6.dev3 03 Apr 2022 H1 U1 Apache-2.0 No Details →
0.6.6.dev2 24 Mar 2022 H1 U1 Apache-2.0 No Details →
0.6.6.dev1 15 Mar 2022 H1 U1 Apache-2.0 No Details →
0.6.5 25 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev9 25 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev8 24 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev7 18 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev6 18 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev5 17 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev4 06 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev3 02 Jan 2022 H1 U1 Apache-2.0 No Details →
0.6.5.dev2 28 Dec 2021 H1 U1 Apache-2.0 No Details →
0.6.5.dev1 28 Dec 2021 H1 U1 Apache-2.0 No Details →
0.6.4 30 Oct 2021 H1 U1 Apache-2.0 No Details →
0.6.4.dev2 22 Oct 2021 H1 U1 Apache-2.0 No Details →
0.6.4.dev1 18 Oct 2021 H1 U1 Apache-2.0 No Details →
0.6.3 07 Oct 2021 H1 U1 Apache-2.0 No Details →
0.6.2 25 Aug 2021 H1 U1 Apache-2.0 No Details →
0.6.1 16 Aug 2021 H1 U1 Apache-2.0 No Details →
0.6.1.dev3 16 Aug 2021 H1 U1 Apache-2.0 No Details →
0.6.1.dev2 24 Jul 2021 H1 U1 Apache-2.0 No Details →
0.6.1.dev1 23 Jul 2021 H1 U1 Apache-2.0 No Details →
0.6.0 15 Jul 2021 H1 U1 Apache-2.0 No Details →
0.6.0.dev3 24 Jun 2021 H1 U1 Apache-2.0 No Details →
0.6.0.dev2 20 Jun 2021 H1 U1 Apache-2.0 No Details →
0.6.0.dev1 16 Jun 2021 H1 U1 Apache-2.0 No Details →
0.5.7.dev1 03 Jun 2021 H1 U1 Apache-2.0 No Details →
0.5.6 14 May 2021 H1 U1 Apache-2.0 No Details →
0.5.6.dev2 12 May 2021 H1 U1 Apache-2.0 No Details →
0.5.6.dev1 11 May 2021 H1 U1 Apache-2.0 No Details →
0.5.5 05 May 2021 H1 U1 Apache-2.0 No Details →
0.5.5.dev1 05 May 2021 H1 U1 Apache-2.0 No Details →
0.5.4 05 May 2021 H1 U1 Apache-2.0 No Details →
0.5.3 22 Apr 2021 H1 U1 Apache-2.0 No Details →
0.5.3.dev1 07 Apr 2021 H1 U1 Apache-2.0 No Details →
0.5.2 24 Mar 2021 H1 U1 — No Details →
0.5.2.dev2 17 Feb 2021 H1 U1 — No Details →
0.5.2.dev1 17 Feb 2021 H1 U1 — No Details →
0.5.2.dev0 15 Feb 2021 H1 U1 — No Details →
0.5.1 05 Feb 2021 H1 U1 — No Details →
0.5.1.dev6 04 Feb 2021 H1 U1 — No Details →
0.5.1.dev5 01 Feb 2021 H1 U1 — No Details →
0.5.1.dev4 01 Feb 2021 H1 U1 — No Details →
0.5.1.dev3 27 Jan 2021 H1 U1 — No Details →
0.5.1.dev2 26 Jan 2021 H1 U1 — No Details →
0.5.1.dev1 25 Jan 2021 H1 U1 — No Details →
0.5.1.dev0 18 Jan 2021 H1 U1 — No Details →
0.5.0 15 Jan 2021 H1 U1 — No Details →
0.5.0.dev2 11 Jan 2021 H1 U1 — No Details →
0.5.0.dev1 23 Dec 2020 H1 U1 — No Details →
0.5.0.dev0 17 Dec 2020 H1 U1 — No Details →
0.4.9 04 Dec 2020 H1 U1 — No Details →
0.4.8 01 Dec 2020 H1 U1 — No Details →
0.4.7 15 Nov 2020 H1 U1 — No Details →
0.4.6 09 Nov 2020 H1 U1 — No Details →

The newest 120 of 126 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 fugue

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-62703: Fugue Framework Remote Code Execution via Unsafe Pickle Deserialization 8.8 high No fix published 25 Nov 2025
CVE-2025-62703: Fugue Package Vulnerable to Remote Code Execution via Pickle Deserialization 8.8 high No fix published 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 fugue

Is fugue safe to use?

Vulert records 2 vulnerabilities for fugue in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is fugue's Vulert package health score?

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

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

Which version of fugue should I use?

0.9.7 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 fugue have?

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

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

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