VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

briefcase: vulnerability history, versions and safety

briefcase is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 30 releases, first recorded in Mar 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
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 26 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all briefcase vulnerabilities

Vulert verdict on briefcase 0.4.6 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.4.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 26 Mar 2026 i
  • Highest CVSS 7.3 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 3,364 i
  • OpenSSF scorecard 6/10 i
  • Last release this month 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 briefcase, 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.4.6 13 Oct 2026 none BSD-3-Clause — Details →
0.4.5 08 Sep 2026 none BSD-3-Clause — Details →
0.4.5rc1 07 Sep 2026 none BSD-3-Clause — Details →
0.4.4 08 Jul 2026 none BSD-3-Clause — Details →
0.4.3 02 Jul 2026 none BSD-3-Clause — Details →
0.4.2 06 May 2026 none BSD-3-Clause — Details →
0.4.1 09 Mar 2026 none BSD-3-Clause — Details →
0.4.0 05 Mar 2026 none BSD-3-Clause — Details →
0.3.26 04 Dec 2025 none BSD-3-Clause — Details →
0.3.26rc5 04 Dec 2025 H1 U1 BSD-3-Clause Yes Details →
0.3.25 26 Aug 2025 H1 U1 BSD-3-Clause Yes Details →
0.3.24 10 Jul 2025 H1 U1 BSD-3-Clause Yes Details →
0.3.23 08 May 2025 H1 U1 BSD-3-Clause Yes Details →
0.3.22 07 Feb 2025 H1 U1 non-standard Yes Details →
0.3.21 24 Jan 2025 H1 U1 non-standard Yes Details →
0.3.20 15 Oct 2024 H1 U1 non-standard Yes Details →
0.3.19 12 Jun 2024 H1 U1 non-standard Yes Details →
0.3.18 06 May 2024 H1 U1 non-standard Yes Details →
0.3.17 06 Feb 2024 H1 U1 non-standard Yes Details →
0.3.16 20 Oct 2023 H1 U1 non-standard Yes Details →
0.3.15 10 Jul 2023 H1 U1 non-standard Yes Details →
0.3.14 12 Apr 2023 H1 U1 non-standard Yes Details →
0.3.13 10 Mar 2023 H1 U1 non-standard Yes Details →
0.3.12 30 Jan 2023 H1 U1 non-standard Yes Details →
0.3.11 14 Oct 2022 H1 U1 non-standard Yes Details →
0.3.11rc4 12 Oct 2022 H1 U1 non-standard Yes Details →
0.3.10 30 Sep 2022 H1 U1 non-standard Yes Details →
0.3.10rc8 30 Sep 2022 H1 U1 non-standard Yes Details →
0.3.10rc7 30 Sep 2022 H1 U1 non-standard Yes Details →
0.3.9 17 Aug 2022 H1 U1 non-standard Yes Details →
0.3.8 27 Jun 2022 H1 U1 non-standard Yes Details →
0.3.7 17 May 2022 H1 U1 non-standard Yes Details →
0.3.6 28 Feb 2022 H1 U1 non-standard Yes Details →
0.3.5 06 Mar 2021 H1 U1 non-standard Yes Details →
0.3.4 03 Jan 2021 H1 U1 non-standard Yes Details →
0.3.3 18 Jul 2020 H1 U1 non-standard Yes Details →
0.3.2 04 Jul 2020 H1 U1 non-standard Yes Details →
0.3.1 13 Jun 2020 H1 U1 non-standard Yes Details →
0.3.0 18 Apr 2020 H1 U1 non-standard Yes Details →
0.3.0.dev8 21 Mar 2020 none non-standard — Details →
0.3.0.dev7 22 Feb 2020 none non-standard — Details →
0.3.0.dev6 19 Feb 2020 none non-standard — Details →
0.3.0.dev5 07 Jan 2020 none non-standard — Details →
0.3.0.dev4 02 Jan 2020 none non-standard — Details →
0.3.0.dev3 01 Jan 2020 none non-standard — Details →
0.3.0.dev2 28 Dec 2019 none non-standard — Details →
0.3.0.dev1 21 Dec 2019 none non-standard — Details →
0.2.10 22 Aug 2019 none non-standard — Details →
0.2.9 19 Mar 2019 none non-standard — Details →
0.2.8 19 Oct 2018 none non-standard — Details →
0.2.7 23 Sep 2018 none non-standard — Details →
0.2.6 29 Jul 2018 none non-standard — Details →
0.2.5 07 Jul 2018 none non-standard — Details →
0.2.4 19 May 2018 none non-standard — Details →
0.2.3 15 Apr 2018 none non-standard — Details →
0.2.2 15 Apr 2018 none non-standard — Details →
0.2.1 01 Aug 2017 none non-standard — Details →
0.2.0 30 Jul 2017 none non-standard — Details →
0.1.9 24 Jun 2017 none non-standard — Details →
0.1.8 22 May 2017 none non-standard — Details →
0.1.7 19 Apr 2017 none non-standard — Details →
0.1.6 20 Mar 2017 none non-standard — Details →
0.1.5 27 Sep 2016 none non-standard — Details →
0.1.4 09 Jul 2016 none non-standard — Details →
0.1.3 04 Jan 2016 none non-standard — Details →
0.1.2 21 Dec 2015 none non-standard — Details →
0.1.1 21 Dec 2015 none non-standard — Details →
0.1.0 28 Jul 2015 none non-standard — Details →

All 68 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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 briefcase

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33430: Briefcase Windows MSI Installer Privilege Escalation via Insecure Directory Permissions 7.3 high 0.3.26 23 Mar 2026
CVE-2026-33430: Briefcase Windows Installer Directory Permission Vulnerability 7.3 high 0.3.26 26 Mar 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 briefcase

Is briefcase safe to use?

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

Vulert scores briefcase 80/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 briefcase affected?

No. 0.4.6, 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 briefcase should I use?

0.4.6 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 briefcase have?

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

2 vulnerabilities were recorded for briefcase in the last 12 months, and the oldest entry in this database dates to 23 Mar 2026. 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 briefcase 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 briefcase for upcoming vulnerabilities?

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