VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

borgbackup: vulnerability history, versions and safety

borgbackup is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Feb 2018 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H1 M2 U2
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 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all borgbackup vulnerabilities

Vulert verdict on borgbackup 1.4.5 i

Updated on 23 Oct 2026

Action needed: 1.4.5 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.4.5 — affected i
  • Vulnerabilities on record 5 over 8 years · 1 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 8 packages i
  • Stars 13,863 i
  • OpenSSF scorecard 6/10 i
  • Last release 3 months ago 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 borgbackup, 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.0b25 27 Sep 2026 U1 BSD-3-Clause Yes Details →
2.0.0b24 02 Sep 2026 U1 BSD-3-Clause Yes Details →
2.0.0b23 23 Aug 2026 U1 BSD-3-Clause Yes Details →
2.0.0b22 22 Jul 2026 U1 BSD-3-Clause Yes Details →
1.4.5 18 Jul 2026 U1 BSD-3-Clause Yes Details →
1.4.4 19 Mar 2026 M1 BSD-3-Clause Yes Details →
2.0.0b21 15 Mar 2026 U1 BSD-3-Clause Yes Details →
2.0.0b20 24 Dec 2025 U1 BSD-3-Clause Yes Details →
1.4.3 02 Dec 2025 M1 BSD-3-Clause Yes Details →
1.4.2 31 Oct 2025 M1 BSD-3-Clause Yes Details →
1.2.9 05 Aug 2025 M1 non-standard Yes Details →
2.0.0b19 02 Aug 2025 U1 BSD-3-Clause Yes Details →
2.0.0b18 19 Jun 2025 U1 BSD-3-Clause Yes Details →
2.0.0b17 23 May 2025 U1 BSD-3-Clause Yes Details →
2.0.0b16 06 May 2025 U1 BSD-3-Clause Yes Details →
2.0.0b15 22 Apr 2025 U1 BSD-3-Clause Yes Details →
1.4.1 18 Apr 2025 M1 non-standard Yes Details →
2.0.0b14 17 Nov 2024 U1 non-standard Yes Details →
2.0.0b13 31 Oct 2024 U1 non-standard Yes Details →
2.0.0b12 03 Oct 2024 U1 non-standard Yes Details →
2.0.0b11 26 Sep 2024 U1 non-standard Yes Details →
2.0.0b10 09 Sep 2024 U1 non-standard Yes Details →
2.0.0b9 20 Jul 2024 U1 non-standard Yes Details →
1.4.0 03 Jul 2024 M1 non-standard Yes Details →
1.4.0rc1 26 May 2024 M1 non-standard Yes Details →
1.4.0b2 31 Mar 2024 M1 non-standard Yes Details →
1.2.8 29 Mar 2024 M1 non-standard Yes Details →
2.0.0b8 21 Feb 2024 U1 non-standard Yes Details →
1.4.0b1 21 Jan 2024 M1 non-standard Yes Details →
1.4.0a1 01 Jan 2024 M1 non-standard Yes Details →
1.2.7 02 Dec 2023 M1 non-standard Yes Details →
2.0.0b7 14 Sep 2023 U1 non-standard Yes Details →
1.2.6 31 Aug 2023 M1 non-standard Yes Details →
1.2.5 30 Aug 2023 M1 non-standard Yes Details →
2.0.0b6 12 Jun 2023 U1 non-standard Yes Details →
1.2.4 23 Mar 2023 M2 U1 non-standard Yes Details →
2.0.0b5 27 Feb 2023 U1 non-standard Yes Details →
1.2.3 24 Dec 2022 M2 U1 non-standard Yes Details →
2.0.0b4 26 Nov 2022 U1 non-standard Yes Details →
2.0.0b3 02 Oct 2022 U1 non-standard Yes Details →
2.0.0b2 10 Sep 2022 U1 non-standard Yes Details →
1.2.2 20 Aug 2022 M2 U1 non-standard Yes Details →
2.0.0b1 07 Aug 2022 U1 non-standard Yes Details →
2.0.0a4 17 Jul 2022 U1 non-standard Yes Details →
2.0.0a3 04 Jul 2022 U1 non-standard Yes Details →
2.0.0a2 26 Jun 2022 U1 non-standard Yes Details →
1.2.1 05 Jun 2022 M2 U1 non-standard Yes Details →
1.1.18 05 Jun 2022 M2 U1 non-standard Yes Details →
1.3.0a1 14 Apr 2022 M1 non-standard Yes Details →
1.2.0 22 Feb 2022 M2 U1 non-standard Yes Details →
1.2.0rc1 05 Feb 2022 M2 U1 non-standard Yes Details →
1.2.0b4 23 Jan 2022 M2 U1 non-standard Yes Details →
1.1.17 12 Jul 2021 M2 U1 non-standard Yes Details →
1.2.0b3 12 May 2021 M2 U1 non-standard Yes Details →
1.1.16 22 Mar 2021 M2 U1 non-standard Yes Details →
1.2.0b2 06 Feb 2021 M2 U1 non-standard Yes Details →
1.1.15 25 Dec 2020 M2 U1 non-standard Yes Details →
1.2.0b1 06 Dec 2020 M2 U1 non-standard Yes Details →
1.1.14 06 Oct 2020 M2 U1 non-standard Yes Details →
1.2.0a9 05 Oct 2020 M2 U1 non-standard Yes Details →
1.1.13 06 Jun 2020 M2 U1 non-standard Yes Details →
1.1.12 06 Jun 2020 M2 U1 non-standard Yes Details →
1.2.0a8 22 Apr 2020 M2 U1 non-standard Yes Details →
1.1.11 07 Mar 2020 M2 U1 non-standard Yes Details →
1.2.0a7 07 Sep 2019 M2 U1 non-standard Yes Details →
1.1.10 16 May 2019 M2 U1 non-standard Yes Details →
1.2.0a6 22 Apr 2019 M2 U1 non-standard Yes Details →
1.2.0a5 21 Mar 2019 M2 U1 non-standard Yes Details →
1.2.0a4 10 Mar 2019 M2 U1 non-standard Yes Details →
1.2.0a3 26 Feb 2019 M2 U1 non-standard Yes Details →
1.2.0a2 24 Feb 2019 M2 U1 non-standard Yes Details →
1.0.13 15 Feb 2019 M2 U1 non-standard Yes Details →
1.1.9 11 Feb 2019 M2 U1 non-standard Yes Details →
1.1.8 09 Dec 2018 M2 U1 non-standard Yes Details →
1.1.7 11 Aug 2018 M2 U1 non-standard Yes Details →
1.1.6 11 Jun 2018 M2 U1 non-standard Yes Details →
1.0.12 08 Apr 2018 M2 U1 non-standard Yes Details →
1.1.5 31 Mar 2018 M2 U1 non-standard Yes Details →
1.1.4 30 Dec 2017 M2 U1 non-standard Yes Details →
1.1.3 27 Nov 2017 M2 U1 non-standard Yes Details →
1.1.2 05 Nov 2017 H1 M2 U2 non-standard Yes Details →
1.1.1 22 Oct 2017 H1 M2 U2 non-standard Yes Details →
1.1.0 07 Oct 2017 H1 M2 U2 non-standard Yes Details →
1.1.0rc4 01 Oct 2017 H1 M2 U2 non-standard Yes Details →
1.1.0rc3 10 Sep 2017 H1 M2 U2 non-standard Yes Details →
1.1.0rc2 28 Aug 2017 H1 M2 U2 non-standard Yes Details →
1.1.0rc1 23 Jul 2017 H1 M2 U2 non-standard Yes Details →
1.0.11 21 Jul 2017 M2 U1 non-standard Yes Details →
1.0.11rc1 26 Jun 2017 M2 U1 non-standard Yes Details →
1.1.0b6 18 Jun 2017 H1 M2 U2 non-standard Yes Details →
1.1.0b5 30 Apr 2017 H1 M2 U2 non-standard Yes Details →
1.1.0b4 27 Mar 2017 H1 M2 U2 non-standard Yes Details →
1.0.10 13 Feb 2017 M2 U1 non-standard Yes Details →
1.0.10rc1 29 Jan 2017 M2 U1 non-standard Yes Details →
1.1.0b3 15 Jan 2017 H1 M2 U2 non-standard Yes Details →
1.0.9 20 Dec 2016 M2 U1 non-standard Yes Details →
1.0.9rc1 27 Nov 2016 M2 U1 non-standard Yes Details →
1.0.8 29 Oct 2016 M2 U1 non-standard Yes Details →
1.0.8rc1 17 Oct 2016 M2 U1 non-standard Yes Details →
1.1.0b2 01 Oct 2016 H1 M2 U2 non-standard Yes Details →
1.1.0b1 28 Aug 2016 H1 M2 U2 — Yes Details →
1.0.7 19 Aug 2016 M2 U1 — Yes Details →
1.0.7rc2 13 Aug 2016 M2 U1 — Yes Details →
1.0.7rc1 05 Aug 2016 M2 U1 — Yes Details →
1.0.6 12 Jul 2016 M2 U1 — Yes Details →
1.0.6rc1 10 Jul 2016 M2 U1 — Yes Details →
1.0.5 07 Jul 2016 M2 U1 — Yes Details →
1.0.4 07 Jul 2016 M2 U1 — Yes Details →
1.0.3 20 May 2016 M2 U1 — Yes Details →
1.0.2 16 Apr 2016 M2 U1 — Yes Details →
1.0.1 09 Apr 2016 M2 U1 — Yes Details →
1.0.0 05 Mar 2016 M2 U1 — Yes Details →
1.0.0rc2 28 Feb 2016 M2 U1 — Yes Details →
0.30.1 07 Feb 2016 M2 U1 — Yes Details →
1.0.0rc1 07 Feb 2016 M2 U1 — Yes Details →
0.30.0 23 Jan 2016 M2 U1 — Yes Details →
0.29.0 13 Dec 2015 M2 U1 — Yes Details →
0.28.2 15 Nov 2015 M2 U1 — Yes Details →
0.28.1 08 Nov 2015 M2 U1 — Yes Details →
0.28.0 08 Nov 2015 M2 U1 — Yes 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

  • 2018 1
  • 2022 1
  • 2023 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for borgbackup

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-15914: Borg Improper Access Control vulnerability in borgbackup 8.8 high 1.1.3 13 May 2022
CVE-2026-62268: borgbackup Symlink and Hardlink Vulnerability Leading to Out-of-Tree File Modification 5.3 medium 1.4.5 15 Oct 2026
CVE-2023-36811: Archive spoofing vulnerability in borgbackup 4.7 medium 1.2.5 30 Aug 2023
CVE-2023-36811: Borgbackup Authentication Bypass 4.7 medium 3eb070191da10c2d3f7bc6484cf3d51c3045f884 30 Aug 2023
CVE-2017-15914: Borgbackup Incorrect Access Control Implementation N/A unrated 1.1.3 08 Feb 2018

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 borgbackup

Is borgbackup safe to use?

Vulert records 5 vulnerabilities for borgbackup in PyPI: 0 critical, 1 high, 2 medium and 0 low, plus 2 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 borgbackup's Vulert package health score?

Vulert scores borgbackup 81/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 borgbackup affected?

Yes. 1.4.5, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of borgbackup should I use?

1.4.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 borgbackup have?

5 vulnerabilities are recorded for borgbackup in the PyPI ecosystem: 0 critical, 1 high, 2 medium and 0 low, plus 2 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 borgbackup vulnerabilities disclosed?

1 vulnerability was recorded for borgbackup in the last 12 months, and the oldest entry in this database dates to 08 Feb 2018. 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 borgbackup 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 borgbackup for upcoming vulnerabilities?

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