CVSS 4.0
5.3 mediumCVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NMedium (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.
CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:Nborgbackup (PyPI): fixed in 1.4.5, 2.0.0b22Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| borgbackup borg | < 1.4.5 |
| borgbackup borg | >= 2.0.0b1, < 2.0.0b22 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-gfp8-w835-v44j | PyPI | borgbackup | <1.4.5 | 1.4.5 |
| GHSA-gfp8-w835-v44j | PyPI | borgbackup | >=2.0.0b1 <2.0.0b22 | 2.0.0b22 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | borgbackup, borgbackup2 | no fix listed | DEBIAN-CVE-2026-62268 |
| Debian | 14 | borgbackup | 1.4.5-1 | DEBIAN-CVE-2026-62268 |
| Debian | 14 | borgbackup2 | 2.0.0b22-1 | DEBIAN-CVE-2026-62268 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 1 more | borgbackup | no fix listed | UBUNTU-CVE-2026-62268 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | borgbackup, borgbackup2 | no fix listed | UBUNTU-CVE-2026-62268 |
| Alpine | v3.24 | borgbackup | 1.4.5-r0 | ALPINE-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 rates this Moderate.
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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
Changes since this site first stored the record. The same for every record: /api/public/changes.