Skip to main content
Vulnerability Database/CVE-2026-104805

CVE-2026-104805: Backup Restoration Path Traversal Vulnerability

CVE-2026-104805 is a path traversal flaw in backup restoration that allows attackers to inject arbitrary files during restoration from compromised repositories. This article covers technical details, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104805 Overview

CVE-2026-104805 is a path traversal vulnerability [CWE-22] in a backup restoration mechanism disclosed by DigitalCanion. The flaw resides in the TGZ archive extraction routine, which fails to validate file paths, file types, integrity, and authenticity before writing files to disk. An attacker with access to the configured backup repository, such as an SFTP share, can supply a crafted archive that places attacker-controlled files anywhere on the underlying Linux host during restoration.

Critical Impact

Successful exploitation can lead to arbitrary file write on the underlying Linux system and may be leveraged to achieve code execution with root privileges, fully compromising the virtual machine.

Affected Products

  • Vendor-supplied backup restoration component (vendor identification pending in NVD)
  • Linux-based virtual appliance using TGZ-formatted backup archives
  • Deployments relying on SFTP or similar repositories without enforced backup passwords

Discovery Timeline

  • 2026-10-05 - CVE-2026-104805 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-104805

Vulnerability Analysis

The vulnerability resides in the backup restoration workflow. When a TGZ archive is retrieved from the configured repository, the application extracts its contents without verifying file-signature or archive authenticity. The restoration routine also does not canonicalize or constrain entry paths before writing files to the filesystem.

Because TGZ (tar+gzip) archives preserve relative and absolute path metadata for each entry, a crafted archive can include entries with traversal sequences such as ../ or absolute paths such as /etc/, /usr/local/bin/, or /root/.ssh/. These entries are extracted with the privileges of the restoration process, which runs as root on the appliance.

Attackers can leverage this to overwrite system binaries, drop cron jobs under /etc/cron.d/, add SSH authorized keys, or modify service unit files. Any of these outcomes can be chained to achieve arbitrary code execution as root.

Root Cause

The root cause is improper limitation of a pathname to a restricted directory [CWE-22] during archive extraction. The code trusts path metadata inside the TGZ archive and performs no integrity or signature verification on the archive itself. Compounding the issue, the backup mechanism does not enforce the use of a backup password, weakening protection of the repository and making it easier for an attacker to stage a malicious archive.

Attack Vector

Exploitation requires access to the backup repository, such as the SFTP location configured for the appliance. An attacker who has obtained repository credentials, or who can write to the share through adjacent compromise, replaces or supplies a malicious TGZ archive. When an administrator initiates restoration, or when restoration occurs through an automated workflow, the archive is extracted and attacker-controlled files are written to arbitrary locations on the host.

See the Digital Canion Security Research advisory for additional technical context.

Detection Methods for CVE-2026-104805

Indicators of Compromise

  • Unexpected files written outside the designated restore directory, particularly under /etc/, /root/, /usr/local/, or /var/spool/cron/.
  • TGZ archives in the backup repository containing entries with ../ sequences or absolute paths.
  • New or modified SSH authorized_keys files, systemd unit files, or cron entries created at the time of a restore operation.
  • Repository access from unexpected IP addresses or accounts, especially write operations to the SFTP share.

Detection Strategies

  • Inspect TGZ archives in backup repositories with tar -tzvf and flag any entry whose normalized path escapes the intended extraction root.
  • Correlate backup restoration events with filesystem change events to identify writes outside expected directories.
  • Alert on filesystem integrity monitoring (FIM) changes to sensitive paths that coincide with restore operations.

Monitoring Recommendations

  • Enable detailed audit logging on the SFTP or backup repository to capture file uploads, deletions, and overwrites.
  • Monitor the appliance for new root-owned processes, scheduled tasks, or privileged service modifications following restore activity.
  • Track administrator initiation of restore operations and require approval workflows for execution.

How to Mitigate CVE-2026-104805

Immediate Actions Required

  • Restrict access to the backup repository to a minimal set of trusted accounts and rotate credentials for any SFTP users with write access.
  • Enforce a strong backup password on all backup jobs to protect archive integrity and confidentiality.
  • Validate the contents of any TGZ archive before performing a restore, confirming the archive originates from the appliance and has not been modified.
  • Suspend automated restoration workflows until a vendor patch is applied.

Patch Information

At the time of publication, no vendor patch reference is listed in the NVD entry for CVE-2026-104805. Monitor the Digital Canion Security Research page and the affected vendor's advisories for updated firmware or software addressing the path traversal and missing signature verification.

Workarounds

  • Store backup archives on a repository that only the appliance can write to, blocking lateral or adjacent attackers from staging malicious archives.
  • Compute and verify a cryptographic hash of each backup archive out-of-band before restoration.
  • Restore to an isolated or staging appliance first, then compare the extracted filesystem against a known-good baseline before promoting to production.
  • Disable the restoration feature entirely if operationally feasible until the vulnerability is patched.
bash
# Inspect a TGZ archive for suspicious path entries before restoration
tar -tzvf backup.tgz | awk '{print $NF}' | grep -E '^(/|.*\.\./)' && \
  echo 'WARNING: archive contains absolute or traversal paths - do not restore'

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.