CVE-2016-10099: Borg (aka BorgBackup) before 1.0.9 has a flaw in the cryptographic protocol used to authenticate the manifest

Q: How do I fix CVE-2016-10099?

borg: upgrade to newer than 1.0.8. Exact commands for each OS are on this page.

Q: Is CVE-2016-10099 being exploited?

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

Q: What does CVE-2016-10099 affect?

CVE-2016-10099 affects borg. Severity is medium (CVSS 5.3). Borg (aka BorgBackup) before 1.0.9 has a flaw in the cryptographic protocol used to authenticate the manifest (list of archives), potentially allowing an attacker to spoof the list of archives.

Q: How urgent is CVE-2016-10099?

Priority 41/100. Remotely exploitable, no login, no user action

This month

MEDIUM 5.3REMOTEUPGRADE

CVE-2016-10099 is a medium-severity flaw (CVSS 5.3) affecting borg. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Borg (aka BorgBackup) before 1.0.9 has a flaw in the cryptographic protocol used to authenticate the manifest (list of archives), potentially allowing an attacker to spoof the list of archives.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 30%)
CISA exploited list	No
Weakness	CWE-310
Published	2017-01-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: borg project

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

Am I affected?

Timeline

2017-01-02 21:59 UTCPublished CVE record published
2026-06-17 00:39 UTCUpdated Record last modified

borg project borg UPGRADE

Affected: <= 1.0.8

Fixed in: newer than 1.0.8

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 1.0.8 (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.

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-2016-10099?

borg: upgrade to newer than 1.0.8. Exact commands for each OS are on this page.

Is CVE-2016-10099 being exploited?

CVE-2016-10099 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-2016-10099 affect?

CVE-2016-10099 affects borg. Severity is medium (CVSS 5.3). Borg (aka BorgBackup) before 1.0.9 has a flaw in the cryptographic protocol used to authenticate the manifest (list of archives), potentially allowing an attacker to spoof the list of archives.

How urgent is CVE-2016-10099?

Priority 41/100. Remotely exploitable, no login, no user action

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-2017-15914 HIGH 8.8 UPGRADE Incorrect implementation of access controls allows remote users to override repository restrictions in Borg se
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

References

← Back to latest CVEs