cve.bz

CVE-2026-62268 borgbackup borg: Link Following

5.3 mediumEPSS 0.2%Fix available

Medium (5.3) in borgbackup borg. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in borgbackup 1.4.5, 2.0.0b22.

On this page
borgbackup is an opensource, deduplicating archiver with compression and authenticated encryption. Prior to 1.4.5 and 2.0.0b22, extracting a malicious archive can follow a symlinked parent path or resolve embedded dot-dot path components and delete or overwrite files outside the extraction directory. A crafted slave hardlink can also use an attacker-controlled hardlink source outside the extraction directory and hard-link that file into the restored tree, disclosing its contents. Creating the malicious archive requires repository access and, for encrypted or authenticated repositories, the Borg key and passphrase; a victim must then extract the archive. This issue is fixed in versions 1.4.5 and 2.0.0b22.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-62268 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62268?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62268?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62268 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
borgbackup borg< 1.4.5
borgbackup borg>= 2.0.0b1, < 2.0.0b22

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gfp8-w835-v44jPyPIborgbackup<1.4.51.4.5
GHSA-gfp8-w835-v44jPyPIborgbackup>=2.0.0b1 <2.0.0b222.0.0b22

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13borgbackup, borgbackup2no fix listedDEBIAN-CVE-2026-62268
Debian14borgbackup1.4.5-1DEBIAN-CVE-2026-62268
Debian14borgbackup22.0.0b22-1DEBIAN-CVE-2026-62268
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 1 moreborgbackupno fix listedUBUNTU-CVE-2026-62268
Ubuntu24.04:LTS, 26.04:LTS, 26.10borgbackup, borgbackup2no fix listedUBUNTU-CVE-2026-62268
Alpinev3.24borgbackup1.4.5-r0ALPINE-CVE-2026-62268

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because successful exploitation requires high privileges, including direct write access to the backup repository and knowledge of the repository encryption passphrase or key, followed by user interaction to extract the archive. In typical enterprise deployments, backup extraction is an administrative operation performed in controlled environments from trusted repositories. Although an untrusted archive could lead to unauthorized file manipulation or data exposure outside the intended destination directory, the prerequisite of possessing authenticated repository access substantially limits practical risk.

Red Hat's mitigation

To mitigate this issue, restrict access to backup repositories and isolate extraction operations:

1. Operational controls: Ensure repository storage access, SSH keys, and Borg encryption passphrases are restricted to trusted personnel to prevent unauthorized users from committing crafted archive data. Avoid extracting archives received from untrusted or unverified sources.

2. Sandboxing: When restoring or inspecting potentially untrusted backup archives, execute the extraction process inside an isolated, unprivileged container or sandbox environment with restricted filesystem mount permissions. This limits the blast radius of any directory traversal or out-of-tree file overwrite.

Caveats: Extracting within a sandboxed or containerized environment introduces operational overhead and requires manual verification before transferring restored files to production paths.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-62268.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON