CVE-2017-15914: Incorrect implementation of access controls allows remote users to override repository restrictions in Borg se

This month

HIGH 8.8UPGRADE

CVE-2017-15914 is a high-severity flaw (CVSS 8.8) affecting borg. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Incorrect implementation of access controls allows remote users to override repository restrictions in Borg servers 1.1.x before 1.1.3.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Published	2018-02-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: borgbackup

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-02-08 23:29 UTCPublished CVE record published
2026-06-17 01:08 UTCUpdated Record last modified

borgbackup borg UPGRADE

Affected: >= 1.1.0 and < 1.1.3

Fixed in: 1.1.3

Safe to downgrade to: a release before 1.1.0

1. Check installed version

apt-cache policy borg || rpm -q borg || borg --version

2. UPGRADE to 1.1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade borg

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade borg

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.1.0 (Debian / Ubuntu)

apt-cache madison borg sudo apt install borg=<VERSION_BEFORE_1.1.0> sudo apt-mark hold borg

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list borg sudo dnf downgrade borg-<VERSION_BEFORE_1.1.0> sudo dnf versionlock add borg

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-15914?

borg: upgrade to 1.1.3. Exact commands for each OS are on this page.

Is CVE-2017-15914 being exploited?

CVE-2017-15914 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-15914 affect?

CVE-2017-15914 affects borg. Severity is high (CVSS 8.8). Incorrect implementation of access controls allows remote users to override repository restrictions in Borg servers 1.1.x before 1.1.3.

How urgent is CVE-2017-15914?

Priority 51/100. High severity

Related CVEs

CVE-2023-36811 MEDIUM 4.7 UPGRADE borgbackup is an opensource, deduplicating archiver with compression and authenticated encryption
CVE-2023-26265 MEDIUM 5.3 UPGRADE The Borg theme before 1.1.19 for Backdrop CMS does not sufficiently sanitize path arguments that are passed in
CVE-2016-10100 MEDIUM 5.3 UPGRADE Borg (aka BorgBackup) before 1.0.9 has a flaw in the way duplicate archive names were processed during manifes
CVE-2016-10099 MEDIUM 5.3 UPGRADE Borg (aka BorgBackup) before 1.0.9 has a flaw in the cryptographic protocol used to authenticate the manifest

References

← Back to latest CVEs