CVE-2026-71243

backmeup (npm) - OS Command Injection via Backup Option Values

Published Aug 5, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
The backmeup npm package assembles shell command strings by directly concatenating its option values (name, source, destination, filter) - e.g. cmd = "mkdir -p " + path.join(info.destination, info.name) + "; " - and executes the resulting string through a shell via ssh2-exec (locally via child_process, or remotely via SSH when an ssh handle is supplied), rather than using execFile/spawn with an argument array.

Analysis

AI-generated

Technical impact

The backmeup npm package builds shell command strings by directly concatenating option values such as name, source, destination, and filter. These concatenated strings are executed through a shell via ssh2‑exec (for remote execution) or child_process (for local execution), instead of using execFile or spawn with an argument array. Because no escaping or input validation is performed, shell metacharacters within any of the option values can manipulate the command string, resulting in an OS command injection vulnerability (CWE‑78). An attacker who can influence any of these option values can trigger arbitrary command execution on the machine performing the backup or on a remote SSH target.

Affected Systems

The affected product is the backmeup module released by adaltas. No specific version ranges are documented by the CNA, so any installed instance that accepts untrusted option values could be vulnerable.

Risk and Exploitability

The CVSS score of 8.8 indicates a high‑severity vulnerability. With the EPSS score of 0.00416, the exploit probability is very low but nonzero, and the vulnerability is not listed in the CISA KEV catalog, suggesting no publicly documented widespread exploitation yet. An attacker can trigger the flaw by supplying malicious values for the backup name, source, destination or filter options, causing the concatenated shell command to be executed either locally or on a remote SSH target. Local execution requires the attacker's ability to influence the options, while remote execution needs a valid SSH session to the target, usually granted by the application. The lack of a vendor‑provided patch means remediation relies on application‑level mitigations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to the latest backmeup release once a patched version is available
  • If upgrading immediately is not possible, remove the use of ssh2‑exec or child_process by configuring the application to avoid executing the concatenated command string
  • Sanitize all option values before passing them to backmeup; for example, reject or encode any shell metacharacters, restrict names to alphanumerics, and validate destination paths

Generated by OpenCVE AI on August 10, 2026 at 21:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Description The backmeup npm package assembles shell command strings by directly concatenating its option values (name, source, destination, filter) - e.g. cmd = "mkdir -p " + path.join(info.destination, info.name) + "; " - and executes the resulting string through a shell via ssh2-exec (locally via child_process, or remotely via SSH when an ssh handle is supplied), rather than using execFile/spawn with an argument array. The only processing applied is path.normalize()/path.join(), which do not neutralize shell metacharacters (;, |, &, $(), backticks, newline). Any application that passes attacker-influenced values into these options (e.g. a user-chosen backup name) is vulnerable to arbitrary OS command execution on the backup host, or on the remote SSH target when one is configured. The backmeup npm package assembles shell command strings by directly concatenating its option values (name, source, destination, filter) - e.g. cmd = "mkdir -p " + path.join(info.destination, info.name) + "; " - and executes the resulting string through a shell via ssh2-exec (locally via child_process, or remotely via SSH when an ssh handle is supplied), rather than using execFile/spawn with an argument array.
Type Values Removed Values Added
Title backmeup (npm): OS Command Injection via Backup Option Values backmeup (npm) - OS Command Injection via Backup Option Values
Type Values Removed Values Added
First Time appeared Adaltas
Adaltas backmeup
Vendors & Products Adaltas
Adaltas backmeup
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The backmeup npm package assembles shell command strings by directly concatenating its option values (name, source, destination, filter) - e.g. cmd = "mkdir -p " + path.join(info.destination, info.name) + "; " - and executes the resulting string through a shell via ssh2-exec (locally via child_process, or remotely via SSH when an ssh handle is supplied), rather than using execFile/spawn with an argument array. The only processing applied is path.normalize()/path.join(), which do not neutralize shell metacharacters (;, |, &, $(), backticks, newline). Any application that passes attacker-influenced values into these options (e.g. a user-chosen backup name) is vulnerable to arbitrary OS command execution on the backup host, or on the remote SSH target when one is configured.
Title backmeup (npm): OS Command Injection via Backup Option Values
Weaknesses CWE-78
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-78

    Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Sources

Status
PUBLISHED
Assigner
TuranSec
Published
Updated
Aug 10, 2026, 11:45 AM
Reserved
Aug 5, 2026, 10:53 AM
Status
Deferred
Published
Aug 5, 2026, 11:16 AM
Modified
Oct 24, 2026, 3:10 PM