CVE-2026-71243
Command injection via shell string concatenation in backmeup npm package
Is CVE-2026-71243 being exploited?
Not confirmed. CVE-2026-71243 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-71243?
CVE-2026-71243 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71243?
Not known from our data. No patch reference has been recorded for CVE-2026-71243, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71243 affect?
CVE-2026-71243 affects backmeup npm package, Node.js applications using backmeup, Backup hosts and remote SSH targets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71243?
Remove/replace backmeup or apply vendor patch; sanitize inputs; use execFile/spawn instead of shell exec.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled fields enable arbitrary OS command execution locally or on remote SSH targets via shell injection.
Immediate action required
- affected<= 0.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.